Mod Attempt Results in Complete Shutdown, Please Help.

So I am by no form of measure anything other than a noob, especially when it comes to modding and writing code and suchlike. However I generally have a feel for what stuff says, and I like to try to make programs do weird things, so this brings me to the problem.

 

Elemental will not load for me at all anymore. It opens the title screen and promptly freezes. A quick ctr+alt+del is enough to get out, but the fact remains that I can no longer play Elemental. I'm running version 1.2a I think its called. (As updated as you can get essentially right now)

 

The problem resulted from my attempt to repeat a mod that apparently worked very successfully for others and is outlined in https://forums.elementalgame.com/389679. (Simple mod should be easy to make work, it just allows you to build maps of sizes other than those built in) After copying the final versions of that code into the CoreMaps.xml folder in Elemental/data/English the game began to refuse to start. I adjusted the code a few times for things I thought were weird, never adjusting the built in code. After these failed too, I decided to delete all the lines I'd writen, but even though the code is now back to exactly the way it was before I cannot get Elemental to start.

 

I figure this is a simple fix, with a solution probably buried in one of the files on here, so I won't bother making this thread obnoxiously long by posting the debuging data.

 

Whatever you could do to help would be helpful.

2,121 views 2 replies
Reply #1 Top

First, are you saying the game stalls on the load screen? Keep in mind when you change core files, all the load files need to be re-read and compiled into a data.zip. This can take minutes, even on very modern computers. If this is what you are seeing, you simply need to wait out the load until you get to the main menu.

Second, if nothing else works, you can shift+rightclick elemental in impulse and select verify installation. That will restore all the files to factory format.

Third, reinstall.

Reply #2 Top

Figured it was something simple like that. I kept getting thrown off by Windows claiming that it was "Not Responding", but yes, it appears to have just needed a bit more time. I think I may try putting the code back in and waiting a bit longer to see if it really was just a matter of time.