ya I used spunkygirl's code for my saving/loading and it's been working perfectly: http://www.byond.com/developer/forum/?id=699653
but then I added spells people get in their inventory and all kinds of stuff, and now this happens every time I host:
runtime error: Maximum recursion level reached (perhaps there is an infinite loop)
To avoid this safety check, set world.loop_checks=0.
proc
name: Write
(/mob/Write)
usr:
Revert (/mob/spells/Revert)
src:
Revert (/mob/spells/Revert)
call stack:
Revert (/mob/spells/Revert)
:
Write(
Savefiles/breakmandx.sav (/savefile)
)
Shadow (/mob/spells/Shadow)
:
Write(
Savefiles/breakmandx.sav (/savefile)
)
Hyper (/mob/spells/Hyper)
:
Write(
Savefiles/breakmandx.sav (/savefile)
)
Revert (/mob/spells/Revert)
:
Write(
Savefiles/breakmandx.sav (/savefile)
)
Shadow (/mob/spells/Shadow)
:
Write(
Savefiles/breakmandx.sav (/savefile)
)
Hyper (/mob/spells/Hyper)
:
Write(
Savefiles/breakmandx.sav (/savefile)
)
Revert (/mob/spells/Revert)
:
Write(
Savefiles/breakmandx.sav (/savefile)
)
Shadow (/mob/spells/Shadow)
:
Write(
Savefiles/breakmandx.sav (/savefile)
proc
name: Write
(/mob/Write)
Shutting down after encountering too many critical errors.
runtime error: Maximum recursion level reached (perhaps there is an infinite loop)
To avoid this safety check, set world.loop_checks=0.
proc
name: Write
(/mob/Write)
Shutting down after encountering too many critical errors.
runtime error: Maximum recursion level reached (perhaps there is an infinite loop)
To avoid this safety check, set world.loop_checks=0.
proc
name: Write
(/mob/Write)
Shutting down after encountering too many critical errors.
runtime error: Maximum recursion level reached (perhaps there is an infinite loop)
To avoid this safety check, set world.loop_checks=0.
proc
name: Write
(/mob/Write)
Shutting down after encountering too many critical errors.
Connection failed.
ID:141219
 May 16 2009, 5:02 am (Edited on May 16 2009, 5:34 am)
|
|
Holy spamaroni! Edit that post and remove all that crap, man (leave only a couple of the errors). Even if someone still tried to help you, he may only be able to get around to doing it in a few weeks because he's scrolling down the page... O_o
| |
well now I don't get spammed that instantly and then crash,
but I still get these ALL THE TIME =(: (Title Screen) Damie904 has left... proc name: Savee (/mob/proc/Savee) usr: Saga (/mob) src: Saga (/mob) call stack: Saga (/mob): Savee() Saga (/mob): music() Saga (/mob): music() TrainerAbu: gawd I'm very slowly getting spammed with lots of errors wish they didn't show up for me at least oh well proc name: Savee (/mob/proc/Savee) usr: TrainerAbu (/mob) src: TrainerAbu (/mob) call stack: TrainerAbu (/mob): Savee() TrainerAbu (/mob): music() TrainerAbu (/mob): music() proc name: Savee (/mob/proc/Savee) usr: TrainerAbu (/mob) src: TrainerAbu (/mob) call stack: TrainerAbu (/mob): Savee() TrainerAbu (/mob): music() TrainerAbu (/mob): music() proc name: Savee (/mob/proc/Savee) usr: Nabutso (/mob) src: Nabutso (/mob) call stack: Nabutso (/mob): Savee() Nabutso (/mob): music() Nabutso (/mob): music() and then after awhile it stops and I just get this over and over: proc name: Savee (/mob/proc/Savee) Saga: and make theee new game continue yosh mad bold kewl lettering instead of cursive Saga: and ya proc name: Savee (/mob/proc/Savee) proc name: Savee (/mob/proc/Savee) proc name: Savee (/mob/proc/Savee) I'll post the music() proc: mob/proc/music() help please =( | |
Oh my GOD.
usr, : abuse, booleans wrongly if'd, ... All that, and you even showed us the wrong proc! Show Savee() please. | |
lol everyone freaks out when I post my code here, I'm a noob at clean DM.
Anyways, here: mob/proc | |
What I'm about to show you wont solve your problem, but it'll improve your programming practices a lot.
For starters, the first thing about your script is your method of doing those tips. %20 is completely unnecessary. To stop the winset() from messing with text, all you need to do is encase your text in escaped quotation marks, like so: winset(src, "Tip", "text=\"This is a standard text string.\"") You'll note that's much cleaner and far easier for you to read. As for your method of tips themselves, the logic your using is flawed and unnecessarily complicated. Every time you add a tip, you have to update that rand() and add another if() statement. This is complicated and painful, and no doubt frustrating to you. How about we improve it, so all you have to do is just add the tip? First things first, remove all of that tip stuff, and put all the tips into a list, which I have taken the liberty of doing for you: var/list/Tips = list( That's much easier to read. Now, we're going to use the length of that list as a max and 1 as a minimum in order to find out which tip we're going to use. winset(src, "Top", "text=\"[Tips[rand(1, Tips.len)]]\"") We've now replaced 27 lines of code with 16. (Unless you count the list as a single line of code, in which case, it's now 2. Neat, eh?) The whole thing should look like this: var/list/Tips = list( Much less code now, and all you have to do to add another tip is simply add it too the list. Quick, simple, easy and efficient. You'll also note I've changed the opening if() statement a little. The z-level always exists (even if it exists as zero), with that in mind, the check is now to see if the z-level is less than 12. Now onto the rest of this code... I simply have no idea what you're doing here. The colon operator is bad practice and can lead to easy breaks in your code down the line. Reply in detail with what you're attempting to do here, hopefully myself or someone else can help you with your desired plan (though we probably wont give you answers, just the means to find answers). | |
Wow, thanks a lot~!
In my eyes, I have to use the colons in these cases. I use them when this happens when I use periods instead: "NewStart.dm:943:error:usr.fusedwith.name:undefined var" but if I use colons, I don't get that error and it ends up working. What I'm doing there has to do with my fuse verb, which makes it so 2 people can become 1 person. (That fusedwith variable is set to refer to the user they're fused with.) They're then able to move as the same character and have 1 name called their fused name. It's always worked before and still does, so yeah. The part with the Obama variable and medal just has to do with a medal I have in my game that the user gets if they've spent 10 MP being fused with someone else. And the savee proc ya said you don't know what it consists of is in this reply: http://www.byond.com/developer/forum/?id=699912 apparently that's the one that gives me errors in the game when other people join when the game auto-saves every 50 seconds using that music proc. But yeah =3. | |
If you need to use the colon for something to work, you know you're doing something wrong.
In your case, it's because the "fusedwith" variable isn't defined to be a mob. So you've gotta make it;
mob/var/mob/fusedwith
This is often used with projectiles, to set the "owner", the user, the person who fired it.
obj/var/mob/owner
| |
Holy Gonzolie (dunno I just made up that word now) that actually makes it work with periods now, thanks :3.
Now I just need the savee proc problem fixed =( http://www.byond.com/developer/forum/?id=699912 but ya. Yosh =3 | |
So the error happens when another player joins? o.O; Meh.
Try making the spawn(500) a sleep(500), because, besides the code still being massive, I can't find anything that points to a loop. | |
wellzz
I found out what happened in the first post and fixed it so that the loop errors stopped, but then http://www.byond.com/developer/forum/?id=699840 that happened instead. When people's music procs happen, I'd get this: proc name: Savee (/mob/proc/Savee) usr: Saga (/mob) src: Saga (/mob) call stack: Saga (/mob): Savee() Saga (/mob): music() Saga (/mob): music() Saga being whatever their name in the game would be. Then, after awhile, the errors would change to just saying this: proc name: Savee (/mob/proc/Savee) and it'd appear whenever their music proc auto-saves them by using the Savee proc, and I think also when they hit the Save verb themselves which also loads the Savee proc. Oh, and I just tried changing spawn to sleep and I can't get it to work right but yaaa | |
Well, dunno if you're still using 'usr' in the proc, but that's definitely bad. Use 'src' or arguments.
Also, in your DM's preferences, you can enable it to show the error line in the runtime error. Would be helpful, huh. | |
And next time, don't fill a post like this. It's unnecessary, since all you really needed to post was two or three runtimes.