RsSepulcher
GregW17
Okay, having just come through the mobs of Sea Spouts, I agree that the lag is unbearable now. I can still somewhat see what I am doing but it is hard to get an attack off now. I do apologize to everyone I gave a hard time to who was complaining about the lag.
As for SS itself, I don't mind it, it's certainly become more challenging, which is a good thing IMO. Gives something to do while we all wait for Chapter 2 to come out.
Now you understand the situation i was in, or anybody else, the lagg is what makes it hard
stare
StarShipAries
Noted:
but you Yelled this :
RsSepulcher
LAGGING IS NOT A FREAKIN BOSS, THATS JUST OUTRAGOUES AND IRRELEVENT, LAGGING IS KNOWN AS A BUG IN THE SYSTEM THAT NEEDS TO BE FIXED, THATS ALL IT IS, MOVE ON FROM THIS STUPID MISDEMEANOR
StarShipAries
Responded:
and then you put down others when they correctly named the Monster...
and when they (devs) gave the monster "lag" a name/ function " Stun" and we knew it (stun=programmed lag)and flagged {it} as an EB (cause it in fact does last long enough to end the connection)
You never apologized for being Rude: but you claim it as yours with this
RsSepulcher
Now you understand the situation i was in, or anybody else, the lagg is what makes it hard
stare
No Now you understand that the site has site-wide programmed " intentional or /and unintentional "Lag" aka "Stun" coding embedded therein..
Now
how do you plan on getting around it..
Maybe there is no getting around it because maybe it is the attempted equivalent to what "passcoding" is to security measures against ... botting ...
Edited once.. clarity of sentence structure
" twice..deleted incorrect word is/replaced with {it}