JSGME Is Case-Sensitive!

DrBeast · 12-11-07, 06:51 AM

This little detail may sometimes slip our mind, be it modders who are making their mods JSGME-ready, or users that install those mods. What does this mean? I'll elaborate with an example:

Let's say we have mod A, which is structured as thus: data\Library\AI_Sensors.dat. What does it do? It replaces the AI_Sensors.dat file, found in the game's Data\Library directory. We install this mod, JSGME keeps a back-up of the original (core game) file.
Now, we install another mod that changes the AI_Sensors.dat, mod B, which has this file structure: Data\Library\AI_Sensors.dat (notice the capital D in Data). What should happen? JSGME should issue a warning that mod B contains a file that exists in mod A, correct? Well, this won't happen! Instead, it'll quietly overwrite the file from mod A, and keep a backup of mod A's file. "Nothing to worry about, we just don't get a warning", you might say. Correct, but what happens if we disable mod A? Normally, JSGME would tell us that we'll have to disable mod B first, as it has altered the same file. It won't do that! Instead, it'll remove the AI_Sensors.dat of mod B and revert to the game's original file, essentially disabling both mod A and B. But, if you then proceed to disable mod B, it will revert to the file from mod A! You can see how this can mess up your original data, yes?
However, if you take the correct route and disable mod B before mod A, you're trouble-free. JSGME will revert to the correct backups all the time.

What needs to be done?
Well, modders should check and be sure that the file structure they're following is an exact copy of the core game's file structure, down to the letter. Mod users should check to see if the file structure is indeed correct. This might save you from needless reinstalls and frustration. Also, when you're disabling mods, make sure to disable them from the bottom up, to avoid any foul-ups of your core game's files.

Hope this helps, happy hunting!

Edit: Guys...disregard all this and go grab the newest version of JSGME (2.0.1). It solves this problem. I thought 2.0.0, which I had installed, was the latest version, but I guess I had a brain-fart and forgot there was a newer version released a few days after I got that one. My apologies for spreading false information.

Fincuan · 12-11-07, 06:56 AM

Good find

Thanks for bringing this up

DrBeast · 12-11-07, 07:17 AM

Oh...damn. Damn and crap! I was just looking over the JSGME thread, and I noticed there's a 2.0.1 version out in late October. I then looked in my Downloads stash, and I found an installer of a similar date. But frankly, I didn't remember that update at all, and it deals with case-sensitivity. So there'a small chance that I haven't installed 2.0.1. I'll have to check as soon as I get home and report back tomorrow (sucks not having internet at home, dammit!). I sincerely hope I didn't do a huge blunder here!

Digital_Trucker · 12-11-07, 02:49 PM

Well, at the very least, you reminded us to make sure we have the latest version

Ducimus · 12-11-07, 04:45 PM

And here i just assumed everyone would have noticed this. *shrug* Think of JSGME as being unix like in its syntax.

ls -al /usr/local/Mod/somefile.upc

is not the same as

ls -al /usr/local/mod/SomeFile.upc

They are infact, totally different.

tater · 12-11-07, 04:50 PM

Yeah, being a unix guy I always use the proper capitalizations. I bet this explains some of my SH4 corruption. I reinstalled from scratch for 1.4, I had a total mix of stock vs modded files in 1.3 after a while.

DrBeast · 12-12-07, 07:15 AM

Ok guys, I screwed up big time. It turns out I didn't have the latest JSGME (2.0.1) installed. That version is not case-sensitive. My apologies to JScones for jumping to conclusions. Now, where's that big hole in the ground I spotted? I think I'll go into hiding for a while

JScones · 12-13-07, 04:26 AM

Yes, the case sensitivity issue was corrected in v2.0.1.

It's a good idea to get into the habit of pressing the "Updates" link in JSGME every once in a while.

DrBeast · 12-13-07, 07:38 AM

Yes, the Update link is very useful, provided one has an internet connection at home. Unfortunately, my only access to the internet is from the Uni where I'm doing my PhD, which means lots of back and forth file transfers from work computer to home with my trusted USB memory stick

12-11-07, 06:51 AM	#1
DrBeast The Old Man Join Date: Oct 2007 Location: Somewhere Out In Space Posts: 1,408 Downloads: 36 Uploads: 0	JSGME Is Case-Sensitive! This little detail may sometimes slip our mind, be it modders who are making their mods JSGME-ready, or users that install those mods. What does this mean? I'll elaborate with an example: Let's say we have mod A, which is structured as thus: data\Library\AI_Sensors.dat. What does it do? It replaces the AI_Sensors.dat file, found in the game's Data\Library directory. We install this mod, JSGME keeps a back-up of the original (core game) file. Now, we install another mod that changes the AI_Sensors.dat, mod B, which has this file structure: Data\Library\AI_Sensors.dat (notice the capital D in Data). What should happen? JSGME should issue a warning that mod B contains a file that exists in mod A, correct? Well, this won't happen! Instead, it'll quietly overwrite the file from mod A, and keep a backup of mod A's file. "Nothing to worry about, we just don't get a warning", you might say. Correct, but what happens if we disable mod A? Normally, JSGME would tell us that we'll have to disable mod B first, as it has altered the same file. It won't do that! Instead, it'll remove the AI_Sensors.dat of mod B and revert to the game's original file, essentially disabling both mod A and B. But, if you then proceed to disable mod B, it will revert to the file from mod A! You can see how this can mess up your original data, yes? However, if you take the correct route and disable mod B before mod A, you're trouble-free. JSGME will revert to the correct backups all the time. What needs to be done? Well, modders should check and be sure that the file structure they're following is an exact copy of the core game's file structure, down to the letter. Mod users should check to see if the file structure is indeed correct. This might save you from needless reinstalls and frustration. Also, when you're disabling mods, make sure to disable them from the bottom up, to avoid any foul-ups of your core game's files. Hope this helps, happy hunting! Edit: Guys...disregard all this and go grab the newest version of JSGME (2.0.1). It solves this problem. I thought 2.0.0, which I had installed, was the latest version, but I guess I had a brain-fart and forgot there was a newer version released a few days after I got that one. My apologies for spreading false information. __________________ Let the Beast inside you free! Last edited by DrBeast; 12-12-07 at 07:20 AM.

12-11-07, 07:17 AM	#3
DrBeast The Old Man Join Date: Oct 2007 Location: Somewhere Out In Space Posts: 1,408 Downloads: 36 Uploads: 0	Oh...damn. Damn and crap! I was just looking over the JSGME thread, and I noticed there's a 2.0.1 version out in late October. I then looked in my Downloads stash, and I found an installer of a similar date. But frankly, I didn't remember that update at all, and it deals with case-sensitivity. So there'a small chance that I haven't installed 2.0.1. I'll have to check as soon as I get home and report back tomorrow (sucks not having internet at home, dammit!). I sincerely hope I didn't do a huge blunder here! __________________ Let the Beast inside you free!

12-11-07, 02:49 PM	#4
Digital_Trucker Silent Hunter Join Date: Jul 2007 Location: The Peach State Posts: 4,171 Downloads: 141 Uploads: 10	Well, at the very least, you reminded us to make sure we have the latest version __________________ RSM-GIEP-Killflags-LV Tribute-Playable Elco __Peace be with you, Dave.

12-12-07, 07:15 AM	#7
DrBeast The Old Man Join Date: Oct 2007 Location: Somewhere Out In Space Posts: 1,408 Downloads: 36 Uploads: 0	Ok guys, I screwed up big time. It turns out I didn't have the latest JSGME (2.0.1) installed. That version is not case-sensitive. My apologies to JScones for jumping to conclusions. Now, where's that big hole in the ground I spotted? I think I'll go into hiding for a while __________________ Let the Beast inside you free!

12-13-07, 07:38 AM	#9
DrBeast The Old Man Join Date: Oct 2007 Location: Somewhere Out In Space Posts: 1,408 Downloads: 36 Uploads: 0	Yes, the Update link is very useful, provided one has an internet connection at home. Unfortunately, my only access to the internet is from the Uni where I'm doing my PhD, which means lots of back and forth file transfers from work computer to home with my trusted USB memory stick __________________ Let the Beast inside you free!

12-11-07, 06:56 AM	#2
Fincuan Admiral Join Date: Aug 2007 Location: Suomi, sauna, puukko, perkele Posts: 2,346 Downloads: 39 Uploads: 0	Good find Thanks for bringing this up

12-11-07, 04:45 PM	#5
Ducimus Rear Admiral Join Date: May 2005 Posts: 12,987 Downloads: 67 Uploads: 2	And here i just assumed everyone would have noticed this. shrug Think of JSGME as being unix like in its syntax. ls -al /usr/local/Mod/somefile.upc is not the same as ls -al /usr/local/mod/SomeFile.upc They are infact, totally different.

12-11-07, 04:50 PM	#6
tater Navy Seal Join Date: Mar 2007 Location: New Mexico, USA Posts: 9,023 Downloads: 8 Uploads: 2	Yeah, being a unix guy I always use the proper capitalizations. I bet this explains some of my SH4 corruption. I reinstalled from scratch for 1.4, I had a total mix of stock vs modded files in 1.3 after a while.

12-13-07, 04:26 AM	#8
JScones Navy Seal Join Date: Apr 2005 Posts: 5,501 Downloads: 19 Uploads: 0	Yes, the case sensitivity issue was corrected in v2.0.1. It's a good idea to get into the habit of pressing the "Updates" link in JSGME every once in a while.