I've been having issues on a UC server lately. I'm wondering if anyone knows what's up with it because I've been the ONLY one on the server with this issue, and all of my other games work fine, and I seemingly have no issues on other servers.

Generally upon login, though not limited to it, my player freezes in place whenever I enter the GMAP from an inside level. I can still type and do everything except actually move for about 10 seconds. If it helps, I noticed that sometimes the levels on the GMAP around the one I'm entering will be black for a split second, as if there is a slow loading time.

The only thing I can imagine is this script may be causing issues, but like I said, I'm currently the only one experiencing anything. It wouldn't also explain why some images aren't loading here and there.

function onPlayerLogin() {
for (temp.pl : allplayers) {
temp.pl.addweapon(this.name);
}
}

function onCreated() {
for (temp.pl : allplayers) {
temp.pl.addweapon(this.name);
}
}

//#CLIENTSIDE
function onCreated() {
setTimer(0.05);
}

function onTimeOut() {
if (player.level.starts("dv_ow")) {
addtiledef("DV_Tileset.png", "", 0);
}else{
addTileDef("DV_Tileset-inside.png", NULL, 0);
}
setTimer(0.05);
}

Sidenote: I reinstalled. Like three times.  

Graal PC? Error? In the same sentence? No! You don't say!

But yeah I have no idea so I'll get out...  

The only thing i can think of is that you have a weapon npc added to your client, that others dont, that's causing the problem.. is it only on this server specifically? What i said could be the problem, or someone messed with you, specifying your account in a weapon that causes this issue.  

Maybe you should do your tiledefs correctly. The syntax is addtiledef("tileset","level prefix",type); addtiledef2("tileset part","level prefix",x,y); There are two kinds of tilesets: type 0 are the default pics1-style tilesets; type 1 are the NewWorld-style tilesets that Era and Graal Kingdoms use. The two tileset types are different sizes.

PHP Code:

//#CLIENTSIDE
function onCreated() {
  addtiledef("DV_Tileset.png","dv_ow",0);
  addtiledef("DV_Tileset-inside.png","",0);
} 


You do not need to re-write your tiledefs every five-hundredths of a second. Tiles definitions for each server you've been on are saved in your Graal folder and will load when you are in the level that starts with whatever you put. If you have more than one tileset that would load in a certain level it will load the first tileset listed. If you have tileset parts (addtiledef2) they will sit over the tileset that is loaded with addtiledef. Tileset parts with the same coordinates will only load the first instance of those coordinates. Tileset parts that cover the same areas of the tileset will be shown in the order that they are loaded; the later part will sit over the former. Messing up tiledefs just makes it so you cannot see the tiles, it does not freeze the client. Having stupid timeout loops can freeze the client.

If you knew what any of these commands did you wouldn't be having issues. Stop copying and pasting other peoples' codes and start learning what they actually do.  

Posted by Skyzer

Maybe you should do your tiledefs correctly. The syntax is addtiledef("tileset","level prefix",type); addtiledef2("tileset part","level prefix",x,y); There are two kinds of tilesets: type 0 are the default pics1-style tilesets; type 1 are the NewWorld-style tilesets that Era and Graal Kingdoms use. The two tileset types are different sizes.

PHP Code:

//#CLIENTSIDE
function onCreated() {
  addtiledef("DV_Tileset.png","dv_ow",0);
  addtiledef("DV_Tileset-inside.png","",0);
} 


You do not need to re-write your tiledefs every five-hundredths of a second. Tiles definitions for each server you've been on are saved in your Graal folder and will load when you are in the level that starts with whatever you put. If you have more than one tileset that would load in a certain level it will load the first tileset listed. If you have tileset parts (addtiledef2) they will sit over the tileset that is loaded with addtiledef. Tileset parts with the same coordinates will only load the first instance of those coordinates. Tileset parts that cover the same areas of the tileset will be shown in the order that they are loaded; the later part will sit over the former. Messing up tiledefs just makes it so you cannot see the tiles, it does not freeze the client. Having stupid timeout loops can freeze the client.

If you knew what any of these commands did you wouldn't be having issues. Stop copying and pasting other peoples' codes and start learning what they actually do.

Naturally, I appreciate the time you took to try to help, but that script wasn't added by me; it was added by a fairly known scripter. For what reason, I can't imagine why.

Also, just to close out this thread: the issue was being caused by a poorly scripted weather NPC. I had a hunch that was it, but I was the only person being affected by it for some reason.  

I did say in the post that I didn't think it was the reason for the freezing, I just wanted to make sure you knew that code was wrong.