Bug? getmaxhp: bad unr

[Norfleet]

I get the following error:

Nagot gick fel
unit -1
getmaxhp: bad unr

What does this mean, and how do fix this? Does this mean anything important, or is it just something I have to rip out with a hex editor to make the game continue?

[Johan K]

Try patching Dominions to Version 2.06. If the problem still remains send your game files to [email protected]

[Norfleet]

I applied the patch, but the existing game remains corrupted. I'll see if it happens again next time. What's the error message mean? Is it some kind of memory corruption?

[Kristoffer O]

Originally posted by Norfleet:
I applied the patch, but the existing game remains corrupted. I'll see if it happens again next time. What's the error message mean? Is it some kind of memory corruption?

Nagot gick fel = something went wrong
unit -1 = unit number -1 (wich shouldn't exist)
getmaxhp: bad unr = calculate max hitpoints: the unit does not exist

To sum up: an nonexistent unit is bugging your game

[Norfleet]

Ah. I thought it might be something like that. Does this tend to mean that the data structure that holds units is smashed? I noticed that my normally high unit production curve had flatlined several turns earlier in that game: Is this a sign that units are being written into garbage-land, or is this a normal behavior for Ashen Empire, and there's a unit cap in place to keep the exponential growth curve under control, and this is thus more or less unrelated?

[Johan K]

The game has a limit of about 32000 units. Ashen Empire is able to reach that limit if you play a long time.

[AndonSage]

After getting this error, I did a search and found this thread. My version of Dom2 is 2.16. Is there still a limit of 32k units in the game? I'm playing on the large Faerun map (400+ provinces) with 17 dominions. Ermor has more units than everyone else added together, but has been flat (on the graph) for a few turns. I'm not worried about his armies, as they are mostly cheap undead, and I'm playing Jotenheim, so I have giants, and I have winter wolves and wights to take out his ethereal units. Anyway, was this error supposed to be fixed? Or will I have to restart, and leave Ermor out of the game next time?

[EonDarkStar]

I've also been getting this error, I've been trying to find out what it was I needed to deal with to get around it, unlike many others I like to play long term, to find a balance where I can keep the game running so that I can continue to enjoy what was already developed. So far in this time around I am over 2,800 turns and I would prefer not having to start over and potentially having to face this again, I've tried drowning troops that seemed to be connected, I am playing Caelum and my enemy is Pangea and it seems that the problem was at one point sourced to Pangea, I tried finding a way to deal with it, I struck the city with many spells designed to damage troops without actually engaging them in combat as that caused the error. But now it is apparently present or always moves to a city under siege with no defense left, I can't move all of my troops out to avoid combat to try to work around it. While there are many troops around it doesn't seem to be the 32,000 troop limit.

[Edi]

If you persist in a game for 2800 turns, you are going to run to the 32k limit even if Ashen Empire isn't in play. Pangaea is one good candidate, since Pans generate freespawn maenads.

In any case, if you play games that last that long, you need to make sure there are as few freespawn generating variables in play as possible. That means no Pangaea and no Ashen Empire.

There is no way to fix the issue for Dominions 2, since development was stopped when Dominions 3 went into production.