Page 1 of 1
Help my game is hosed
Posted: Sun Jan 18, 2004 4:14 pm
by PeterParker
I have a problem, suddenly I have all kinds of monsters running around as #)4934!4%. They are everywhere, and different monsters labeled this. Makes no sense, I have tried running recovery, resseting the map file, resetting the active and known monster files with no success. Anyone else ever seen this before? Also Nightmare doesn't show this at all.
Pete
Re: Help my game is hosed
Posted: Mon Jan 19, 2004 1:49 pm
by Hobo_Bill
I saw that on a board that had some screwed up monster dats.. The monsters would randomly change from their normal name to some symbol of some kind and back again, sometimes.. All other aspects of the monsters were the same, but the names were jacked. All I can tell you is it sounds like your .dats are screwed up, IMO.
Re: Help my game is hosed
Posted: Mon Jan 19, 2004 2:41 pm
by syntax53
I have a problem, suddenly I have all kinds of monsters running around as #)4934!4%. They are everywhere, and different monsters labeled this. Makes no sense, I have tried running recovery, resseting the map file, resetting the active and known monster files with no success. Anyone else ever seen this before? Also Nightmare doesn't show this at all.
Pete
sounds to me like corrupted dat files. you said you 'reset' the monster and map files ... did you repalce (wccknms2.dat, wccacms2.dat and wccmp002.dat) with (wccknms2.vir, wccacms2.vir and wccmp002.vir)? what version mud? was it installed as an upgraded or a fresh install? when did it start happening, other then "suddenly"?
Re: Help my game is hosed
Posted: Mon Jan 19, 2004 5:59 pm
by PeterParker
sounds to me like corrupted dat files. you said you 'reset' the monster and map files ... did you repalce (wccknms2.dat, wccacms2.dat and wccmp002.dat) with (wccknms2.vir, wccacms2.vir and wccmp002.vir)? what version mud? was it installed as an upgraded or a fresh install? when did it start happening, other then "suddenly"?
Yes I copied the vir files over the dat files. It happened the same day I posted originally. It was a fresh install of 1.11o, not an upgrade. I'm so lost with this problem.
Pete