Internet connection issue

[GSIV-Rumple]

This is a new issue for me: I run the launcher, get in game just fine, then when I run a script like go2 or bigshot, my internet disconnects.

I tested just sitting in game and I am able to stay connected. I also checked not connected to the game, just surfing the internet, watching Netflix, etc and there were no connection issue. Any thoughts?

[Gelston]

This is a new issue for me: I run the launcher, get in game just fine, then when I run a script like go2 or bigshot, my internet disconnects.

I tested just sitting in game and I am able to stay connected. I also checked not connected to the game, just surfing the internet, watching Netflix, etc and there were no connection issue. Any thoughts?

Lich shouldn't be effecting your internet... That is weird.

[Luftstreitkräfte]

this has actually happened to me before but I won't assume it's Lich causing it. perhaps you noticed the lack of connection in your GS window first so you assumed it was the cause.

[Gelston]

this has actually happened to me before but I won't assume it's Lich causing it. perhaps you noticed the lack of connection in your GS window first so you assumed it was the cause.

I'd say that is closer to it. Back when I used to play, I'd first know when my internet went down because GS told me.

[GSIV-Rumple]

Ok, I apologize for mentioning that the running of go2 or bigshot caused my internet to disconnect. Let me rephrase it this way: my internet works fine. Doing everything else. The lack of connection only appears to be ultra sensitive when I run ;go2 or ;bigshot because I can sit in game, doing absolutely nothing, and it will keep me connected. I apologize, I do not accept that there is no correlation.

[Gelston]

Ok, I apologize for mentioning that the running of go2 or bigshot caused my internet to disconnect. Let me rephrase it this way: my internet works fine. Doing everything else. The lack of connection only appears to be ultra sensitive when I run ;go2 or ;bigshot because I can sit in game, doing absolutely nothing, and it will keep me connected. I apologize, I do not accept that there is no correlation.

I don't think it is possible that there is a correlation.

[GSIV-Rumple]

Cool, thanks.

[Luftstreitkräfte]

Ok, I apologize for mentioning that the running of go2 or bigshot caused my internet to disconnect. Let me rephrase it this way: my internet works fine. Doing everything else. The lack of connection only appears to be ultra sensitive when I run ;go2 or ;bigshot because I can sit in game, doing absolutely nothing, and it will keep me connected. I apologize, I do not accept that there is no correlation.

Ohhh.

I have a second issue which happens immediately when I log in. I use ;go2 or other scripts and there is a significant delay before they operate. Try killing the script you initiated and re-running it. That usually fixes the lag. Otherwise you're looking at a 15-20 second delay.

I think it's just a lag connecting you to Lichnet to run the scripts.

-Drew

[DaCapn]

Ohhh.

I have a second issue which happens immediately when I log in. I use ;go2 or other scripts and there is a significant delay before they operate. Try killing the script you initiated and re-running it. That usually fixes the lag. Otherwise you're looking at a 15-20 second delay.

I think it's just a lag connecting you to Lichnet to run the scripts.

-Drew

You're probably talking about the delay imposed by the map database loading.

If you have any script favorited (or auto-starting under current lich parlance) which uses the map database like narost or uberbar (anything that uses lich room data), the map database must be loaded before the script can function. You should notice that login-lag once those specific scripts are loading.

[Tillmen]

Ohhh.

I have a second issue which happens immediately when I log in. I use ;go2 or other scripts and there is a significant delay before they operate. Try killing the script you initiated and re-running it. That usually fixes the lag. Otherwise you're looking at a 15-20 second delay.

I think it's just a lag connecting you to Lichnet to run the scripts.

-Drew

Like DaCapn said, this lag is the map database loading. I feel like I should point out that if you interrupt the loading of the map database by killing the script that's loading it, or if you have two scripts that both start on login that load the map database at the same time, there's a chance your map database will not load completely. This leads to the ever common ";updater update forcemap", which merely downloads an exact copy of what you already have, and loads it again. This issue is fixed in Lich 4.6. That is, the issue of the map database not loading correctly under some circumstances, not the lag issue. If you really want to avoid the lag of loading the map database, you're going to have to not use the map database.

As for the disconnecting issue, try setting Stormfront to save settings locally. Lich can, for some unknown reason, cause a disconnect when Stormfront settings are transfered through the game stream. Stormfront settings are uploaded/downloaded in one big long string. If that string gets too big, either Stromfront crashes or the game disconnects you. This disconnect almost always happens within 3-5 seconds of logging in, which is why I hadn't blamed it on this before. However, I have seen it happen once or twice at random later times. So, maybe it's worth a try.

Besides that, after the disconnect, check the debug-#.txt file in lich\temp (the debug file with the highest number is the most recent). If there's an error message in there, I suppose it's possible that Lich is crashing for some reason. This is also fairly unlikely. The only ways I know of to crash Lich is to break out of the error catching (i.e. Thread.new { exit }), or for gtk to cause a segfault. If you had narost running while using go2, perhaps that would have caused a segfault. But again.. with it working for so many other people, I don't see any likely reason for this to happen. In order to see a segfault error message, you're going to have to launch ruby using ruby.exe (instead of rubyw.exe) from a command prompt.