Kaiochao's Site - BYOND Error: bad mob

BYOND Error: bad mob in Developer Help

ID:926327

Aug 12 2012, 2:12 am

Code:

mob/player
    Read(savefile/s)
        . = ..()  // <-- Line of the error
        icon = initial(icon) // because I don't save icons

Problem description:
runtime error: BYOND Error: bad mob proc name: Read (/mob/player/Read) source file: mob.save.dm,8 usr: null src: call stack: Read(worlds/poooop/players/kaiochao... (/savefile)) load() Login() Login() Kaiochao (/client): New() Kaiochao (/client): New() Kaiochao (/client): New()
It just started doing this. I'm not sure what I've changed to make it start doing this. It's not being nice anymore. If I had more information, this would be a bug report, but I don't like filing bug reports because I usually don't have very much info on the "BYOND BUGs" I come across.

Oh, and sometimes Dream Daemon and Dream Seeker instantly go to the "X has stopped working" window.

(BYOND 496.1145, Windows 7 64-bit)
...Actually, I installed the 497 beta and re-installed 496 to see if it'd fix it. I guess it didn't.

#1 Aug 12 2012, 2:38 am
DarkCampainger	Can you show us where you're loading the savefile? Are you using the `>>` operator to do it, or are you calling Read() directly? (it should be the former)

#2 Aug 12 2012, 8:19 am
Kaiochao	I'm calling Read because it hasn't been working otherwise, but I'm probably just doing it wrong.

#3 Aug 12 2012, 9:46 am (Edited on Aug 12 2012, 10:19 am)
Kaiochao	I use Read because the other method creates a new mob, while Read sets values to the current mob and avoids multiple Logins. I recently included Forum_account's Pixel Movement. His libraries don't seem to play nice with saving/loading. Somehow, including Pixel Movement just causes my savefile (kaiochao.sav) to become over 1800kb before DS/DD crashes. I don't get it.