Full Games List
Featured Games
New Games
Reviews
Images
Blogs
Game Updates
Images Feedback Summary
Game Design Highlights
Tutorials
Articles
Scripts
Utilities / Plugins
Resources
Engines
Engine Bulletins
What is Makerscore?
Past Events
Achievements
Forums
Post History
Chat
New to RMN?
Full Store List
RMN Music Pack (free)
Add Review
Subscribe
Nominate
Submit Media
RSS
Remap Menu Commands
WolfCoder- 03/01/2011 05:30 PM
- 1615 views
Hey! Now time for a sweet new feature that's already implemented and will be in the next release!
I added a syscall to remap the menu commands. What's this do? Well, take a look at the following picture:
Don't forget E is always the command you want to use and F is what you set to 1 to run it.
Here, A is the menu command to change which can be any of these:
1 - Item 2 - Skill
3 - Equip 4 - Save
5 - Status 6 - Row
7 - Order 8 - ATB
And B is the Common Event ID to map it to. I made Common Event 5 say some message to test this out with.
C is enable/disable. This overrides any previous methods of disabling some menu commands, this lets you enable and disable any of them except for quit. Be sure to put 1 into C or the menu option will get disabled. These are also saved so the next time you load a game, the options will still be disable/enabled.
See how I only set three variables when I test disabling? I had already set E and B doesn't matter if I'm disabling the option anyway.
This is a good way to hijack some commands you'll never use to add a way to manage whatever custom RPG system you made right from the standard menu.
I added a syscall to remap the menu commands. What's this do? Well, take a look at the following picture:
Don't forget E is always the command you want to use and F is what you set to 1 to run it.
Here, A is the menu command to change which can be any of these:
1 - Item 2 - Skill
3 - Equip 4 - Save
5 - Status 6 - Row
7 - Order 8 - ATB
And B is the Common Event ID to map it to. I made Common Event 5 say some message to test this out with.
C is enable/disable. This overrides any previous methods of disabling some menu commands, this lets you enable and disable any of them except for quit. Be sure to put 1 into C or the menu option will get disabled. These are also saved so the next time you load a game, the options will still be disable/enabled.
See how I only set three variables when I test disabling? I had already set E and B doesn't matter if I'm disabling the option anyway.
This is a good way to hijack some commands you'll never use to add a way to manage whatever custom RPG system you made right from the standard menu.
Posts 
Pages:
1
View playlists
CloseI'm confused. So does this mean the first 6 variables will be reserved for remapping the menu commands? Because that's going to fuck with all kinds of things.
This essentially allows players to call custom events via commands in the default menu then? (eg, new skill menus with pictures, etc if we wanted?)
WolfCoder
3554
I'm confused. So does this mean the first 6 variables will be reserved for remapping the menu commands? Because that's going to fuck with all kinds of things.
You have to add the line Year=20XX to the .ini file for it to do this. And even then, you can relocate the registers somewhere else if you want to upgrade projects and use the extra features.
This essentially allows players to call custom events via commands in the default menu then? (eg, new skill menus with pictures, etc if we wanted?)
It's kind of the point, yes. I'm even adding commands that let you draw individual GUI elements directly without using pictures so you can create custom menus for custom systems or whatever. Or the command can do other things, whatever you feel like doing.
Rad. I hope that eventually there will be some kind of gui to all this so you won't have to mess around with flipping all these variables constantly. = D
So then you have plans to rework the editor as well. I hope you will not waste time making one from scratch like easyRPG
WolfCoder
3554
It would have to be from scratch actually, just as this engine is from scratch. The difference is that I'm likely not going to be writing any sort of editor from scratch until the summer. The engine will be in beta form, complete or near complete, on the 20th. I want to deliver on this, and then I will have to shift my focus to two school projects for the rest of this semester.
Pages:
1
