Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Pages: 1
Offline
same problem for me
Toop tried to prank us all.
World is over
We are dead.
TOOP TRYING TO CREATE TOOPBOT OR ALT!! NOOOOOOOOOOOOOOOO!!!!!!!!!!!!!!!!!!
Offline
Toop killed it
How? All he does is graphics
thanks zoey aaaaaaaaaaaand thanks latif for the avatar
Offline
Michele wrote:Toop killed it
How? All he does is graphics
I think they are referring to when I used /killroom to empty my level because it was disconnecting people on there constantly. I also told them to disperse and play a less laggy world before sinking my world.
Offline
Offline
same for me, also is ee dying? because of unity? unity you killed us all
Unity sends its regards
Maverick: Started up on a 6, when he pulled from the clouds, and then I moved in above him.
Charlie: Well, if you were directly above him, how could you see him?
Maverick: Because I was inverted.
Offline
same for me, also is ee dying? because of unity? unity you killed us all
I think it's that Player.io is having issues, the website causes some lag, and something to do with flash. Unity and html5 in addition to other optimizations would actually save EE from the lag hopefully :].
Offline
JohhnyCraig wrote:same for me, also is ee dying? because of unity? unity you killed us all
I think it's that Player.io is having issues, the website causes some lag, and something to do with flash. Unity and html5 in addition to other optimizations would actually save EE from the lag hopefully :].
oh ty for letting me know
Offline
JohhnyCraig wrote:same for me, also is ee dying? because of unity? unity you killed us all
I think it's that Player.io is having issues, the website causes some lag, and something to do with flash. Unity and html5 in addition to other optimizations would actually save EE from the lag hopefully :].
what is hmtl5?, i know just hmtl color code
Pages: 1
[ Started around 1732697836.1492 - Generated in 0.115 seconds, 12 queries executed - Memory usage: 1.54 MiB (Peak: 1.71 MiB) ]