I Got Alot Of Errors Online, But Don't Get Any Off Line in Developer Help

ID:174750
 
Jul 22 2003, 1:07 pm
When I'm Hosting My Game I'm Constantly Getting The Error:

source file:code.dm,387
runtime error: Cannot read null.HP
proc name: Attack (/mob/PC/verb/Attack)

And Then It Says It's Not Posting All The Errors Or Else It Would Crash!

Can Some One Please Help Me =(
#1 Jul 22 2003, 1:58 pm
I Got The Exact Error:

DarkCampainger (/mob/PC): Attack(null)
runtime error: Cannot read null.HP
proc name: Attack (/mob/PC/verb/Attack)
source file: Code.dm,416
usr: DarkCampainger (/mob/PC)
src: DarkCampainger (/mob/PC)
call stack:
DarkCampainger (/mob/PC): Attack(null)


BYOND Warning: further proc crash messages are being suppressed to prevent overload...

What Should I Do?
#2 Jul 22 2003, 3:03 pm
In response to DarkCampainger (#1)
maybe if you post the code somebody might be able to help
#3 Jul 22 2003, 10:36 pm
That particular error would probably happen when someone (let's call them Person A) attacks someone else (Person B), but Person B has just logged out. Network lag is probably a major contributing factor.

Just check to see if Person B is still in the game (if the var for Person B is null, then they've logged out) before doing any attacking. If Person B has logged out, then cancel the attack.
#4 Jul 23 2003, 3:01 pm
In response to DarkCampainger (#1)
STOP USING CAPS FOR EVERY WORD!
#5 Jul 24 2003, 6:57 am
In response to Jp (#4)
Jp wrote:
STOP USING CAPS FOR EVERY WORD!

You too.
#6 Jul 25 2003, 12:37 pm
In response to Wolf01 (#5)
Lol, Everyone Keeps Telling Me That =)


In One Ear And Out The Other



:)
#7 Jul 28 2003, 2:40 pm
In response to DarkCampainger (#6)
perhaps you should listen then, since that would actually allow people to read your posts without getting irritated at your mangling of the english language. Just an idea...
#8 Aug 29 2003, 6:42 am
In response to Lazyboy (#2)
I am Actually Having The Exact Same Problem... I do not know if this has any contribution to the fact that My Server Keeps Freezing, But I have managed to get Rid Of most of those errors by putting if(M) before every time increment you either change or read The other mob...