29-05-2002 12:25									#1
	SLIC Error on saved games Support Apolyton

I keep getting a SLIC error message whenever I load a saved game (unless it's very early in the game). The error message is "In object CheckForUnit, function_GetUnitFromArmy: value out of bounds". This appears to occur on the first unit move after loading and all subsequent moves (mine and the AI) for the duration of the first turn after loading. After the first turn the game seems to operate normally. I'm running the CTPII patch 1.11 and the Apolyton mod pack. I hope that someone here can help me out.

	29-05-2002 17:15									#2
	Support Apolyton or Terrorists Win

Im not sure of the exact reference to the SLIC message, but was the save game from the unmodded game? You cant play a saved game from the original game with the apolyton pack, or most of the other mods, if any.

	29-05-2002 19:35									#3
	Put an end to popups!

Have you got DebugSlic to '=Yes' or '=No' ? It should be '=No' for running any mods.

(In case you haven't the foggiest what I'm talking about, open ctp2_program/ctp2/userprofile.txt and search for DebugSlic)

	29-05-2002 22:18									#4
	Support Apolyton, buy Civilization: The Boardgame

Thanks Immortal Wombat, that seems to have been the problem. I thought I had already changed that but I must have exited the text editor without saving. Again, thanks a lot.

	29-05-2002 22:47									#5
	Support Apolyton, buy Galactic Civilizations: Deluxe Edition

Wombat- Maybe you can explain a few things about slic for me. What exactly do you do when you "reload the slic" and why does it matter if the debug equals yes or no? I'm just kind of curious what exactly these changes do to the program. Thanks in advance.

	30-05-2002 04:09									#6
	Support Apolyton, buy Galactic Civilizations: Deluxe Edition

debugslic is a flag that toggles how well the game finds errors in the code. I'm sure Peter could explain this better, but bascally, if its set to Yes, it finds every single source of error, and tells you. For some reason, there are some 'bugs' that the debug finds that do not affect the operation of the code, and indeed seem to be neccessary to the function of the code.
To stop the messages from flagging up these non-bugs, set debugslic to no, and it will glide over errors that are not detrimental to the operation of the code. But will still tell you about syntax errors, and incorrectly written code.

To "reload the slic", you can either reload the game, or open the chat window (') and type "/reloadslic" This flushes out all the pre-running SLIC (including message logs, global variables etc.) and replaces it with the SLIC that is being loaded from script.slc and its subsidiary files. This is useful while editing SLIC with the game open, because you can write some code, load it in, see what errors it gives you, change them, reload etc. Or if it gives you no errors, you can see exactly what the code does, and whether its working as it should.

	30-05-2002 21:51									#7
	Remove this text

Ok, I think I understand things a little better now. Thanks.

	31-05-2002 04:26									#8
	Support Apolyton, buy GURPS/ Alpha Centauri

Amazing, just amazing. They anticipate your problem and post the answer just before you get there.

I came here tonight to search for an answer for the exact same problem, but Wombat had already posted the answer. And yes, my debugslic entry was set to "yes" also.

Thanks

Bob Mercer

	01-06-2002 03:32									#9
	Lose 30 kilos (of popups)

We at Apolyton take pride in our community.