1
2
Apr 24 2014, 4:42 am
|
|
I reckon it's a conflict between mob.Name, and atom.name. Is there a particular reason that you've defined mob.Name, as opposed to using the existing atom.name variable?
|
What exactly is the difference between the two? Name is the player's inputted name, as defined here:
New |
Well, that's what I'm asking you! ^_^
atom.name is a variable that's defined by default, to denote the printable / viewable name of an atom. By the sounds of it, for your player mobs, the character name is what should be it's value. Given that, I'd remove the Name variable, and just use name. |
How would I change the above code to allow that? I have never worked with atoms before, so I don't even know how to call it.
|
You're already doing it, for loc. loc is an atom variable. mobs are sub-types of atoms, and so ... you're working with atoms all the time!
New And remove var/Name off mob. |
Scratch that. I have, but without actually knowing about it. I have some alterations to make, so I'll let you know what happens in a little bit.
|
runtime error: Failed to write variable Race to savefile players/Alaricus.sav. The value being written was "Human". It solved the problem for a second, but now it seems we have awakened an entirely new beast. (Edit: Actually now that I look at it, the problem was not fixed. I was simply tabbed to a different channel. Apparently, removing Name just makes the error go to another variable x_x) |
That's the only one.
However... I think it MAY be fixed? Loading as well. This is what I have now: mob Somehow, adding an F to the ..() in both Write() and REad() fixed it? I have no clue why, though I suppose it was because nothing was being specified. Still though... wat? |
Well, it does mean you were not passing the savefile to the default proc, yes, so it doesn't know where to save/load.
http://www.byond.com/forum/?post=1557368#comment9817872 I recommended that there. Also, I do still really recommend you don't call Write() directly. |
Well when I try to use "F << src", it says "runtime error: bad output" every time.
|
This'll be due to your saving of icons, overlays and underlays. I guess I'll leave you as you are for now, but strongly recommend you implement the steps talked about here:
http://www.byond.com/forum/?post=1187245 http://www.byond.com/forum/?post=1187381 As it will greatly improve 1. the performance of saves/loads when you 50+ players 2. your ability to debug saving/loading issues. |
Your comment about saving overlays and underlays got me thinking.
mob I read through Ter's tutorial, and got some ideas with tmp variables. Those were all just normal variables being saved, which when using "F << src" was giving a bad output. However, when changing them to temp, it started working properly. Man this was a headache lol. Regardless, thanks for the aid. |
1
2