14-03-2001 04:51									#1
	MM2_TryMilitia variable....error Support Apolyton buy from Amazon

Another idea to the general debugging or suggestions to common errors might be to set up forums which direct people to solutions of common errors or allow specifici problems to be isolated rather than to post all problems with the main Med Mod thread or Diplomod thread.

I've seen this one before in the main Med mod thread by preacherman involving the error message:-

MM2_TryMilitia,variable "MM2_TryMilitia#tmpLoc" and "noname" are of different type

There is no great problem here as it just falls out of the game but I always seem to be able to get back in from the desktop where the game was dumped so it's only a little annoying - this is the third consecutive turn that I've been dumped on the same message

But for all those skilled in debugging I've got about 8 cities now and a small stack of two barbarian archers wandering around looking for trouble. If you want more info I'll save the game as it is and give full details of who's where or what's going on

So where might be look for the cause???

------------------
Theirs is not to reason why, theirs is but to do and die.

	14-03-2001 05:06									#2
	Support Apolyton or Terrorists Win

Just a little more information which might help....

The error message is also trigger at the time I settle my next city so somewhere along the line I suspect one of these variables has got corrupted during the game.

But then, what would I know?

	14-03-2001 10:24									#3
	Support Apolyton, buy Civilization: The Boardgame

I have gotten the errors you mentioned in previous versions of the mod. Wait until we get things settled down, and perhaps they will go away. This slic stuff is really fickle, so don't get down especially if no one else is reporting the error you are having.

	14-03-2001 16:09									#4
	Tired of ads?

You can probably solve this problem by opening the chat window ('-key) and typing /reloadslic. You'll probably have to do this everytime after you loaded a savegame, since loading a savegame causes this problem (at least it did in the past).