top of page

Menu




Inside "Data/Scripts" there is a main menu script file called "Menu.script". It uses its own commands but basically it's a script. Any menu option is hard-coded so all you can do is change its position and add a text.


mcolor 255 255 255 - sets main menu font color as R,G,B.

mbutton "CONTINUE" 50 370 "return" -1 - creates a button. You can't create your ownn button, they're hard coded. The last number is a meu screen this button will be shown at: -1 - any of them, 0 - main screen only, 1 - save, 2 - load, 3 - video, 32 - video 2, 4 - game, 5 - audio, 6 - input, 62 - keyboard.

mtext "SETTINGS" 570 30 5 - the only component you can create. Just shows a text.

As of Alpha 49 you can now add custom keybinds, based on script inputs, to the input screen.


minput [posX] [posY] [scriptName.script] [pageNumber]

mrange [posX] [posY] [db.varName] [min] [max] [step] [defaultValue] [pageNumber] - 'step' is how much to subtract/add when clicking left/right.

mcheckbox [posX] [posY] [db.varName] [defaultValue (0/1)] [pageNumber]

For added presentation, menu sounds can be added in the system resources screen in the editor. - System resources importer allows unique sounds for hover, click, and when you hit the upper/lower limit of a range.


Menu checkbox text can be changed with mcheckboxstyle command in menu.script files.

mcheckboxstyle "Off" "Hover Off" "Hover On" "On" - eg; mcheckboxstyle No -No- -Yes- Yes

Added three new menu options for modifying db.variables ('db' values are saved to the Saves/db.txt file, offering a form of persistent storage that isn't tied to a save file.)

bottom of page