Eagle_cz

Nice intro Enjoy and see ya on the server!

because it was proper shutdown according to messages in the log file and server uptime (internal server time)

yes, already passed to etl devs... 48312650 ******************** ERROR: MSG_Copy: can't copy 32769 into a smaller 32768 msg_t buffer ******************** 48312650 ----- Server Shutdown ----------

fixed ... and what else what fixed/reworked?

Server was updated to etlegacy-v2.76-704-g690c51a . * SR database was cleared ...list of other changes will follow soon

Welcome to the forum and enjoy your stay here

May the Christmas season fill your home with joy, your heart with love and your life with laughter. Wishing you a very Merry Christmas and we look forward to seeing you in 2020! Merry Christmas guys! @0wN1x thanks for this great poster

problem is that mapscript is completely different than previously used. This will take a time to fix it - im unable to do it till end of week

Thans for info. Admins will look on that...

Welcome to the forums and enjoy your stay here

yeah, server killer .. please no .. .but what about this one ? http://activegamer.net/et/map/658-Secret_Bay_(Final).html

yes, it's connected with g_inactivity, ... passed to etl devs and going to reenable our putspec.lua ... thanks for info!

welcome to the forums and enjoy your stay here

welcome to the forum and enjoy your stay here

Welcome to the forum and enjoy your stay here

Yeah and it happen when player °punda° was in game... its confirmation of my idea about problem with spec chars. I used both clients- old ET and new Legacy. Old et client was unusable once punda wrote something on the main chat. With legacy client i had 'only' few secs lag/freeze and then it worked normaly... any idea @Spyhawk please?

What u mean by crash and by again? Was stable a week or more and non told me about crash. Good, will look into logs...

CONFIRMED! 64103250 ^7^0<=^3TM^0=>^3EAGLE^0_^3CZ^7: ^2punda, can u say anything on the main pls ? 64104100 Item: 8 item_health 64104550 Item: 20 weapon_magicammo2 64115500 say: ^7^b°^xP^yund^xA^b°^7: ^2i agree 64115500 ^7^b°^xP^yund^xA^b°^7: ^2i agree 64115550 WARNING: bad command byte for client 20 64115550 WARNING: bad command byte for client 20 64115550 WARNING: bad command byte for client 20 64115550 WARNING: bad command byte for client 10 64115600 WARNING: bad command byte for client 20 64115600 WARNING: bad command byte for client 10 64115600 WARNING: bad command byte for client 20 64115600 WARNING: bad command byte for client 10 64115600 WARNING: bad command byte for client 20 64115600 WARNING: bad command byte for client 20 64115600 WARNING: bad command byte for client 10 64115600 WARNING: bad command byte for client 20 64115650 WARNING: bad command byte for client 20 64115650 WARNING: bad command byte for client 10 64115650 WARNING: bad command byte for client 20 64115650 WARNING: bad command byte for client 10

...interesting ... hapened only few times (and now too) when player with 'strange' nickname (with spec. char in nicname) saying something ... 63309300 ^7^b°^xP^yund^xA^b°^7: ^2no? 63309350 WARNING: bad command byte for client 10 63309350 WARNING: bad command byte for client 10 63309350 WARNING: bad command byte for client 20 63309350 WARNING: bad command byte for client 10 63309400 WARNING: bad command byte for client 10 63309400 WARNING: bad command byte for client 20 63309400 WARNING: bad command byte for client 10 @ryven any idea pls ?

only this: 44342750 ^7^b°^xP^yund^xA^b°^7: ^2reee 44342800 WARNING: bad command byte for client 20 44342800 WARNING: bad command byte for client 20 44342800 WARNING: bad command byte for client 9 44342800 WARNING: bad command byte for client 20 44342800 WARNING: bad command byte for client 9 44342800 WARNING: bad command byte for client 34 44342850 WARNING: bad command byte for client 9 44342850 WARNING: bad command byte for client 20 44342850 WARNING: bad command byte for client 34 44342850 WARNING: bad command byte for client 20 44342850 WARNING: bad command byte for client 9 44342850 WARNING: bad command byte for client 34 44342850 WARNING: bad command byte for client 9 44342850 WARNING: bad command byte for client 20 44342850 WARNING: bad command byte for client 34 44342850 WARNING: bad command byte for client 9 44342850 WARNING: bad command byte for client 20 44342850 WARNING: bad command byte for client 34 44342850 WARNING: bad command byte for client 20 44342850 WARNING: bad command byte for client 9 44342850 WARNING: bad command byte for client 34 44342900 WARNING: bad command byte for client 9 44342900 WARNING: bad command byte for client 34 44342900 WARNING: bad command byte for client 20 44342900 WARNING: bad command byte for client 9 44342900 WARNING: bad command byte for client 20 44342900 WARNING: bad command byte for client 34 44342900 WARNING: bad command byte for client 9 44342900 WARNING: bad command byte for client 34 44342900 WARNING: bad command byte for client 20 ...and tons of that "Possible DRDoS attack to address xxx.xxx.xxx.xxx:7783, ignoring getinfo/getstatus connectionless packet" messages ...

Welcome to the forum and enjoy your stay

@Boosted bro, when you will have a time, can you look onto that please ? I wanna know your opinion on that. thanks!

lol ... ok, it's fixed now

Welcome to the forum and enjoy your stay here

server updated to version 627-ga46406d SR database was cleared & our 'extended' wolfadmin is not working, so we using default one (until i will fix it).