Tips and Tricks Tutorial Ver.

[Archeia]

This topic is to teach people some nifty Tips and Tricks that helps speed up development in a Quality of Life kind of way. You can add your own as well. I'll start with a few examples. All discussions go here.

Saving Memory A

Spoiler

Do you have too many facesets and preloading too much into memory and sometimes they still get delayed? You can stack them like this and still be usable in the editor. Just try to keep it under the height of 1024 to avoid loading issues:

Saving Memory B

Spoiler

If you have a lot of animations, I recommend using this. It will save you a lot of space. Or use @KanaX 's Spriter Plugin.

How to Setup Teleport/Transfer Locations with just One Event

Spoiler

Normally, you copy and paste numerous events that teleport to different locations or use a parallel process to check regions to know when and where to teleport/transfer your player. Here's a more effective way to do it:

- Use a Plugin that can modify Event Hitboxes. Event Hitbox Resize by @Yanfly, Big Events by @Shaz or Orange Event Hitboxes by @Hudell will do the trick.

- Create a single event and give it the event notetag property based on which Plugin you are using. If you have a map with 5 tiles long to teleport to another location, then give your event either:

Shaz's Plugin:

<bigEvent: 5x1>

Hudell's Plugin:

<hitboxWidth:5>

- Grab the x,y based of the tiles you are interested in.


- Add a conditional branch inside that event using the Script Function. We'll be using the following Script Call:

($gamePlayer.pos(x, y))

It should end up looking like this:


This tutorial doesn't just apply to Teleport/Transfer. It has multiple uses depending on your needs!

My game runs at 120FPS! (Works only in RMMV 1.6.1)

Spoiler

Go and open your project folder/package.json
Make it look like this:

{
    "name": "",
    "main": "index.html",
    "js-flags": "--expose-gc ",
    "window": {
        "title": "",
        "toolbar": false,
        "width": 816,
        "height": 624,
        "icon": "icon/icon.png"
    },
    "chromium-args": "--limit-fps=60"
}

Disable Window Resizing
Add the propery resizable in package.json.

{
    "name": "",
    "main": "index.html",
    "js-flags": "--expose-gc ",
    "window": {
        "title": "",
        "toolbar": false,
        "width": 816,
        "height": 624,
        "icon": "icon/icon.png",
        "resizable": false
    }
}

 

[ozubon]

How to use strings as variables

Spoiler: Spoiler

There are times you want to store data other than numbers into variables. The string can be any text you want. In this example, I'll store an ingredient for a soup and then check if it's added through a conditional branch.

It's very simple: In control variables, I set a variable to the operand Script and then type the name inside quotation marks.

Now variable 11 is set to Onion instead of a number.

And now let's make something happen if it is!
I make a conditional branch and go to page 4 and in the script option I type $gameVariables.value(11) == "Onion"

This script checks if variable 11 is Onion.

So to sum it up:
1. Set a variable with Script to "your text here"
2. In conditional branch you can check with Script $gameVariables.value(ID) == "your text here"

 

[Archeia]

Spend less time searching for events tip
So, this is just a simple QoL I did for myself while game devving. Sometimes, just putting all your initialize code on the top left isn't enough. Maybe you have to use an empty map for reasons unknown and have 0 visual cues on what's going on. Or even when you do, you have a lot of events that you transform via code or whatsoever with no pictures on them strewn across the map and you don't remember what they're for. There can be a lot of reasons!

Here's a template of what I do to workaround this and how they will appear in editor.

Spoiler

There's two ways you can hide the event markers. Either you make the first page empty and put the 2nd page as the start of your content, events put the latter pages as priority if they don't have conditions, like this:

Spoiler

Alternatively, create a new JS file. In my case I called it SpaghettiCode.js and then add the following snippet. Replace DEV_TEST with the filename of your event marker image. Make sure to activate it in your plugin manager!

//=============================================================================
// * Hide Event Markers
//=============================================================================
var Archeia = Archeia || {};
Archeia.Game_CharacterBase_isTransparent = Game_CharacterBase.prototype.isTransparent;
Game_CharacterBase.prototype.isTransparent = function() {
    if (this.characterName() === 'DEV_TEST') return true;
    return Archeia.Game_CharacterBase_isTransparent.call(this);;
};

 

[Burgerland]

How to measure time in frames

Spoiler

Since 60 frames = 1 second, you can use frames to count seconds. Create a new Event, go to second page of Event Commands, under Timing on the right hand side of the page is the command Wait. Depending on the duration you want, here's how to convert frames into units of time measurement. It's multiples of 60.

1 second = 60 frames
5 seconds = 300 frames
10 seconds = 600 frames
30 seconds = 1800 frames
1 minute (60 seconds) = 3600 frames
5 minutes = 18000 frames
10 minutes = 36000 frames
30 minutes = 108000 frames
1 hour (60 minutes) = 216000 frames
5 hours = 1080000 frames
10 hours = 2160000 frames
1 day (24 hours) = 5184000 frames
1 week (7 days) = 36288000 frames
1 month (4 weeks) = 145152000 frames
6 months = 870912000 frames
1 year (12 months) = 1741824000 frames

Since the maximum frames for Wait is 999, I recommend using 900 frames per Wait for any time over 10 seconds after dividing the duration you want by 900 to see how many Wait Commands you need. Below is the selfsame list with the number of Wait Commands for each duration when you divide the desired Wait frames by 900.

60 - 600 frames (1 second - 10 seconds) = 1 Wait Command
1800 frames (30 seconds) = 2 Wait Commands
3600 frames (1 minute) = 3 Wait Commands
18000 frames (5 minutes) = 20 Wait Commands
36000 frames (10 minutes) = 40 Wait Commands
108000 frames (30 minutes) = 120 Wait Commands
216000 frames (1 hour) = 240 Wait Commands
1080000 frames (5 hours) = 1200 Wait Commands
2160000 frames (10 hours) = 2400 Wait Commands
5184000 frames (1 day) = 5760 Wait Commands
36288000 frames (1 week) = 40320 Wait Commands
145152000 frames (1 month) = 161280 Wait Commands
870912000 frames (6 months) = 967680 Wait Commands
1741824000 frames (1 year) = 1935360 Wait Commands