Hello,

I dug up some old code I found from waaaay back, and wanted to tinker with with. It is an old ROM modified codebase.

http://www.mediafire.com/download/lk0q49...

For the LIFE of me, I cannot understand why it will not start! It claims it cannot find mobprobs, when querying the area. The mobprogs are ALL there, however. This was definitely stable code before.

Could someone please have a look. I am sure I will be kicking myself, because this has to be something stupid I am doing.

Please post your error message log.

Fri Dec 13 14:40:23 2013 :: Initializing shared string manager…
Fri Dec 13 14:40:23 2013 :: Initializing random number generator…
Fri Dec 13 14:40:23 2013 :: Setting time and weather…
Fri Dec 13 14:40:23 2013 :: Assigning GSN's…
Fri Dec 13 14:40:23 2013 :: Reading area files…
Fri Dec 13 14:40:23 2013 :: [*****] FILE: darkhave.are LINE: 892
Fri Dec 13 14:40:23 2013 :: [*****] BUG: Mob: 10017 couldnt open mobprog file


I checked in the area file, which calls the mobprog to find what it is calling… I then went in to the directory and the prog file is there. I've included the codebase in the mediafire link above. You'll see it all looks copacetic.

What does line 892 look like?

M 10017 0 guildguard.prg NL


If I remove that line, it does it for the next mobprog. It simply cannot access any of the mobprogs, although they are in the right spot (I've not touched any of the directory structures.

Check file permissions, but more likely, there may be a path environment variable that leads the loader to look in the wrong place. Find your loader function based on the error message and then add a debug message showing where it is looking for the file.

Also, make sure that it's loading mprogs from files already loaded in the area list?
If you try to load ones beyond it, it'll crash.
Reorder them, or simply make all mprogs contained within the same area.
GL bud.

- Dave.

Er wait, your code has separate prog files? Yeah read-error.
See also: Plamzi's answer :P

Find this line, right here. Work out what causes it to be called. Add information (either work out how to use your debugger or just spew more information to the log. Either is good, and both are valid). Information includes, for example, the short description of Mob 10017. What the name of the mobprog file it's trying to open is. Where it is looking for that mobprog file. After that, you should have all the information you need to slay this bug.

Happy hunting!