MGE Peculiarities

[Peregrine]

but then, I'm one of a minority of scenario designers who do NOT use that method. I always save as scenario if I'm making changes using the cheat menu and never bother with saving as a saved game. Also, and I'll point this out for other scenario-designers, if you make any changes using the editors menu, you do not have to "save" in any way. You can make your changes using that menu, exit the game, then load it right back up and the changes you made are still there. No muss, no fuss.

If you use the Cheat menu, you do have to reset the time increments, as well as a few other details whenever you save as scenario, but if you do so having selected the first or "white"-colored player, making those changes is not that much of a problem; only the durational effects that have to do with the first player accumulate and those are easy to reset. It's really only the tech beaker accumulation for that player that must be reset.

 

[Henrik]

Originally posted by kobayashi

However, there are cases where it will be difficult to edit the events file manually. - like when you want to give a tech and you don't know the corresponding number. In those cases, you can load up the xxx.scn and use the event s editor but don't save.

Either that or just do it in the save and run delevent on it like I do

 

[CivPartisan]

I've thought about writing a manual giving all the specifics for tech numbers, unit positions, corresponding sounds, maprect terrain numbers, and so forth...

I hadn't really thought about it lately, but after reading here...it might be useful...

John

 

[Andrew Livings]

I've thought about writing a manual giving all the specifics for tech numbers, unit positions, corresponding sounds, maprect terrain numbers, and so forth...

I've made comments in my "normal" rules.txt with extra info like this, which comes in very handy as I use that as a template for new projects. Remember, any text after a semi-colon is disregarded, so you can add comments wherever you like (just don't add new lines between an "@" line and the end of a section.

Here's another tip for saving games. You can load .scn files as a saved game rather than through begin new scenario. Simply backspace over *.scn and type in "*.scn", then load the file you want. You don't advance any and the events block is reset.

 

[kobayashi]

Originally posted by Henrik


Either that or just do it in the save and run delevent on it like I do

Originally posted by Andrew Livings


Here's another tip for saving games. You can load .scn files as a saved game rather than through begin new scenario. Simply backspace over *.scn and type in "*.scn", then load the file you want. You don't advance any and the events block is reset.

and to think I've just been using the save file the plain way all these years.

 

[kobayashi]

Another stupid thing about MGE is the 'set human player to none' has got a screwed up screen redraw routine so multiple images of the same unit appear everywhere. You can't see what is going on like in FW.

Being the barbarian is not much better either - its the same speed as having the entire screen revealed as the units are actually moving under the fog o war.

 

[Morten Blaabjerg]

Agreed. thats one of the things I truly miss from the classic version. It was very useful for playtesting.

 

[DarthVeda]

I really hate how MGE doesn't have a @DEBUG ability for the events.txt.... makes life really hard on we typo-happy scenario creators.

 

[Marko]

Don't be so hard on MGE, guys. It has many fine points over FW too. One example is MOVEUNIT command in events. It was really buggy in FW but has been fixed in MGE.