Log in

View Full Version : En_menu.txt question


Steppenwolf
01-22-07, 04:01 PM
Does anyone know if SH3 cares if the keys in this file are in numerical order?

i.e. If these key entries were in the following order:
591=Men Down on deck
607=Destroyer on Attack Run
596=We've been spotted

Would it object to key 596 being after 607, or does it just go by the key's name (596=) and the order is irrelevant?

The reason I ask is that I am trying to put all of the little one or two line file tweaks that I do manually, into SH3 Commander's "static settings" file, so I can apply/unapply them all easily. GWX has the "596=We've been spotted" message commented out. So, if I try and change it with SH3 Commander, Sh3 Commander doesn't think that key exists and instead of changing that key, it writes the new "596=We've been spotted" message to the END of the section. So the "596=We've been spotted" line LOOKS fine, but is out of numerical sequence.

I can, of course just change it manually, but it's those manual changes I'm trying to get away from and get more orgainzed by using Commander to do them. I can, of course, also just make the change, start a patrol, try to find a ship and see if the game explodes. But thought I would ask here first, if anyone has run into something like this in this file (or some other SH3 file) before potentially crashing the system. Thanks.

Samwolf
01-22-07, 04:05 PM
As far as I know, order does not make a difference, I have some of the upgrade text out of numerical order and SH3 seems to work fine.

Steppenwolf
01-22-07, 04:39 PM
Thanks a lot Samwolf, that's what I wanted to know.

JScones
01-23-07, 02:20 AM
Correct. Order is indeed irrelevant.

Where an entry does not exist in the destination SH3 file, SH3Cmdr will write it to the end of the associated section "block".

This is fine. SH3 will not get upset. Indeed, writing to the end of the block allows for easier identification of (user) typos in the entries that are added to Static settings.cfg (or other SH3Cmdr files), as indeed you noticed. ;)

Perhaps more fundamentally though, SH3Cmdr wouldn't allow this to happen if it upset SH3. ;)