ID:146751
Feb 19 2005, 6:10 pm
|
|
mob Problem: It won't warp me to my save_x,save_y and save_z coords. ~>Jiskuha | |
Jiskuha wrote:
That sends me to a blank screen. Are you reading it if there is no savefile or anything? | |
client I get the "Save loaded" part so that's working fine however when it goes to Load() it gives me a blackish screen. Any suggestions? ~>Jiskuha | |
The only potential problem I see with this code (although other code posted on this thread would be a better choice) is that you're using Move() to move the player, which is a bad idea because that location might be taken. Set src.loc directly instead.
You should also have a fallback location if none is available from the savefile. I.e.: loc = locate(last_x, last_y, last_z) Lummox JR | |
(although other code posted on this thread would be a better choice) So you are saying i should use the method another's example shows me? ~>Jiskuha | |
client Here is what keeps happening. I log in load my save and then after i load my save file it bumps me back to the beginning of the testers() proc. Any help? ~>Jiskuha | |
Of course Tester() is being called when you load a mob from a savefile. When you load the mob it loads with the same key and all, which in turn switches your client over to using that new mob. (Plus, you're loading directly into client.mob, so you're also forcing it to be set as your new mob.) Logout() and Login() are called implicitly whenever you switch mobs.
What you'll need to do is probably set some sort of var that will signal that this mob has just been loaded and doesn't need to call Tester() when it logs in. You have a few other problems, though, that need addressing first. First of all, your Load() proc is actually much much worse off than it was before. You're loading x,y,z directly into mob.x, mob.y, and mob.z; that's not going to work. You have to load directly into local vars just like the other code in this thread did. Your load code actually worked before (as far as setting the player's old position is concerned) because it did something similar to that. One other big problem is the infinite recursion in Tester(). That is, the proc is calling itself just to loop--which it doesn't need to do in this case--and it's doing so without calling spawn(). In fact there's a security hole here because 1) anyone can just keep entering passwords indefinitely, and 2) if they do so without success, it will cause a runtime error. Wrong: src << "<small>Please input Testers pass code." Right: // always close your HTML tags Lummox JR | |
client/proc/Save() I tried that and i removed the testers proc however i am still getting logged out on load. ~>Jiskuha | |
New system(AGAIN!)
mob/verb/Save() This one now wont load. ~>Jiskuha | |
Is it really so hard for someone to help me? I've tried to re-program this thing multiple times to get a working code.
~>Jiskuha | |
Bump again.
~>Jiskuha | |
You really haven't been posting enough code for anyone to help you further. You've been making such drastic changes in fact that not posting some of those procs made it impossible to figure out what was going on. If you screwed with Login(), you should've posted Login(). You should post Logout() too since you keep logging out during a load.
Bumping your post over and over is useless if you're not going to provide enough information. Lummox JR | |
My login/Logout is simply this:
mob and for testing purposes my saving system is two verbs: mob/verb/Save() Problem: it still does not work(Like before) even with the testers proc removed. ~>Jiskuha | |
No wonder your players are logging out when they load a character. Logout() isn't deleting the mob itself; it's deleting the whole client.
When a character loads, there's going to be a change of mobs involved, which means Logout() and Login() get called automatically. Since Logout() calls del(src.client), the client goes bye-bye. Lummox JR | |
try that