Ok, so ive got a handful of new monsters that ive just put into one of my monster test areas. I walk into a room in my test loop and the bbs crashes with the following error: wgserver.exe - Access Violation. Attempt to read from: 100.
Last time i saw this, was attempt to read from 0 and you guys pointed out that I needed to activate mods, but thats no longer the case.
I suspect there is something wrong with one of my monsters, and i would assume its one of the two in the room when the board crashed. Does anyone know what I could have done in the monster info that may have caused this?
I have a db export of the two monsters in the room with me when i crashed it if someone would like to look them over. Let me know either your email addy or your im contact info and ill get it to you.
Attempt to read from 100...crash
Re: Attempt to read from 100...crash
Take the monsters out of the room. Test. Insert one moster in room. Test. Insert other monster in room. Test.
If your board crashes when you take both of them out, you have a room problem. Compare the room to similar rooms throughout the realm.
If your board crashes when you put the first monster in, that monster has a problem. Compare the monster to similar monsters throughout the realm.
If your board crashes when you put the second monster in, that monster has a problem. Compare that monster to similar monsters throughout the realm.
If you fix one monster, and the board still crashes, re-test, with different variables.
If your board crashes when you take both of them out, you have a room problem. Compare the room to similar rooms throughout the realm.
If your board crashes when you put the first monster in, that monster has a problem. Compare the monster to similar monsters throughout the realm.
If your board crashes when you put the second monster in, that monster has a problem. Compare that monster to similar monsters throughout the realm.
If you fix one monster, and the board still crashes, re-test, with different variables.
Re: Attempt to read from 100...crash
Well, i pretty much know that the problem is with one specific monster. The board didnt crash until that monster was inserted. Im just trying to figure out what variable about the monster could be causing the problem.
If i make a change to a monster, what do i need to do so that when i bring the board back up, all instances of that monster will be updated. I.E. if i change the hp of a monster, it seems like i have to kill the monsters previously in the game before they gen with my changes applied. Just so you know, my current edit method is to edit files copied to their own folder, compile update, bring down the bbs, copy the update to the working directory, bring the bbs back up.
If i make a change to a monster, what do i need to do so that when i bring the board back up, all instances of that monster will be updated. I.E. if i change the hp of a monster, it seems like i have to kill the monsters previously in the game before they gen with my changes applied. Just so you know, my current edit method is to edit files copied to their own folder, compile update, bring down the bbs, copy the update to the working directory, bring the bbs back up.
Re: Attempt to read from 100...crash
I believe that is the best way to do it. You will always have instances of old monsters floating around left in memory and whatnot, until you kill them. Usually you have to kill a couple before any of the new ones will regen, that's just how it goes.
Re: Attempt to read from 100...crash
but if something about the old monster is crashing the bbs...then i never will be able to kill them
Re: Attempt to read from 100...crash
Run an offline recovery. When you see "Deleting Active" that's basically deleting every monster in the realm and replacing it/regenerating it.
Also..what version of mud are you running?
I don't know if anyone elses mud treats them as good..but I edit the files in my WG folder, fuck backups. If I got backups and something fucks up, nothing will ever get done..if something fucks up, it gives me more incentive to fix it that the BBS can't be up until I do. I never have problems though.
Anyway..when I edit things, then compile an update, I run a cleanup.
After the cleanup, the changes took affect on the already alive monsters. IE - Before I reset by MUD, I changed the Beholder halfway in to drop 6 eyes. I edited it like that, while the BBS was up, compiled an update and ran a cleanup. After the BBS came back up, no recovery, the 1st beholder to die (as in, he'd never been killed thus far on the BBS) dropped 6 eyes.
My edits go in as I do them, I don't have to kill/respawn monsters.
Also..what version of mud are you running?
I don't know if anyone elses mud treats them as good..but I edit the files in my WG folder, fuck backups. If I got backups and something fucks up, nothing will ever get done..if something fucks up, it gives me more incentive to fix it that the BBS can't be up until I do. I never have problems though.
Anyway..when I edit things, then compile an update, I run a cleanup.
After the cleanup, the changes took affect on the already alive monsters. IE - Before I reset by MUD, I changed the Beholder halfway in to drop 6 eyes. I edited it like that, while the BBS was up, compiled an update and ran a cleanup. After the BBS came back up, no recovery, the 1st beholder to die (as in, he'd never been killed thus far on the BBS) dropped 6 eyes.
My edits go in as I do them, I don't have to kill/respawn monsters.