The 'missing' bosses/monsters

[LennyLen]

But Ive never met any "new" monster type.

Hmmm. When I said I tested it, I meant that I just loaded up Diablo and then ran the .dat file through DHack to make sure there were no errors. I didn't actually play it.

It might have something to do with the seed size of the monsters so I'll try changing them to see if that helps.

Dont worry about problem with Dhack. If you ask Lenny, he can make changes right in Diablo.exe file and send that file to you. Its just minor modification of his nice C program. If he will be so kind of course ...

Actually, It'll be easier to modify it to create a .mod file that works with the DPatch utility I put in my last post. I designed the .mod format to be identical to the .dat format. The only difference between them is that the .dat file has memory addresses, while the .mod file has file addresses.

When entering some dlvl, both files disapear from Dhack. Sometimes in 10 dlvl, sometimes in 11 and sometimes never (no "new" monster type was picked up). I think it happens in first dlvl you enter AND where the game initially placed new enabled monster types.
Player himself even doesnt recognize that something happened. Dat files are threw away and Diablo do monster placing over again.

Weird. I suspect that has something to do with the next problem.

Look what happens when I deactivate and reactivate hacks:

That's a bug/feature with DHack. If you overwrite the same of area in memory twice in the same hack, it only reverts the second overwrite when the hack is deactivated. Then when you try to reactivate it, you get an error, since the value at that memory address no longer matches what the hack says should be there.

This can be worked around by changing the second value on each line (the values are <address> <old data> <new data>) to **. I prefer not to use ** myself, since there's a good reason why the memory checking routines are there.

Or I can just change the way that I created the .dat file. It was simpler to turn everything on, then just turn a couple of monsters back off than to turn each individual monster on. However if I take the second approach it will stop some memory locations from being overwritten twice.

I also suspect that doing this will solve the problem of the hacks disappearing from DHack.

I'm a little too hungover at the moment to do any coding, but I'll see how I feel this afternoon.