It all started back when RPG Maker VX was released. My friends and I would always lament how it’s impossible to just drag pictures and make our mockups work like magic. No need for script hunting or bug programmers to do every miniscule edit to our projects because we couldn’t do it. With RPG Maker VX Ace and a small conversation in a private chatroom, we finally started work on it.
The Luna Engine is a project by Archeia_Nessiah and Yami, with the amazing help of NeonBlack and Rhyme. It is to create a series of scripts that will allow people to modify the GUIs present inside the game, whilst being easy to use and compatible with the majority of scripts. The Luna Engine took us a little more than a year (June 15 2013~July 2014) to develop, put through beta, make sample graphics for and write the manual. While it was a long journey, it was definitely worth it.
Due to its nature as a GUI script, it might conflict heavily with scripts that do numerous visual modifications. The Luna Engine works best for vanilla battle systems such as the Default Battle System or Yanfly’s Battle Engine due to its popularity, added features and user friendliness. Because of Neonblack’s involvement with this development, it should work with his CP Battle System. This should work with Sideview Graphical Enhancement Scripts like Battle Engine Symphony and Kread’s Animated Battlers.
We do not have plans at the moment to make it compatible with any other scripts aside from Yanfly, Yami, Neonblack and Kread’s scripts. Please don’t ask us for compatibility patches for any other systems because we won’t be able to provide them. We might attempt to add more compatibilities in the future, but for now, it is not possible.
If you would like to report bugs, please remember the following things before reporting:
- You are required to at least be familiar with RPG Maker’s default function. An example scenario would be, if your test character’s skills aren’t displaying, then check their levels, etc. We had instances where people thought it was Luna Engine’s fault.
- Make sure to test the scripts without other scripts to be sure it’s the Luna Engine’s fault.
- Make sure to read this manual and/or reference it. Use CTRL+F or Find for any questions or about features you’re uncertain of.
- You can ask for tech support at email@example.com if this manual doesn’t answer your questions or if you found a bug.
- For further updates in regards to the Luna Engine, you can check our Github or check the Luna Engine tag in Division Heaven.
- Open the Script Editor (F11). Remember that CTRL+F only searches for items inside the present script. CTRL+SHIFT+F means it will search all scripts.
- I recommend using Notepad++ (Free even plugins) or Sublime Text (Shareware) when editing scripts. They have flexible features and it could help you fix anything wrong with your configuration while checking for other errors during testing.
- If you want to compare configurations with the demo scripts, Notepad++ has a plugin for it. Sublime Text has Sublimerge but costs $20. DiffNow is a personal favorite.
The list below just refers to the general options of the configuration script. It doesn’t cover everything and serves as a refresher or a short course of the options. Most, if not all, options found in the script are commented, so there should be no problems figuring out what they can do in case the manual doesn’t cover it.
- :width – the width of the window or item.
- :height – the height of the window or item.
- :max_width and :max_height – these help the system find a value to center the contents shown in the screen.
- :x – this refers to the X coordinate of the screen. This refers to the horizontal (left and right) axis. Negative (e.g. -1) values mean they would move to the left, while Positive values mean they would move to the right.
- :y – this refers to the Y coordinate of the screen. This refers to the vertical (up and down) axis. Negative (e.g. -1) values mean they would move to the up, while Positive values mean they would move to the down.
- :offset_x and :offset_y – these refer to how much you want to nudge the window display without affecting its base x and y. Useful for items such as GUI borders.
- :z – this refers to the item’s display priority. Think of it as layers when you use an image program or when mapping in RPG Maker. The higher the value, the higher it will be drawn above other items.
- :offset_z – this makes the item adjust itself by a specific value just in case you have drawn other items and want an item to remain on top.
- :padding – this refers to the spacing between the window border and the window contents. The default value is 12.
- :vertical – this helps the system determine if the cursor and contents should be displayed vertically if true, or horizontally if set to false.
- :cursor – this is to enable or disable the default cursor.
- :lunatic – when set to true, it will check the Lunatic configuration the user has set for that specific scene.
- :background_variable – this option allows you to have multiple skins for your GUI. Remember that it reads it as a string (e.g. $game_variables = “Menu_Green”) and set a different variable for each menu.
- Another important thing to remember is that enemies and actors are referred to as Battlers in RPG Maker. So if you want to change anything related to the actor itself, it’s most likely in Battler_Status section of Luna’s Configuration Script.
- If you want to use Yami’s Battle Engine Symphony or Kread’s Animated Battlers, you should set animation_on_hud configuration to false.
- When using Yanfly’s Free Turn Battle (FTB) set :arrow_battler in YEA Compatibility to true and if use spin command, :all_dir to false.
- If you want to use the horizontal actor command, set :arrow_battler in YEA Compatibility to false.
- If you want to change the battler options and it doesn’t work, try setting lunatic to false. If you are using lunatic, read the comments as you have to draw the names manually.
- If you want to have more than four party members, go to Adjust Party Size by Archeia.
This is a sample version of what Luna Engine can do. It is highly limited but should give you a good idea on how it works. This is for Non-Commercial Use only.
If you want the Commercial Version, please get the Store Product!