LOCKEZ'S PROFILE

As best I can tell, here's how agility seemed to work based on my testing:

- If character A has twice as much agility as character B, character A will get turns twice as often.
- The overall battle speed will either slow down or speed up based on the total number of party members + enemies. If there are more battlers, then the overall battle speed will be slower. This doesn't actually affect combat balance at all, it just speeds everything up evenly. (This rule is actually just a side-effect of the next rule...)
- Similarly, the overall battle speed will either slow down or speed up based on the total combined agility of all party members + allies. If the total combined agility is higher, then the overall battle speed will be slower. Similar to above, this doesn't actually affect combat balance at all, it just speeds everything up evenly.
- The end result of the above rules is that there will always be approximately the same total number of turns per minute.
- I did not test for an effective cap of 256, but it's certainly possible. If this cap exists, it is a cap per character, not a cap on the total combined agility.

These sorts of custom menus have to be done with events, due to RM2K3's lack of scripts. Amazingly, we don't seem to have any sort of custom menu system tutorial here in our tutorials section. Which sucks because it's pretty complicated. But here are the basics:

- Make an auto-start event. If your menu is on its own map (which is easier) then this should be a map event, and opening the menu should send the player to this map. Otherwise, it will need to be a common event, with a switch as a precondition, and opening the menu will be done by turning on this switch.
- Make a variable, "cursor location". If your menu is two-dimensional instead of just a single list, you'll need two variables, "cursor x-coordinate" and "cursor y-coordinate". The autostart event will need a conditional branch for every possible location the cursor can be. Within each of those conditions, if the condition is true, move the cursor picture (or event) to the specified location.
- Below that, in the same event, add a key input processing command, that accepts all the keys your game uses. The key the player presses will be stored into a variable, "player input".
- Then have some conditional branches, which will fork based on this "player input" variable. If the player pressed down, increase the cursor variable by 1. If the player pressed up, decrease the cursor variable by 1. In a 2-dimensional menu, you also need to check for left and right. If they pressed cancel, close the menu. If they pressed enter...
- If they pressed enter, then you need to detect their cursor coordinates, and do whatever you want that command on the menu to do. If your menu is a team-changing menu, then it would add or remove whichever team member the cursor is currently on. If your menu is a main menu, and the cursor is over the "Equip" command, then you get to send them to a second custom menu, where they choose equipment. Etc.


This is easier for simpler menus, like a team-changing menu. It's much harder for a real main menu, since the things the player can do are much more complicated, and it's not always easy to do what you want with just events.

With any luck, you can figure out where to go from here, or maybe find a tutorial on another site that explains the finer technical details.

On normal mode, the difficulty is pretty reasonable. If you play on Really Freaking Hard mode, and then decide to complain that the game is really freaking hard, I have no sympathy.

He didn't stop because of the difficulty though, he stopped because he didn't like the game. Oh well. Like a previous poster said, although the game is "Completed" I am still capable of making updates to it, and I plan to do so. Some of the issues mentioned were just problems with RPG Maker, but others are things I can address in updates.

The problems you mentioned are all duly noted and I will most likely attempt to address some or all of them with an update in the near future. In particular, I know that I really should rewrite the opening somehow to have the tutorial fight first.

Technical note, though: You cannot count. The battles in Opening Credits Forest occur every 20-32 steps. Yes, I actually created a custom random battle system which has a minimum number of steps. And that minimum number is four times what you claimed the average number is.

My main disagreement with the reviewer here is actually just that I don't really approve of a review that only covers the first 10% to 15% of a game. However, I suppose many of the points he made are still fair.

Makerscore isn't a rating of your game, nor is it even linked to your game - it's linked to you. It's a (bad) indication of how much you as a person have contributed to the community. Note that the same number appears next to every forum post you make.