1. Some plugin development proficiency(having written several easy, simple and small battle-related plugins up to 1k LoC scale)

2. Basic knowledge on what the default RMMZ turn based battle flow implementations do in general

3. Basic knowledge on what the default RMMZ TPBS battle flow does in general on the user level(At least you need to know what's going on on the surface when playing it as a player)

Simplified Flowchart

Please note that this flowchart only includes the most important elements of the battle flow, to avoid making it too complicated and convoluted for the intended targeting audience

Battle Start

Input Action Slots

BattleManager.selectPreviousCommand = function() {
    if (this._currentActor) {
        if (this._currentActor.selectPreviousCommand()) {
            return;
        }
        this.cancelActorInput();
    }
    this.selectPreviousActor();
};

Scene_Battle.prototype.changeInputWindow = function() {
    this.hideSubInputWindows();
    if (BattleManager.isInputting()) {
        if (BattleManager.actor()) {
            this.startActorCommandSelection();
        } else {
            this.startPartyCommandSelection();
        }
    } else {
        this.endCommandSelection();
    }
};

Thinking In Frames

Frame Start

Scene_Battle.prototype.update = function() {
    const active = this.isActive();
    $gameTimer.update(active);
    $gameScreen.update();
    this.updateVisibility();
    if (active && !this.isBusy()) {
        this.updateBattleProcess();
    }
    Scene_Message.prototype.update.call(this);
};

Scene_Battle.prototype.updateBattleProcess = function() {
    BattleManager.update(this.isTimeActive());
};

Scene_Battle.prototype.isTimeActive = function() {
    if (BattleManager.isActiveTpb()) {
        return !this._skillWindow.active && !this._itemWindow.active;
    } else {
        return !this.isAnyInputWindowActive();
    }
};

BattleManager.update = function(timeActive) {
    if (!this.isBusy() && !this.updateEvent()) {
        this.updatePhase(timeActive);
    }
    if (this.isTpb()) {
        this.updateTpbInput();
    }
};

BattleManager.isBusy = function() {
    return (
        $gameMessage.isBusy() ||
        this._spriteset.isBusy() ||
        this._logWindow.isBusy()
    );
};

BattleManager.updateEvent = function() {
    switch (this._phase) {
        case "start":
        case "turn":
        case "turnEnd":
            if (this.isActionForced()) {
                this.processForcedAction();
                return true;
            } else {
                return this.updateEventMain();
            }
    }
    return this.checkAbort();
};

BattleManager.updatePhase = function(timeActive) {
    switch (this._phase) {
        case "start":
            this.updateStart();
            break;
        case "turn":
            this.updateTurn(timeActive);
            break;
        case "action":
            this.updateAction();
            break;
        case "turnEnd":
            this.updateTurnEnd();
            break;
        case "battleEnd":
            this.updateBattleEnd();
            break;
    }
};

Start Phase

BattleManager.updateStart = function() {
    if (this.isTpb()) {
        this._phase = "turn";
    } else {
        this.startInput();
    }
};

Turn Phase

BattleManager.updateTurn = function(timeActive) {
    $gameParty.requestMotionRefresh();
    if (this.isTpb() && timeActive) {
        this.updateTpb();
    }
    if (!this._subject) {
        this._subject = this.getNextSubject();
    }
    if (this._subject) {
        this.processTurn();
    } else if (!this.isTpb()) {
        this.endTurn();
    }
};

BattleManager.updateTpb = function() {
    $gameParty.updateTpb();
    $gameTroop.updateTpb();
    this.updateAllTpbBattlers();
    this.checkTpbTurnEnd();
};

Game_Battler.prototype.updateTpb = function() {
    if (this.canMove()) {
        this.updateTpbChargeTime();
        this.updateTpbCastTime();
        this.updateTpbAutoBattle();
    }
    if (this.isAlive()) {
        this.updateTpbIdleTime();
    }
};

BattleManager.updateTpbBattler = function(battler) {
    if (battler.isTpbTurnEnd()) {
        battler.onTurnEnd();
        battler.startTpbTurn();
        this.displayBattlerStatus(battler, false);
    } else if (battler.isTpbReady()) {
        battler.startTpbAction();
        this._actionBattlers.push(battler);
    } else if (battler.isTpbTimeout()) {
        battler.onTpbTimeout();
        this.displayBattlerStatus(battler, true);
    }
};

Action Phase

Turn End Phase

BattleManager.checkTpbTurnEnd = function() {
    if ($gameTroop.isTpbTurnEnd()) {
        this.endTurn();
    }
};

Game_Troop.prototype.isTpbTurnEnd = function() {
    const members = this.members();
    const turnMax = Math.max(...members.map(member => member.turnCount()));
    return turnMax > this._turnCount;
};

BattleManager.endTurn = function() {
    this._phase = "turnEnd";
    this._preemptive = false;
    this._surprise = false;
};

Battle End Phase

BattleManager.updateBattleEnd = function() {
    if (this.isBattleTest()) {
        AudioManager.stopBgm();
        SceneManager.exit();
    } else if (!this._escaped && $gameParty.isAllDead()) {
        if (this._canLose) {
            $gameParty.reviveBattleMembers();
            SceneManager.pop();
        } else {
            SceneManager.goto(Scene_Gameover);
        }
    } else {
        SceneManager.pop();
    }
    this._phase = "";
};

Update TPB Input

BattleManager.updateTpbInput = function() {
    if (this._inputting) {
        this.checkTpbInputClose();
    } else {
        this.checkTpbInputOpen();
    }
};

BattleManager.checkTpbInputClose = function() {
    if (!this.isPartyTpbInputtable() || this.needsActorInputCancel()) {
        this.cancelActorInput();
        this._currentActor = null;
        this._inputting = false;
    }
};

BattleManager.checkTpbInputOpen = function() {
    if (this.isPartyTpbInputtable()) {
        if (this._tpbNeedsPartyCommand) {
            this._inputting = true;
            this._tpbNeedsPartyCommand = false;
        } else {
            this.selectNextCommand();
        }
    }
};

BattleManager.selectNextCommand = function() {
    if (this._currentActor) {
        if (this._currentActor.selectNextCommand()) {
            return;
        }
        this.finishActorInput();
    }
    this.selectNextActor();
};

Summary

That's all for now. I hope this can help you grasp these basic knowledge. For those thoroughly comprehending the essence of the default RMMZ TPBS battle flow implementations, feel free to correct me if there's anything wrong

For those wanting to have a solid understanding to the default RMMZ TPBS battle flow implementations, I might open a more advanced topic for that later

1. Little javascript coding proficiency(barely okay with writing rudimentary Javascript codes up to 300 LoC scale)

2. Basic knowledge on what the default RMMZ turn based battle flow does on the user level(At least you need to know what's going on on the surface when playing it as a player)

Simplified Flowchart

Please note that this flowchart only includes the most important elements of the battle flow, to avoid making it too complicated and convoluted for the intended targeting audience

Start Battle

BattleManager.initMembers = function() {
    this._phase = "";
    this._inputting = false;
    this._canEscape = false;
    this._canLose = false;
    this._battleTest = false;
    this._eventCallback = null;
    this._preemptive = false;
    this._surprise = false;
    this._currentActor = null;
    this._actionForcedBattler = null;
    this._mapBgm = null;
    this._mapBgs = null;
    this._actionBattlers = [];
    this._subject = null;
    this._action = null;
    this._targets = [];
    this._logWindow = null;
    this._spriteset = null;
    this._escapeRatio = 0;
    this._escaped = false;
    this._rewards = {};
    this._tpbNeedsPartyCommand = true;
};

SceneManager.goto(Scene_Battle);

SceneManager.push(Scene_Battle);

Scene_Battle.prototype.createAllWindows = function() {
    this.createLogWindow();
    this.createStatusWindow();
    this.createPartyCommandWindow();
    this.createActorCommandWindow();
    this.createHelpWindow();
    this.createSkillWindow();
    this.createItemWindow();
    this.createActorWindow();
    this.createEnemyWindow();
    Scene_Message.prototype.createAllWindows.call(this);
};

BattleManager.startBattle = function() {
    this._phase = "start";
    $gameSystem.onBattleStart();
    $gameParty.onBattleStart(this._preemptive);
    $gameTroop.onBattleStart(this._surprise);
    this.displayStartMessages();
};

BattleManager.startInput = function() {
    this._phase = "input";
    this._inputting = true;
    $gameParty.makeActions();
    $gameTroop.makeActions();
    this._currentActor = null;
    if (this._surprise || !$gameParty.canInput()) {
        this.startTurn();
    }
};

Input Actions

Game_Battler.prototype.makeActions = function() {
    this.clearActions();
    if (this.canMove()) {
        const actionTimes = this.makeActionTimes();
        this._actions = [];
        for (let i = 0; i < actionTimes; i++) {
            this._actions.push(new Game_Action(this));
        }
    }
};

Game_Actor.prototype.makeActions = function() {
    Game_Battler.prototype.makeActions.call(this);
    if (this.numActions() > 0) {
        this.setActionState("undecided");
    } else {
        this.setActionState("waiting");
    }
    if (this.isAutoBattle()) {
        this.makeAutoBattleActions();
    } else if (this.isConfused()) {
        this.makeConfusionActions();
    }
};

Game_Enemy.prototype.makeActions = function() {
    Game_Battler.prototype.makeActions.call(this);
    if (this.numActions() > 0) {
        const actionList = this.enemy().actions.filter(a =>
            this.isActionValid(a)
        );
        if (actionList.length > 0) {
            this.selectAllActions(actionList);
        }
    }
    this.setActionState("waiting");
};

Scene_Battle.prototype.changeInputWindow = function() {
    this.hideSubInputWindows();
    if (BattleManager.isInputting()) {
        if (BattleManager.actor()) {
            this.startActorCommandSelection();
        } else {
            this.startPartyCommandSelection();
        }
    } else {
        this.endCommandSelection();
    }
};

Scene_Battle.prototype.startPartyCommandSelection = function() {
    this._statusWindow.deselect();
    this._statusWindow.show();
    this._statusWindow.open();
    this._actorCommandWindow.setup(null);
    this._actorCommandWindow.close();
    this._partyCommandWindow.setup();
};

BattleManager.processAbort = function() {
    $gameParty.removeBattleStates();
    this._logWindow.clear();
    this.replayBgmAndBgs();
    this.endBattle(1);
};

BattleManager.onEscapeFailure = function() {
    $gameParty.onEscapeFailure();
    this.displayEscapeFailureMessage();
    this._escapeRatio += 0.1;
    if (!this.isTpb()) {
        this.startTurn();
    }
};

Game_Actor.prototype.onEscapeFailure = function() {
    if (BattleManager.isTpb()) {
        this.applyTpbPenalty();
    }
    this.clearActions();
    this.requestMotionRefresh();
};

Game_Actor.prototype.clearActions = function() {
    Game_Battler.prototype.clearActions.call(this);
    this._actionInputIndex = 0;
};

Scene_Battle.prototype.selectNextCommand = function() {
    BattleManager.selectNextCommand();
    this.changeInputWindow();
};

BattleManager.selectNextCommand = function() {
    if (this._currentActor) {
        if (this._currentActor.selectNextCommand()) {
            return;
        }
        this.finishActorInput();
    }
    this.selectNextActor();
};

Game_Actor.prototype.selectNextCommand = function() {
    if (this._actionInputIndex < this.numActions() - 1) {
        this._actionInputIndex++;
        return true;
    } else {
        return false;
    }
};

Scene_Battle.prototype.selectPreviousCommand = function() {
    BattleManager.selectPreviousCommand();
    this.changeInputWindow();
};

BattleManager.selectPreviousCommand = function() {
    if (this._currentActor) {
        if (this._currentActor.selectPreviousCommand()) {
            return;
        }
        this.cancelActorInput();
    }
    this.selectPreviousActor();
};

Game_Actor.prototype.selectPreviousCommand = function() {
    if (this._actionInputIndex > 0) {
        this._actionInputIndex--;
        return true;
    } else {
        return false;
    }
};

Process Turns

BattleManager.startTurn = function() {
    this._phase = "turn";
    $gameTroop.increaseTurn();
    $gameParty.requestMotionRefresh();
    if (!this.isTpb()) {
        this.makeActionOrders();
        this._logWindow.startTurn();
        this._inputting = false;
    }
};

BattleManager.makeActionOrders = function() {
    const battlers = [];
    if (!this._surprise) {
        battlers.push(...$gameParty.battleMembers());
    }
    if (!this._preemptive) {
        battlers.push(...$gameTroop.members());
    }
    for (const battler of battlers) {
        battler.makeSpeed();
    }
    battlers.sort((a, b) => b.speed() - a.speed());
    this._actionBattlers = battlers;
};

BattleManager.updateTurn = function(timeActive) {
    $gameParty.requestMotionRefresh();
    if (this.isTpb() && timeActive) {
        this.updateTpb();
    }
    if (!this._subject) {
        this._subject = this.getNextSubject();
    }
    if (this._subject) {
        this.processTurn();
    } else if (!this.isTpb()) {
        this.endTurn();
    }
};

BattleManager.getNextSubject = function() {
    for (;;) {
        const battler = this._actionBattlers.shift();
        if (!battler) {
            return null;
        }
        if (battler.isBattleMember() && battler.isAlive()) {
            return battler;
        }
    }
};

BattleManager.processTurn = function() {
    const subject = this._subject;
    const action = subject.currentAction();
    if (action) {
        action.prepare();
        if (action.isValid()) {
            this.startAction();
        }
        subject.removeCurrentAction();
    } else {
        this.endAction();
        this._subject = null;
    }
};

BattleManager.startAction = function() {
    const subject = this._subject;
    const action = subject.currentAction();
    const targets = action.makeTargets();
    this._phase = "action";
    this._action = action;
    this._targets = targets;
    subject.cancelMotionRefresh();
    subject.useItem(action.item());
    this._action.applyGlobal();
    this._logWindow.startAction(subject, action, targets);
};

BattleManager.endTurn = function() {
    this._phase = "turnEnd";
    this._preemptive = false;
    this._surprise = false;
};

BattleManager.updateTurnEnd = function() {
    if (this.isTpb()) {
        this.startTurn();
    } else {
        this.endAllBattlersTurn();
        this._phase = "start";
    }
};

Execute Actions

BattleManager.updateAction = function() {
    const target = this._targets.shift();
    if (target) {
        this.invokeAction(this._subject, target);
    } else {
        this.endAction();
    }
};

BattleManager.invokeAction = function(subject, target) {
    this._logWindow.push("pushBaseLine");
    if (Math.random() < this._action.itemCnt(target)) {
        this.invokeCounterAttack(subject, target);
    } else if (Math.random() < this._action.itemMrf(target)) {
        this.invokeMagicReflection(subject, target);
    } else {
        this.invokeNormalAction(subject, target);
    }
    subject.setLastTarget(target);
    this._logWindow.push("popBaseLine");
};

BattleManager.endAction = function() {
    this._logWindow.endAction(this._subject);
    this._phase = "turn";
    if (this._subject.numActions() === 0) {
        this.endBattlerActions(this._subject);
        this._subject = null;
    }
};

Summary

That's all for now. I hope this can help you grasp these basic knowledge. For those thoroughly comprehending the essence of the default RMMZ turn based battle flow implementations, feel free to correct me if there's anything wrong

For those wanting to have a solid understanding to the default RMMZ turn based battle flow implementations, I might open a more advanced topic for that later

Note: I'm going to use a wolf as an example and Imma show two ways to do this.

1. You need a actor who is a wolf and one who is Billy.
2. You need 1 variable that equals to Billy's EXP
3. You need 1 variable that equals to Wolf's EXP
4. Go to Control Variable
5. Go to game data <= If you have VX, skip this step and go to step 6
6. Go to actor
7. Go to the right, you should see level
8. Change it to EXP
9. It should look like this: Control Variables: [Var ID: Billy's EXP] = [billy]'s EXP

Pick the correct common event and BAM! You're done. 

1. Create a skill called "Wolf Transformation" (or anything you like)
2. Create a skill called "Wolf Transformation OFF"(or anything you like)

Any Questions? 

Brief description:  Have you ever watched a movie and seen how the credits pop up as the opening action scene plays out?  People are talking, fighting, doing all the movie things, but the credits appear and vanish along the way without disturbing the flow of action.  It's become such a common thing that movie critics actually criticize films that don't do their opening credits in this way.  This method will allow you to have that in your game without scripts or even a lot of special skill!

Requirements:  Obviously, you will need RPGMaker VX Ace (this should also work with everything but MZ as it only requires that you have access to the built in battle animations tab). Beyond that, you will need a simple photo editing software like Photoshop. I use GIMP because it's free and relatively simple to use.  You can technically do this with paint, but if you do, you will need to use another service to make the background transparent.  Before I discovered GIMP, I used lunapic as it's free and all online.  This is inferior to GIMP in my opinion, but it has the advantage of not requiring the download of a frankly massive program.

TL;DR:  You need an RPGMaker that has the animation tab (so any except for MZ) and you need a way to edit pictures while keeping them transparent.

Step 1; The Credit:

To begin, we need to take a random base from the animations folder of the RTP.  We're not actually going to change it, but rather, we're going to use it as a template.  I used Thunder4 because it's one of the larger bases with room for 25 animation panels.  I advise making a copy and pasting it into another folder, then working on the copy so that you don't accidentally overwrite the base picture.

Once you have it loaded up in your editor, erase everything so that the only thing left is the transparent background, As shown here:

Choose a small corner of the template then, and insert the text you want!  Don't worry about it being more than one animation panel.  It probably will be larger than one, depending on how much you have to type.  For my test case, I used a simple "A Game By Aslanemperor"

Save, export, or whatever you need to do.  Take any extra steps you may need to make the image transparent.  This is standard with GIMP, and I hear that Photoshop makes this pretty easy as well.  Once this is done, simply import this into your game using the built in Resource manager in RPGMaker.

Step Two; The Animation:

This part can get a little time consuming, but is still VERY simple.  My example took up two panels worth of room on the template (out of a max of 25).  As such, I took those two panels, and set them side by side over where I wanted them to go.  The animation system makes this very easy as everything is designed to lock neatly into place, so as long as you pay attention, it will be a simple matter to make everything look good.  Now we figure how long you want your credit to show itself, and where you want it on the screen.  For this example, I placed mine directly in the center.

When you're putting together your frames, keep timing in mind.  1 second is equal to roughly 30 animation frames.  Because of this, I set up the fade in to last through the first 26 frames, then had it hold solid for another 45, followed by a more rapid 15 frame fade out.

I did this by right clicking each individual panel and adjusting the "Opacity" number.  Because I wanted this to be close to a full second of fade in, I added 10 points to the value on every frame, making it go fully Opaque at frame 26, with a value of 255.  This is why it can be a bit time consuming.  Once you know what you're doing, however, it doesn't take long to put these together.  It took me just over 5 minutes to put everything for this animation together.

You'll notice that there's a box for the animation beyond just the scope of the target.  That box represents your screen.  Depending on where you want this to show up on the screen, that's where you'll place your animation box.  For instance, if you align it with the top left of that box, it will show up on the top left corner of the screen.

Step Three; Implementation:

So, you've made your "Credits" animation, and you're ready to place it.  The way I did it, was to have an event along the path the player has to follow, and when they walk over that area, it triggers the credit animation.  I set the animation to be centered on the player.  This way, it keeps on showing in the area I want as he walks:

Don't forget when making your event that you want to set it to end after the player has walked past it.  Also, DO NOT click for it to wait if you want your character to continue doing things while this shows.

Conclusion:

So, I found this entire process to be extremely easy, and can be done with things that anyone has access to (you can even manage this with just paint and a web browser).  It's a unique way to put your credits into your game without a clunky opening video (which usually requires some sort of video editing software).  If you have any questions, or you know an easier way to pull this off, I'm happy to hear it.  I hope this helps someone!

• One for texts like dialogs and terms in menus
• And another for numbers like HP, MP, time, money, etc

First you must copy the font files to your project's fonts folder.

To change the font of text before or after a dialog box, execute this code via the Script (Last Page) event command:

FontManager._urls["rmmz-mainfont"]="";
FontManager._states["rmmz-mainfont"]="";
FontManager.load("rmmz-mainfont","MyPersonalizedFont.ttf");

Replace MyPersonalizedFont.ttf with the name of the copied font in the folder, enclosed in quotation marks.

To restore the font of the texts to the one defined in the database, use the following command without changing anything:

FontManager._urls["rmmz-mainfont"]="";
FontManager._states["rmmz-mainfont"]="";
FontManager.load("rmmz-mainfont",$dataSystem.advanced.mainFontFilename);

To change the font of the numbers, which are likely to be less used, the command is similar:

FontManager._urls["rmmz-numberfont"]="";
FontManager._states["rmmz-numberfont"]="";
FontManager.load("rmmz-numberfont","MyPersonalizedFont.ttf");

To restore the font of the texts to the one defined in the database, use the following command without changing anything:

FontManager._urls["rmmz-numberfont"]="";
FontManager._states["rmmz-numberfont"]="";
FontManager.load("rmmz-numberfont",$dataSystem.advanced.numberFontFilename);

To understand, the _urls and _states objects serve to memorize the loaded fonts, so it is necessary to delete them to reload the new fonts.

If you prefer a simple plugin ready to work follow this link:

https://github.com/BossRpg/RMMZ-SimpleFontManager

First download the program through this link:

F4Enabled=1

F5Enabled=1

F12Enabled=1

Fullscreen=1

Icondefault=1

Hope it can help pepople using this engine :)

Parallax Mapping Videotutorial

Anyways, I'm just reposting this as I had a local copy and I remembered that a lot of the previous links to 'script call master lists' were broken when this site and the Degica one upgraded software. So, here it is: (I'm too lazy to reformat it )

Variables
$game_variables[n]
Switches
$game_switches[n]
Conditional Branch
if #something
#something
else
#something
end
Show Picture
screen.pictures[index].show(file_name, upperleft/center, x, y, x zoom, y zoom, opacity, blend type)
Move Picture
screen.pictures[n].move(0/1 (top left or center), x, y, zoom1, zoom2, opacity, blend type (0,1, 2), wait)
Picture Tone
screen.pictures[n].start_tone_change(Tone.new(0, 0, 0, 0), wait)
Looping
For
#something
end
Move Event
move_route = RPG::MoveRoute.new
move_route.repeat = false
move_route.skippable = true
m = RPG::MoveCommand.new
m.code = 45 #The List of M Code can be found over Game_Character, this current m.code is call script
m.parameters = ["script call here"]
move_route.list.insert(0,m.clone)
$game_player.force_move_route(move_route)
Transfer Event Location
$game_map.events[id].moveto(new_x, new_y)
Transfer Player
$game_player.reserve_transfer(map_id, x, y, direction)
Screen Tint
t = Tone.new(red,green,blue, gray)
screen.start_tone_change(t, duration)
Shake Screen
@params = []
@params[0] = power or $game_variables[x]
@params[1] = speed or $game_variables[y]
@params[2] = duration or $game_variables[z]
Note: (Neonblack and Fomar0153 found this glitch!)
The shake screen has an option in the editor where you can add a "wait" or not. But the glitch involves that it will wait no matter what. But it will only wait a number of frames equal to whatever the speed is set to the default option. For example, the setting is 5 power, 5 speed, 60 frames, and wait. It will wait for 5 frames, no matter what.
 
Call Common Event:
 
$game_temp.reserve_common_event(id)
Play SE/ME/BGS/BGM:
 
RPG::SE.new("SE Name", volume, pitch).play
RPG::ME.new("ME Name", volume, pitch).play
RPG::BGS.new("BGS Name", volume, pitch).play
RPG::BGM.new("BGM Name", volume, pitch).play
Show Text:
 
$game_message.add("Text")
Gain/lose Item:
 
$game_party.gain_item($data_items[id], amount)
$game_party.lose_item($data_items[id], amount)
(For weapons/armor use $data_weapons or $data_armors in place of $data_items.)

Gather Followers:
 
$game_player.followers.gather
Change Player Followers:
 
$game_player.followers.visible = true or false
Erase Event:
 
$game_map.events[event_id].erase
Some conditional script calls to add to Celianna's:
Button pressing
 
Input.repeat?:)A)
Input.press?:)A)
Movement
 
$game_player.dash?
$game_player.jumping?
$game_map.events[event_id].moving?
$game_map.events[event_id].jumping?
Location
 
$game_map.events[event_id].x
$game_map.events[event_id].y
$game_player.x
$game_player.y
Remove Actor
 
$game_party.remove_actor(actor_id)
Add Actor
 
$game_party.add_actor(actor_id)
Remove Party Member from position (where x = party position. 0 = 1st member, 1 = 2nd member, etc.)
 
m = $game_party.members
$game_party.remove_actor(m[x].id)
If you ever wanted to add every item/skills/weapons for debugging purpose (or something else?) it can be kind of tedious to add them all if you have alot. This small script call will help immensely:
 
$data_items.each { |i|
next if i.nil? or i.name == ""
$game_party.gain_item(i, 99)
}
Of course, if you want you can change $data_items to $data_weapons or something else and the amount you want.

When checking for input triggers/pressing you can actually shorten that a bit:
 
Input.trigger?:)CTRL)
There is no need to write Input::CTRL anymore.

To get the leader of the party you can do this:
 
$game_party.leader
Gain/lose gold:
 
$game_party.gain_gold(amount)
$game_party.lose_gold(amount)
Check for current max gold:
 
$game_party.max_gold
Get map id and name:
 
$game_map.map_id
$game_map.name
To correct the screen shake bug thing do the following at Game_Interpreter:
 
def command_225
screen.start_shake(@params[0], @params[1], @params[2])
wait(@params[2]) if @params[2]
end
Now it will wait the right amount of frames and not 5.
 
$game_player.region_id == n
$game_map.events[event_id].region_id == n
Show Choices
 
params = []
choices = []
choices.push("choice 1")
choices.push("choice 2")
params.push(choices)
params.push(0/1/2 this part is where you press cancel and which choice to default)
setup_choices(params)
It is pretty easy to fake the When [**] command (402).
The definition is just

 
command_skip if @branch[@indent] != @params[0]
Where @params stores the choice number for that specific branch (0, 1, 2, ... )

So all you have to do is replace @params[0] with an integer

 
if @branch[@indent] == 0
# branch for first choice
elsif @branch[@indent] == 1
# branch for second choice
end
Editor line continuation
$game_variables[12] = ($game_variables[6] ==
$game_variables[10]) && ($game_variables[7] == $game_variables[11]) &&
($game_variables[8] == $game_variables[10]) &&
($game_variables[9] == $game_variables[11])
change the text dialog background:
$game_message.background = 1 #0 = default blue, 1 = dim, 2 = transparent
 
Equip weapon
$game_actors[1].change_equip(0,$data_weapons[1])
the 0 value in the above code snippet can have the following values:
0 = weapon
1 = shield
2 = headgear
3 = body-gear (armor)
4 = accessory
 
 
Transfer player
$game_player.reserve_transfer(map_id, x, y, $game_player.direction)
$game_player.followers.visible = true or false
Audio.se_play(name, volume, pitch)
Is Weapon Equipped?
$game_actors[actor id].weapons.include?($data_weapons[weapon id])
Access self switches
$game_self_switches[[mapid, eventid, 'A']] = true

Make sure you use [[...]] and not just [...]
Get Currency Unit
$data_system.currency_unit
For any equipment, you can use this:
  right_hand = $game_actors[actor_id].equips[0]
  left_hand = $game_actors[actor_id].equips[1]
To get the items. Replace the index in equips for the item you're looking for (0 = right hand, 1 = left hand, 2 = head, 3 = body, 4 = accessory, provided you're not using any scripts that change that).
 
You can check their types with:
  if right_hand.is_a?(RPG::Weapon)
    # do something
  elsif right_hand.is_a?(RPG::Armor)
   # do something else
  end
Or get their properties with with
  right_hand.id
  right_hand.name
  right_hand.icon_index
  right_hand.description
  # etc..
 i.e. if you want to check if you have a Prinny Gun equipped on your first weapon slot:
  right_hand = $game_actors[actor_id].equips[0]
  if !right_hand.nil? && right_hand.name.eql?("Prinny Gun")
    # Do something
  end
You don't even need to keep track of the IDs, really (unless you want to, for some reason). If there's no way to not have a weapon equipped in your game, you can also take out the ".nil?" check.
 
Showing a text box with pure script
 
$game_message.position = X
0 -Top
1- Middle
2- Bottom

$game_message.background = X
0 - Normal
1 - Faded
2 - Transparent
 
$game_message.face_name = 'Actor1' <- Name of the graphic plate
$game_message.face_index = 0 <- Position in the plate of the face you are using.
 
$game_message.face_name = 'Actor1'
$game_message.face_index = 0
$game_message.background = 2
$game_message.position = 0
$game_message.add("Text")
$game_player.passable?(x, y, d) and $game_map.events[event_id].passable?(x, y, d)

are extensions to this that do a little more detailed checking.

$game_map.passable? only tells you whether you can leave one tile in the direction of the other. The player and event versions take it further and tell you if you can leave that tile in the direction of the other AND if you can enter the other tile from the tile you're on now (for example, if you are facing right and the tile in front of you is the edge of a cliff that is higher than you - $game_map.passable? would tell you that you CAN step right from the current tile. But $game_player.passable? would tell you that you could not move onto the next tile from the left). It also looks to see if there is an event on your target tile which would stop you going there, but $game_map.passable? would not tell you that.
Check HP
You can check an actor's current hp with:
 
$game_actors[x].hp
Or the leader's current hp:
 
$game_party.leader.hp
Or a member of the party:
 
$game_party.members[x].hp
Check Items
Here's the script from Game_Interpreter that places the quantity of an item into a variable:
 
$game_party.item_number($data_items[param1])
So you'd just change param1 to the item id you're interested in, and add your condition around it:
 
if $game_party.item_number($data_items[32]) == 15
Checking how many of a particular type of weapon or armor is very similar:
 
$game_party.item_number($data_weapons[param1])
$game_party.item_number($data_armors[param1])
Access Event by Name
# Code by Filip H.F. "FiXato" Slagter
# Place this under Materials and above Main Process and before any scripts that would make use of it.
# Allows you to also use Game Switch *names* instead of just IDs in $game_switches[] calls.
class Game_Switches
# Overload the [] method so we can also call switches by their name, for instance:
# $game_switches['my switch']
alias_method :find_by_name, :[]
def [](switch)
switch_id = (switch.kind_of?(String) ? $data_system.switches.find_index(switch) : switch)
find_by_name(switch_id)
end
 
# Overload the []= method so we can also set switches by their name, for instance
# $game_switches['my switch'] = true
alias_method :set_by_name, :[]=
def []=(switch,value)
switch_id = (switch.kind_of?(String) ? $data_system.switches.find_index(switch) : switch)
set_by_name(switch_id, value)
end
end

    Recover All for your entire party:

@params = [0, 0]
command_314
 
 
 
 
Show a named animation (in this case 'Sleep') for the player and wait for it to end:
animation_name = 'Sleep'
animation_id = $data_animations.find_index{|ani|ani && ani.name == animation_name}
@params = [-1, animation_id, true]
command_212
Move_Route_Turn
$game_map.events[eventid].set_direction(#)
2 = down, 4 = left, 6 = right, 8 = up.
 
Event Ballon
$game_map.events[eventid].balloon_id = # where # is the row of the balloon spritesheet you want to show (I think the top row is 1, not 0), and eventid is the id of the event
Player Facing
$game_player.direction

2 = down
4 = left
6 = right
8 = up
If ActorX or ActorY is in party
$game_party.members.include?($game_actors[X]) or $game_party.members.include?($game_actors[Y])
Or
$game_party.members.any? {|a| [X,Y].include?(a.id)}
Change Actor Graphic
actor.set_graphic(character_name, character_index, face_name, face_index)
Use Item
$game_actors[id].use_item($data_items[x])
$game_party.leader.use_item($data_items[x])
$game_party.members[index].use_item($data_items[x])
Show Battle Animation
Show Battle Animation:

    @enemy_index = 0
    @animation_id = 1
     
    iterate_enemy_index(@enemy_index) do |e|
    e.animation_id = @animation_id if e.alive?
    end

That will show a battle animation.
 
Shop Processing
# goods = [[type, id, price_override_flag(, price)]] Ex:
goods = [[0,1,1,25],[0,2,0]]
SceneManager.call(Scene_Shop)
SceneManager.scene.prepare(goods, true)
Or
goods = []
for id in 1..20
goods.push([0, id, 0])
end
SceneManager.call(Scene_Shop)
SceneManager.scene.prepare(goods, true)
 
Store Actor Level
$game_variables[x] = $game_actors[id].level
Control Weather
$game_map.screen.change_weather(type, power, duration)
where type is :none, :rain, :storm, or :snow, and power and duration are what you would have set the sliders to on the box.

followed by Wait X Frames if you want it to halt processing until the weather is set.
Move Set Route -> Change Graphic
$game_map.events[id].set_graphic("character_name", character_index)
id is the id of the event you want to change.
"character_name" is the name of the graphic file you want to change to (make sure to keep the quotation marks).
character_index is the index on the character sheet (it starts counting at 0).

This guide was inspired, and re-written from an old guide I use, or used to use. I'm re-writing it as it doesn't fit in with all the new features of Ace. If you would like to check it out, here it is! http://www.rpgmakerv...showtopic=47252

Table of Contents

1. EXP Curve

2. Parameter Curves

3. Creating Enemies

- Basic Enemies

- Bosses

4. Skills

5. Weapons, Armor, and Items

6. Money

7. Last Words

This is pretty simple, what it does is change how fast, or slow you want your class to level up. What I normally do is leave this alone, but feel free to change it how you want! I'll do a little walk through of what each slider does.

Base Value: It does what it says! It is the "base" number of EXP it will take to level up. Say you slide everything else down, and leave this one at 30. It will take 30 EXP to level up.

Extra Value:This is basically just like the base value. What it does is just add on to what you have for your base value. Say again, we set the base value at 30, and the extra value at 10, it would then take 40 EXP to level up. It just adds it up.

Acceleration A: This speeds up or slows down how much EXP it will take to level up.

Acceleration B: Does the same thing as Acceleration A.

All these really do is change how much of a certain parameter to will have at a certain level. There are two main ways to change these. The first one is to just drag a line or curve you think is good, I don't recommend doing this. The second one is clicking on Generate Curve. Here is one rule I always use. For health, add two zeros on for level 99. For the rest only add one. I will walk you though all of them.

MHP: (Max Health Points) This is how much health you will have in total at a certain level. Say you set your level one health to 57, set your level 99 to 5700. For this one you add two zeros.

MMP: (Max Magic Points) This is how much magic you will have in total at a certain level. If you set your magic to 36 at level one, set your level 99 to 360. From here and the rest you add one zero.

ATK: (Attack) This is how much physical damage you can do at a certain level.

DEF: (Defense) This is how much physical damage you can take at a certain level.

MAT: (Magic Attack) This is how much magical damage you can do at a certain level.

MDF: (Magic Defence) This is how much magical damage you can take at a certain level.

AGI: (Agility) This is how fast you are. It controls if you miss or not, and if you have certain scripts installed, how fast you attack.

LUK: (Luck) This controls if you will contract a state or not. The higher your luck, the lower chance you have of getting a certain state, such as poison.

When making enemies, it's kind of hard to figure out how much health they will need so they won't be too easy or too hard to kill. It goes the same way for the rest of the stats. I'll give a quick walk through of what you can do to solve that problem! It is also hard to tell what level you are when you will need to kill them. So play every once in a while to tell. Remember to always check if the enemy is too strong with the Battle Test after. Also, when I make enemies, I don't just make them. I make them as I go in my game! If you make them right from the start, you don't know if they will be too strong, also you might not use most of them.

Normal Enemy

MHP: Double the player's health.

MMP: Depends on the skills the enemy has. If it's a magic user, like a mage, give the same amount or double the enemies health. If it isn't a magic user, I recommend either none, or half of the enemies health.

ATK: Around 30% less than the player's attack if you are using low health and such as I am. (Using 15 health at level one.) If you are using stuff like 250 health at level one, keep it the same as the player's. If it is a magic user, I recommend half the player's attack.

DEF: Same as the player.

MAT: If it's a magic user, Around 30% less than the player's attack, or magic attack. (Which one is higher.) If it isn't, either none or half of the player's.

MDF: Same as the player.

AGI: I would recommend around one or two points higher than the player's agility.

LUK: Same as players.

Dungeon Enemy

MHP: Triple the player's Health.

MMP: Depends on the skills the enemy has. If it's a magic user, like a mage, give the same amount or double the enemies health. If it isn't a magic user, I recommend either none, or half of the enemies health.

ATK: Same as the player, or one point higher. If it is a magic user, around 30% higher than the player's attack.

DEF: Around 10% higher.

MAT: If it's a magic user, the same as the player's attack, or magic attack. (Which one is higher.) If it isn't, either none or half of the player's.

MDF: Around 10% higher.

AGI: Same as the player's or one point less if you use certain scripts.

LUK: Same or two points higher than the player's.

Now, for making the experience they give you is kind of difficult. What I did was keep changing it until I found a decent amount. It depends on your EXP curve you set. I left mine how it was, so the first enemy I encountered has the EXP of 8. Then for the next enemy, you have to see what level you encounter it. Say I encounter the next enemy at a level of 3. I sat that enemies EXP to 14. For the gold, I use half the amount of the EXP. So for 14 EXP, I give 7 gold.

For bosses it is pretty much the same as basic enemies, but with higher stats. For the experience, I give them a lot. Use the same technique as the one for basic enemies, but double the value of the experience. Then for the gold, give half of the amount from the experience.

MHP: 5 times higher than the player's.

For All the Rest: Times it by 1.5 higher (Or 150%) than the player's.

The skills are always one thing I've hated doing. Even after finding a clever way of doing the skills, I stikk hate doing it, but that is my opinion. You could love doing it! But either way, I'll share my technic of how to make the skills.

The first thing you want to do, is decide how much Magic (Or Technical) Points you need it to be. To do that, decide how many skills you want the class to have. Say you want to have 20 skills. Use that, and divide it by 100, then you get 5. So that means, every 5 levels, that class will get a skill. So say your first skill will be at level 5. Go to the class and find out how many MMP you will have at level 5. Once you find out, divide it by 5. That is how much MP the skill will cost!

Now we move on to the damage, the rest is pretty self explanatory.

Type: Pretty easy, what does the spell do?

Element: What element is it?

Formula: This is wear the magic happens. Click on quick, for Base Value, set that as double of your ATK or MAT. (Depending on if it's a magic user or not.) Then for Physical and Magical it's pretty simple. If it is a physical skill, set the Physical to 100, if it is a magical skill, set the Magical at 100.

Variance: This is the range of damage. Say you leave it at 20. It will do between 20% higher or lower of what you set as your formula.

Critical: Does the skill have a chance to land a critical?

Alright, we've came a long way haven't we? Well we are almost done!

Let's move on, first to weapons. If it is a one handed weapon, it should be half of the player's attack. So if a player has an attack of 18, the weapon should be 9. If it is a two handed weapon, it should be 75% of the player's attack. If it is a dual wield weapon, it should be around 30% of the player's attack.

For armor, we have three parts. The body, head, and shield. All three pieces should offer a total of 50% defense. If your player doesn't want to use a shield, then take that off and have it offer a total of 35% defense to balance it out. The body armor should offer 25% defense, the head should offer 10%, and the shield should offer 15%.

Now for items, for now, I will just explain a healing potion. Potions for HP, it is a good idea to have the potion heal a little more than what the player actually has, for other classes as well. You should also make a potion for around every ten levels. Now, lets say you were making a potion for a level 10 player, with the HP of 198. You want the potion to heal 20% more than what you have. So for that, 39.6 is 198 of 20%. So you use 198, and round that up to 40. Then you add it, to get a total of 238. That would be how much it would heal.

Now we are moving on to money, how much will it cost to buy certain items? Will you have enough money at the time of the game?

This is pretty simple. For weapons and armor, the price should be around 10 to 15 times the amount of stats they have. Say you have a sword with 16 ATK, 6 AGI, and 2 LUK. add that up to 24, and times it around 10 to 15. I will use 10, so the price would be 240. For weapons/armor that have states or resit elements and such, they amount of the item should increase by around 25%.

For Inns, the should make the price of it fit in with the theme of the town/city. If it is a broken up town who just came out of a war, the price should be cheap. If it is the richest kingdom in the world, it should cost a lot.

For items, I'll again use a HP potion for example. The price should be half of what the potion does. If you have a HP potion that heals 500 HP, it should cost 250. As for other items, such as those that remove poison, or stun, they should cost around how important the state is. Something that cures poison should be cheaper than something that cures stone, while something that cures stone, should be cheaper than something that revives a character from death.

Now it is over! I really hope that this guide has helped. If you see any errors, or something that doesn't seem to be balanced to you let me know! I thank MrE for making the guide I used for more than a year now, and inspiring me to write an up-to-date one! Good luck on balancing your game, and have fun!

In the previous article, I went over the basics of MV tools. In this article, I’ll be going over the process of creating your own MV Tools.

Why Create Your Own?

MV Tools add extra shortcuts to the editor, and will pass the current project's path to the application that the user launches. The application could be a GUI application, or it could be a console-based application that simply performs some data processing using the current project's information.

It's mostly for user convenience, but it also makes your tool feel more official since it actually appears in the editor! Anyways, let's go through the process to creating your own MV Tool.

MV Tool Anatomy

MV Tools are actually quite simple:

• There’s an exe file
• There’s an “identification” folder.

And that’s really all there is to it.

Executable

Application

This is the executable that will be launched when you press the icon in the editor. It can’t be any name though; it must be one of the following:

• WindowBuilder.exe
• TilesetBuilder.exe
• SceneBuilder.exe

This is hardcoded into the editor, so it only expects one of these filenames. You can see it in the RPGMV.exe

Anyways for testing purposes, simply create a blank text file and rename it “WindowBuilder.exe”.

Identification

This what the editor uses to get information about your MV Tool. In this folder, there’s a file called “app” (no extension) and a folder called “toolbar” which basically holds a 32×32 pixel icon that will be displayed in the editor. The “app” file is just a text file that has three lines of text:

NAME
VERSION
DESCRIPTION

Anyways so let’s set up a sample “app” file and add an icon to the toolbar folder. You can just use notepad to create the “app” file, but make sure you have file extensions enabled in your file explorer.

Now, when you go and add it to the editor, it’ll find your tool with the details you entered

And finally, once you confirm, it will appear in your editor, like the official MV tools!

The hime app itself does nothing because it’s just an empty file called “WindowBuilder.exe”, but you can actually add any executable app to RPG Maker MV as long as it has the identification folder, and the exe is a valid name

For example, I went and added notepad++ to it, which is my text editor of choice that I use for all my MV plugin development and other programming

When you click on the notepad++ icon, the editor will launch notepad++, and it will actually open something

This is the Game.rpgproject file which sits in the base directory of your project folder! So basically RPG Maker MV sends the path to your project file to the application, which you can use to automatically load some data in the project for example.

Some Thoughts

So now you’ve learned how to create your own MV Tools. What can you do with it? Anything really. It’s just a regular application, so you can do whatever you can think of.

Of course, your application ideally should be able to run externally, but integrating it with the editor means that users who may not be as tech-savvy will be able to run your tool on their current project without having to go and open it from outside of the editor, which might not seem like that big of a deal but could be useful.

How To Make An Open-World RPG

*Required items* rpg maker MV | Alpha ABS| Everything else is optional and will be linked when used in the videos

THE GAME WE WILL BE MAKING

Welcome To The Island Of Hearth

Story

It was 10 decades ago when the portal opened and from

it evil so old, that only old and ancient magic

forgotten to the world can defeat It. Many have fallen

to this great new threat. Adventures from all over

the world have come to hearth looking for fame and glory.

But in the end. Only them who has protected Hearth for a

1000 years can protect it yet again. From evil old or

new they shall fall by their blades.

Your family has protected all of hearth for centuries

Now is no acceptation. Defeat the evil.

This new evil can only be defeated with the Eye of Gore

find and retrieve it. Then free the land once again.

But do not fear for even if you fall, your Ancestor

will take your place.

About

Open-world dungeon-crawling Zelda like Skyrim type RPG.

Classes

Noob -Starting off like everyone else

Adventure – You’ve earned the right to venture through the dungeons.

Warrior -You fancy a strong fighter

·        WarKnight – A warrior like no other in battle and war

Magi – You dabble in the Arcane arts

·        WarMage – You use your learning to devastate any battlefield

Thief – You don’t fight like the others but you get it done.

·        WarNinja – Using the shadows now one can see you coming in battle

features

Open-world

Explore the exciting Island of Hearth, discover the hidden mystery of the dungeons and the ancient evil.

Crafting

Craft potions, armor, and weapons. The best gears can only be crafted.

RPG Progression!

The more you use an action the better it comes. You can train different weapon types, armor, and skills. You can also add stat points as you level up!

Action Battle system

No waiting for turns, plunge yourself straight into the heat of battle.

Visible Gear

See what your character is wearing.

Endless loot!

Tones of loot from weapons to potions, spells, and other valuable items.

Mini-Games

Enjoy many mini-games from the casino in town to the other random game across the map.

Guilds

Four guilds to join, and rank up in with exclusive gear and benefits for joining.

Time Progression

Things happen as time pass.

• SETTING UP THE WORLD
  • LETS MAKE AN OPEN WORLD RPG DEARHEART EP 0
  • LETS MAKE AN OPEN WORLD RPG DEARHEART EP 1
  • LETS MAKE AN OPEN WORLD RPG DEARHEART EP 2
  • LETS MAKE AN OPEN WORLD RPG DEARHEART EP3

WATCH ME MAKE THE GAME!

Tutorial Made by: Soulpour777

Graphics: Moghunter's Master Demo

Q: I wanted to make my own simple animated title screen, but I don't have the knowledge to do so. I want to make my own way of making a Title Screen just like Moghunter's scripts, can you teach me?

This is basically the goal of this tutorial. Today, we're going to make our own Animated Title Screen! Awesome, right? Yayy! Before we start, we will need the following materials! Remember that I may add new materials as we go on to the tutorial.

Save them under your Titles1 folder. That is where we will all be putting our graphics in. Now that we have the necessary graphics needed, let's jump right into the scripting. Open your RPG Maker VX Ace and start a new project. I recommend making this in a fresh project so it won't cause any disruption on your project. Just to be safe

Now, once you created a new project, press F11 to go the Script Section. You can also click the Script Section Icon on your Ace's tool ribbon. Go to the Materials part on your script and create a new section below. This is where we are going to start our scripting. 

The things we need to do on our Title Screen are the following:

• Use our Game_Title as the title instead of the Default Game Title
• Make our background
• Make some images move

To begin with, start with this on your script:

class Scene_Title < Scene_Base
  alias :soul_animated_titlescreen_simple :start
  #--------------------------------------------------------------------------
  # * Start Processing
  #--------------------------------------------------------------------------
  def start
    soul_animated_titlescreen_simple
    create_grass_fog
    create_trees
  end
end 

What we did here was to create a class called Scene_Title inheriting its functions from Scene_Base. Instead of rewriting Scene_Title's method start, we created an alias. What is an alias? Alias simply means a new name for our method. We need to call the alias on that method as well, it is called Calling the Original Method. If you are wondering why there is a : sign on the alias, that is because : signed things are considered methods. You can also alias it this way if you want:

alias soul_animated_titlescreen_simple start

Does the alias need to be like that? Can't we make our own alias?

No. It is not necessary. You can alias it with any name you want.

If you are wondering what create_grass_fog and create_trees are, that is what we will define next.

We need to overwrite our create_background from the original Scene_Title, so do this:

  #--------------------------------------------------------------------------
  # * Create Background
  #--------------------------------------------------------------------------
  def create_background
      @background = Plane.new
      @background.bitmap = Cache.title1("Background")
      @background.z = 0
  end 

This time, we changed the original things inside the create_background method. We created a new Plane object and made a bitmap whose name is the "Background" which we just had saved awhile ago. Now, let me explain a few things here (also from the help file to be more accurate of what they actually mean):

Planes

  #--------------------------------------------------------------------------
  # * Create Grass
  #--------------------------------------------------------------------------  
  def create_grass_fog
    @grass_fog = Plane.new
    @grass_fog.bitmap = Cache.title1("Fog0")
    @grass_fog.z = 3
  end
  #--------------------------------------------------------------------------
  # * Create Trees
  #--------------------------------------------------------------------------  
  def create_trees
    @trees = Plane.new
    @trees.bitmap = Cache.title1("Fog1")
    @trees.z = 2
  end

  #--------------------------------------------------------------------------
  # * Update Frame (Basic)
  #--------------------------------------------------------------------------
  def update_basic
    Graphics.update
    Input.update
    update_all_windows
    @grass_fog.ox += 3
    @trees.ox += 1
  end   

Q: I advance read the Sprite Class and it says it also has ox. Can't we just use sprites instead?

A: Good question, isn't it? Well the reason for that is because the Sprite won't replicate itself or rather does not work like a Parallax. When you use Planes, it works like a parallax and repeats itself, unlike sprites, they don't when they scroll.

So what we did here is: we made the Fog0 scroll horizontally by 3 and the trees by 1. We created it in update_basic because it works every frame.

Moving on, we need to draw our Game's Title, so we need to overwrite the draw_game_title. On your script, do this:

  #--------------------------------------------------------------------------
  # * Draw Game Title
  #--------------------------------------------------------------------------
  def draw_game_title
    @game_title = Sprite.new
    @game_title.bitmap = Cache.title1("Game_Title")
    @game_title.z = 4
    center_sprite(@game_title)
    @game_title.y = Graphics.height / 2
  end 

And lastly, we need to dispose every image that we made here. So, on your script, do this:

Let me explain what we did here on the dispose method.

  #--------------------------------------------------------------------------
  # * Free Background
  #--------------------------------------------------------------------------
  def dispose_background; end  

#==============================================================================
# ** Scene_Title
#------------------------------------------------------------------------------
#  This class performs the title screen processing.
#==============================================================================

class Scene_Title < Scene_Base
  alias :soul_animated_titlescreen_simple :start
  #--------------------------------------------------------------------------
  # * Start Processing
  #--------------------------------------------------------------------------
  def start
    soul_animated_titlescreen_simple
    create_grass_fog
    create_trees
  end
  #--------------------------------------------------------------------------
  # * Termination Processing
  #--------------------------------------------------------------------------
  def terminate
    super
    dispose_background
    dispose_all_used_graphics
  end  
  #--------------------------------------------------------------------------
  # * Create Background
  #--------------------------------------------------------------------------
  def create_background
      @background = Plane.new
      @background.bitmap = Cache.title1("Background")
      @background.z = 0
  end
  #--------------------------------------------------------------------------
  # * Create Grass
  #--------------------------------------------------------------------------  
  def create_grass_fog
    @grass_fog = Plane.new
    @grass_fog.bitmap = Cache.title1("Fog0")
    @grass_fog.z = 3
  end
  #--------------------------------------------------------------------------
  # * Create Trees
  #--------------------------------------------------------------------------  
  def create_trees
    @trees = Plane.new
    @trees.bitmap = Cache.title1("Fog1")
    @trees.z = 2
  end
  #--------------------------------------------------------------------------
  # * Update Frame (Basic)
  #--------------------------------------------------------------------------
  def update_basic
    Graphics.update
    Input.update
    update_all_windows
    @grass_fog.ox += 3
    @trees.ox += 1
  end    
  #--------------------------------------------------------------------------
  # * Draw Game Title
  #--------------------------------------------------------------------------
  def draw_game_title
    @game_title = Sprite.new
    @game_title.bitmap = Cache.title1("Game_Title")
    @game_title.z = 4
    center_sprite(@game_title)
    @game_title.y = Graphics.height / 2
  end
  #--------------------------------------------------------------------------
  # * Free Background
  #--------------------------------------------------------------------------
  def dispose_background; end  
  #--------------------------------------------------------------------------
  # * Free All Graphics
  #--------------------------------------------------------------------------
  def dispose_all_used_graphics
    @background.bitmap.dispose
    @background.dispose
    @grass_fog.bitmap.dispose
    @grass_fog.dispose
    @trees.bitmap.dispose
    @trees.dispose
    @game_title.bitmap.dispose
    @game_title.dispose
  end
end

Go ahead and test it!

A: Definitely yes! Make sure to create them in a method, call them from the start method. Make sure they're instance variables too! Also, don't forget to dispose them Organize your Plane's z well too.

@image_i_like_to_scroll.oy += value

Welcome to the wonderful guide of bosses! You must be wondering what bosses are, right?

Bosses are special types of enemies that spice up any types of games whether it's rpg, shooting, action, etc.

What you want are bosses for an rpg, am I right? Let me give you a guide to better and badder bosses.

I will update this guide when I find more stuff to add to this list.

Section A: Types of Bosses

There a many types of bosses in the story that act according to the situation. Take for example the "Final Fantasy" series repetitive and well known boss, Gilgamesh. Gilgamesh is a boss that appears as a goofy, stupid, prideful, but yet one of the most interesting bosses except for Kefka. Anyways Gilgamesh appears in Final Fantasy I, V, VI, and XII as bosses while in the other series as summonings. Gilgamesh always tries to make the scenes comical or serious and fighting him is very challenging except in FFV of course.

Another repetitive boss would be the Omega Weapon, another type of boss in the FF series that appears as a secret boss. Secret bosses are bosses that are way beyond harder than the final bosses. They consist of powerful moves that can KO characters in a single hit or constantly hit them with status attacks. In the end when you defeat the secret boss, the rewards are little or always worth it.

There are the normal bosses, who in-game are to challenge characters every time they near a part of the story or close to finishing a dungeon. These types of bosses are to halt the player from progressing any further into the story. These types of bosses act like a log in front of a gold flower that you manage to find in the woods and you have only a chisel to cut your way past it.

Then there are the Final Bosses which are the bosses at the end of the story when the main character is close to completing his/her objective in the story. Exdeath in FFV was the final boss when Bartz and the party enter the void and which their objective was to beat him to save the world as in almost every FF game. Final Bosses are to be tough end game bosses and not a boss that gets killed in one shot (Sega CD Zelda). Final Bosses are to be the cliche and tell the player that it is time to meet their match or be ffed in the balls for punishment. They give the player a sense of accomplishment when they face the tough boss as they complete the game.

Finally, there are the joke bosses. Literally they are a joke to the game like Seigfried, in FFVI who you fight on the Phantom Train that only dealt one damage and had 100 HP. These types of bosses are for entertainment purposes only and are to be beaten into a pulp instantly.

Section B: The Many Types of Bosses

Every boss must be different or the game will be considerably meaningless in every way. How bosses should act to how they look like it would be boring to fight a boss named "Soldier" and have him look like a soldier who looks frail and thin like "Angelina Jolie" (lulz). Bosses have to have their own name like "Dawnshredder" or "Barnum's Ultimate Grill Cat Titan" something like that and actually make them look dangerous and awesome.

Bosses also must have personalities and not act like a robot unless they are actually are a robot type boss which I will find acceptable. If bosses have no emotion then it is not unique, it's just another Sephiroth wanna be just waiting in the shadows to be trolling everyone in the game. Take for example Kefka from FFVI and the Prinny Overlord from Disagaea, both are unique because one is barking mad and almost became a god while the other is a giant penguin with knives and bombs that is a walking bomb. These bosses have emotions that are unique from the stereotypical serious, momma-boy bosses and do actions that are not at all robotic.

Religious Bosses or myth-type bosses are also great additions to any game. These bosses represent a religion or a story within the world that the characters fight in like "God". These bosses are to give reason to why something is in the game or a cause to a curse to a town.

Section C: Boss Battles

Boss battles as I explained are to be challenging and a stop gape for players when they go through the game. Bosses have high hp, mp, attack, defense, etc. Their stats are triple of the the players and his/her party also they are difficult to beat because of the array of attacks the bosses have. Bosses must BE difficult to be difficult to beat and not one hit death unless they are joke bosses. A good example of that is of course Sega CD's Zelda.

Bosses must have special attacks that characters and other monsters don't have to make the battle hard, also they must be a constant nuisance to the parties stats as well like applying poison, blind, confusion, etc. Omega Weapon from the FF series had an attack that could kill, petrify, blind, etc. if it hit one of your characters. Also in a boss battle, bosses have minions that they have with them in battle that can prove an annoyance. When implementing a battle, try having the enemies come back from the dead some turns later or have the boss call reinforcements when he/she reaches a certain hp level.

Final Boss battles are a big one because these battles are a test of one's meddle of what the player has gone through in the entire game. In the FF series V and VI, both final bosses had multiple bodies or battles within the final battle. Body parts that are connected to the boss that have it's own attacks and also high hp can be challenging to a player. Also add something to the boss when it dies like a suicide move or a move that can deal damage to the players party when it dies.

Also sometimes you want to add flair or difficulty to boss battles, for example the dragon Shinryuu in FFV in the rift can change elements in battle, but the downside was it's type was always dragon making it susceptible to the Jump attack. By giving bosses elements can asses what the player does to the boss in battle. Also have a time and point when the boss is invincible for a certain period of time and you must defeat his minions to make the boss vunerable again.

Also add some dialog during the fight as well to make the battle more energetic or sad either way to change the flow of battle. Also I suggest for some bosses to use transformations to throw off the player completely. One more thing is to try to limit player moves and actions in battle like banning their magic or skills so the player would have a hard time dealing with the boss, don't make it permanent though or it would be just a chore to beat the boss with only attack. Buffing up the boss is a good idea too so the player can focus on healing and buffing up their characters as well.

Section D: Lewt!

Bosses all have loot and good loot as well. Play WoW and you'll see that bosses drop gear, weapons, or items unattainable anywhere else. Some bosses drop keys or an item that allows the player to go further into the story and allow them to see beyond the stuck point where the player is at. If you don't create loot for the player then the player will be disappointed that they got no lewt! (Not really lulz.)

Section E: Example

Here are some examples of some G-R-E-A-T Boss Battles from different RPG games:

Seymour FFX (Badass music and boss fight :3:

I hope all of you enjoyed this guide and take into consideration into making a kick-ass boss battle!

After this tutorial you should be ready to make your first game and beyond.

After we cover the basics and advance stuff we will be moving on to plugins. Stay tuned.

Tutorial Playlist - RPG Maker MV

RPG Maker MV Video Tutorial EP 1: Introduction

RPG Maker MV Video Tutorial EP 2: Interface

RPG Maker MV Video Tutorial EP 3: Maps and Regions

RPG Maker MV Video Tutorial EP 4: Events PT 1

Alpha ABS Tutorial Playlist - Alpha ABS Tutorials

RPG Maker MV Alpha ABS Tutorial EP1: Installation and configuration
RPG Maker MV Alpha ABS Tutorial EP2:Skills Items and Weapon Overview

RPG Maker MV Alpha ABS Tutorial EP3: Skill Setup

RPG Maker MV Alpha ABS Tutorial EP4: Weapon Setup

RPG Maker MV Alpha ABS Tutorial EP5: Item Setup

RPG Maker MV Housing system Tutorial snippet - Snippets

So far i will be covering all these topics, but i know there's a lot missing from the list ,
that's where you guys come in, if you want me to do a tutorial on something, post it here, pm me, or leave me a message on YouTube and I'll add it to the list.

@CristorcusHelix, no, the Class System script does not interfere.

Now, for simplicity's sake, I won't throw my entire script in the fray, just the pieces needed to get this working.

Below is the command that goes under COMMANDS:

    COMMANDS =[
      :currencies,   # Opens the currency window.
    ] # Do not remove this.

Below is the hash for all custom commands, which is what Currencies will be. Note that you can change what the menu command appears text wise by changing the Display Name (be sure to keep the quotes and comma there!), but don't change the command or the handler method.

CUSTOM_COMMANDS ={
    # :command => ["Display Name",  ShowSwitch, EnableSwitch,  Handler Method],
      :currencies => [  "Currencies",        0,        0, :command_currencies],
      :debug      => [       "Debug",        0,        0,      :command_debug],
      :shop       => [        "Shop",        0,        0,       :command_shop],
      :gogototori => [   "Synthesis",        0,        0,     :command_totori],
      :grathnode  => [   "Grathnode",        0,        0,    :command_install],
    } # Do not remove this.
    
  end # MENU
end # YEA

The handler method will go below the Scene_Menu portion at the bottom of the script. Be careful to copy and paste the code correctly.

  
  #--------------------------------------------------------------------------
  # new method: currencies
  #--------------------------------------------------------------------------
  def command_currencies
    return unless $imported['Clstn_Currencies']    
    SceneManager.call(Scene_Currencies)
  end
  

And that should do it. If there's any issue, give me a ring.

i have no idea how to use variables either, it that’s important.

So here is my latest scheme. It is my hope to start from the very beginning and go all the way up to RegEXP (as that was my ultimate goal when I started scripting).

Edit: Not on holidays anymore, but still continue when I can...

Tut 01 ~ Variables

Tut 02 ~ Variable Types and IF Statements

Tut 03 ~ Methods & Functions

Tut 04 ~ Method Arguments

Tut 05 ~ Boolean Operators

Tut 06 ~ The 'Return' Keyword

Tut 07 ~ Playing Audio (BGM, BGS, ME, SE)

Tut 08 ~ Arrays

Tut 09 ~ Classes

Tut 10 ~ The 'New' Keyword

Tut 11 ~ A little on Instance Variables and some more on 'New'

Tut 12 ~ Class Inheritance

Tut 13 ~ More on Class Inheritance

Tut 14 ~ The 'Super' Keyword

Tut 15 ~ Hierachy of Classes and Methods

Tut 16 ~ Aliasing Methods

Tut 17 ~ First Script: Collision Sound

Tut 18 ~ 'If', 'Unless', and the 'Case' keyword

Tut 19 ~ Loops

Tut 20 ~ More Loops and the 'Break' Keyword

Tut 21 ~ Concatenating Strings

Tut 22 ~ Gsub (Replacing Text)

Tut 23 ~ Modules

Tut 24 ~ Module Methods

Tut 25 ~ Some Altenate 'If' Statement Code and .is_a?

Tut 26 ~ Going Through the Workings of the Default Scripts

Tut 27 ~ Ternary Operators

Tut 28 ~ Second Script: Play SE on Balloon Pop-Up

Tut 29 ~ Aliasing Module Methods

Tut 30 ~ Creating Command Window Options

Tut 31 ~ Creating a Window and Drawing Text

Tut 32 ~ Using Script Calls in Events

Tut 33 ~ Creating a Custom Scene

Tut 34 ~ Using Sprites and Textures

Tut 35 ~ attr_reader, attr_writer, attr_accessor and Saving Variables in a Save File

Tut 36 ~ Writing a Basic Word-Wrapper

Tut 37 ~ Finishing the Synopsis Scene

Tut 38 ~ Writing Script Instructions

Tut 39 ~ Accessing Pre-Made/Internal Data

Tut 40 ~ 2D|3D Arrays

Tut 41 ~ Hash

Tut 42 ~ Horizontal Commands, Animated Sprites, Window Entrances

Tut 43 ~ Scrolling Text in a Window

Tut 44 ~ Third Script: Sound Test Scene (Part One)

Tut 45 ~ Third Script: Sound Test Scene (Part Two)

Tut 46 ~ Third Script: Sound Test Scene (Part Three)

Tut 47 ~ Third Script: Sound Test Scene (Part Four)

Tut 48 ~ Third Script: Sound Test Scene (Final)

Tut 49 ~ Structs

Tut 50 ~ Getting Access to the Contents of Noteboxes

Tut 51 ~ Regular Expressions

Tut 52 ~ Getting Multiple Regex Matches

Tut 53 ~ Event Commands and Comment Tags

Tut 54 ~ Creating a Core Script

Tut 55 ~ Fiber.new { explain_me() }

So, I figured this out, with some contextual aid, but for those of you looking to simplify messages, or however this may be useful to you, here's how to store the price of any item in a variable.

Event Command Set Variable

Script

$data_items[00].price

Replace 00 with the item ID (like Potion is ID 1 by default), and when the variable is set, it will be set with the price as defined in the DB (by default a potion's price is 50).

You can also do this with $data_armors and $data_weapons to get the prices of those.

One example of this being useful is in messages.

"A Potion costs \v[1]\G."

This way, if the DB changes, you don't have to alter potentially hundreds of messages to match the DB change.

Yup, that's really all there is to it.

Requirements:

-Node.js

-BrowserSync

-An RPG Maker MV project.

Video version:

Text Version:

Here’s how to start using it:

1. Download Node.js from https://nodejs.org (or from your repository, if you are using a Linux distro). You can use either the LTS or the Current version.

2. After installing, run the node command line, then type “npm install -g browser-sync” (without the quotes. This will take a while.

3. Once installed, switch to the game’s folder in the command line (usually, cd <folder>).

4. Type “browser-sync start --server” (without the quotes). This will set up the server and open the game in the default browser.

If everything went right, you’ll see the “Connected to BrowserSync” badge and the game should work as it should.

If you need the game to refresh the browser every time you edit the game, you’ll need to tell BrowserSync to monitor the files.

To do that, type:

browser-sync start --server --files “<folder>/<file or filetype>”

Examples:

browser-sync start --server --files “data/*.json”

browser-sync start --server --files “*”

After that, just edit the game. The browser will refresh automatically.

Part 2 will come when I figure out the best way to animate the attacks.

So if anyone has any idea how to check if an actor is attacking for the purpose of a conditional branch condition, let me know.

I love the default combat system. Side view is all right, but its been done by 34956875602 different games.

I like the first person aspect. To me it just feels more personal.

Sadly it is a little lacking in the flair department, and so I set out to fix this. 

Keep in mind, what I am about to show you isn't for the faint of heart or those allergic to chocolate.

And it might give you a quick glimpse of how certain events can be used differently and more creatively.

Evented True First person battles.

(Disclaimer, this is not animated. It simply shows hands, and weapons/gauntlets/shields if you set them up.

See opening comments about the system being animated)

(Disclaimer 2, this only checks for the equipment of the first actor, or whoever you set up the common event for)

Step 1.

Creating the Resources

In this evented combat system, we will be using pictures to show the player and weapons instead of sprites.

In this tutorial, they will be referred to as the "Frame" or "Frames".

All frames will go in your "Picture" folder, in the img folder at the root of your Project Folder.

I HIGHLY recommend using gimp to modify/create pictures. I use it for all of my sprite art.

You can find it at http://www.gimp.org/downloads/

All frames must be the native resolution of the game you are creating.

Meaning that if you are using the default resolution, the frames must be 816x624.

I started with a basic empty picture, sized 816x624. Make sure that it is transparent.

If you dont know how to do that, well, google works wonders when learning to use a program like Gimp.

I then cropped and modified some of the SV actors hands to create a kind of Elder scrolls esque view.

For the Spriting illiterate, here is a basic image to use/build off of.

I then modified some of the weapons sprites in the same way.

You may also use/build off of these.

After you have these resources, you are ready for the eventing!

Step 2.

Creating the Event

First and foremost, we will be using a common event at the beginning of each battle to show the equipment.

So name a common event something like FPB or something, idk.

Within that common event, we are going to be using conditional branches to check for equipment at the start of battle.

The first event will be Show Picture. This is located on the second tab under Picture.

The frame we will be using is "Holding.png"

Set that frame to be picture number 3.

The reason this is set first, and not in a condition, is so that even if we dont have a weapon equipped,

it will still show the fists. So barehand fighting is a thing.

From there the flow of adding items is rather simple.

Condtional Branch> Actor> Weapon>the weapon you want to check for

Make sure to leave "create else branch?" unticked.

Then within that conditional branch we set the corresponding weapon frame.

Show Picture> "name of weapon frame you wish to use"

Set that to picture number 1

E.g 

Conditional Branch>Actor 1>Weapon> Longsword

the conditional branch will show up as

*If: Actor 1 has equipped Longsword

     Show Picture : #1, Longsword, Upper Left (0,0), (100%,100%), 255, Normal

The picture number indicates in what order it will be drawn, 1 being the first and lowest frame.

Therefore when we use the "Holding" frame as picture two, and the weapon frame as picture 1,

the holding frame will overlap the weapon giving the appearance of being held.

Do the same for each weapon in your database.

By the time you are finished it should look something like this;

Step 3.

Calling the system for battle

The very last step in this process is to run the common event from the troop tab.

Go to troops, and in the battle event, run the common event we just created.

Set the conditions for Turn number 0 and the span as Battle.

It should look like this

If you don't fell like setting up EVERY troop event I highly recommend Yanfly's

Base Troop Events.

It will allow you to use the first troop's event as a general event that ALL troops use.

You can find it here

http://yanfly.moe/yep/

Step 4.

Prepare for BATTLE!

With any luck I have described this well enough for you to have the event set up perfectly.

Go in to battle young one, and draw thee pixel sword!

(Of course I'm still a noob myself, And this is my very first post so don't ding me to bad XD)

Now I've been playing around with RMVXA a lot lately and while i was randomly making a BS test run of a enemy attack system.

I came to the conclusion that I wanted to actualy try to make a back story. So I ended up making a back story and then I ended up

deciding I wanted to make a game! So I pondered for a while and wanted to add all kinds of crazy features and nick nacks and what not. The only problem is that I know no codeing of any sort at all (You know, with the scripting tab) However I noticed I was decent at comeing up with events on the event editor.

Well I wanted to add a bit of demention to my game and add that little touch I don't think a lot of people have. I wanted to make a day and night transition system. Now at first I was thinking "Holy crap, this is going to be very complicated. There will be thousands of variables, a hundred triggers and pages and pages of scripting!" But fortunatly, through some crafty thinking and my ability to over analize things, my transition system was born. (Also note that, from what I understand, RMVX works just like RMVXA so this can be implemented into that program as well, though I've never tried to do it myself.)

The tutorial comes with full step by step instructions that tell you just about everything you need to know and hopefuly eases the frustration you could of have had if they weren't there. XD If you have any questions, tips, experiences, or comments please post it here or send me a private message. I'll check daily (if not hourly) and hopefully I can reply to you as soon as possible.

After an error with a script, I tried using events to create a transfer between driving a vehicle and an interior. With some help from other members, I was able to create a way to do it.

In-Game Screencaps:

How It Works:

I hope this is helpful to some people! If there's anything anyone needs clarified, please say so here.