This is an improvement on the usual cheat code event. How? 1. it's bigger 2.it uses text input
It's pretty much an expansion on the stuff in the Tester's Tool kit. How the event is triggered (switch, touch etc) is up to you.
This one is long. It changes party gold, items, levels...everything. Hence the couple hundred choice boxes and redundant variable use. First, create a new actor (you read that right) Leave it blank; don't fill anything in, especially the name. This'll make sense soon enough. If you don't like your blank actor, you can make a face graphic that says "Enter Cheat Code" and call it "Cheat"
Go to your event and put in: actor name input processing condition branch-if actor (cheat)'s name is (whatever you want the code to be): ->Show choices: gold, party, items, other when gold-enter input # for variable GOLD- increase gold by variable GOLD when party ->show choices-Level, armor, weapons,other when level ->show choices (list of party members. 4 boxes, 4 party members. Convenient, eh? ) (select a party member) input # for variable-LEVEL change level of party member to variable LEVEL when items- (same deal. if the variable is this, give that item) -show choice box (weapons, armor, scrolls etc) when armor (same as items) when weapons (same as items, armor...etc) when other show choices: chapter select, graphics, speed (you can use this to change stuff like graphics and walking speed/options via the Move Route command) when chapter input number for variable-LEVEL condition branch -when variable level ==1 transfer player to (wherever you want in chapter 1) (make a condition branch for each chapter, with the number entered corresponding to the chapter you want)
This is obviously shorter than it's likely to be. You can just use some Call common event stuff so that you don't have a list box as long as your arm. It'll effectively call up, through a series of choice boxes, everything you could possibly need to change anything about your party. I'm pretty sure I got everything. You can get the gist of how it works pretty easily, so it's easy to see where there might be a problem. And no, I can't make it shorter. It covers everything I could think of that you might want to chage.