I think there is an error somewhere in my coding but i cant find it.Everytime i try to run my game a message comes up saying:
runtime error: Cannot read null.name
proc name: SaveMob (/client/proc/SaveMob)
source file: new_char_handling.dm,63
usr: null
src: Miraiman (/client)
call stack:
Miraiman (/client): SaveMob()
Miraiman (/client): Del()
CheckBan(null)
Login()
Read(players/m/miraiman.sav (/savefile))
Miraiman (/client): LoadMob("Miraiman")
ChooseCharacter()
Login()
runtime error: Cannot modify null.mob.
proc name: LoadMob (/client/proc/LoadMob)
source file: new_char_handling.dm,69
usr: null
src:
call stack:
LoadMob("Miraiman")
ChooseCharacter()
Login()
BYOND(334.839) BUG: bad ref (3:9) in DecRefCount(DM new_char_handling.dm:69)
and a message in red letters doesnt stop taking up space on the chat room part of my game it says:
BYOND(334.839) BUG: network message underflow (88,1).
PLEASE HELP!
ID:148765
Oct 9 2002, 2:45 am
|
|
Miraiman wrote:
[snip] BYOND(334.839) BUG: network message underflow (88,1).[snip] I was getting this one earlier today. I was guessing that it was a problem with the Dantom servers at the time. (Meanwhile, RoadRunner has been horrible in my area so it could have been related to my connection.) |
In response to ACWraith
|
|
I have Road runner too, it keeps lossing connection :(. Mostly while im not home, but i do check my site while im at school so i know. GRRR on them.
|
Two problems:
First, you're handling your bans in entirely the wrong place. A ban should be handled in the first Login() or before (in client/New()).
Second, since you have null.name popping up as the culprit, there's your clue; whatever you put before .name is null. If you'd posted code, we could point out immediately what the problem is, but you didn't do that. When you post in Code Problems, include code.
My guess is your SaveMob() proc is peppered with usr, where usr shouldn't be used at all.
Again, we'd need code to tell what the heck is wrong with this one.
However, "Cannot modify null.something" is the easiest bug to find and fix.
This is a BYOND bug, and what you should do is package up your code (with the other bugs included) and send it off to [email protected] with an explanation of the bug.
This is probably related to the other one.
Lummox JR