Jump to content

Eagle_cz

Leader
  • Posts

    6,089
  • Joined

  • Last visited

  • Days Won

    172

Posts posted by Eagle_cz

  1. fixed ...

    and what else what fixed/reworked?

    Quote

    * fixed debriefing chat window cursor was broken on overrun
    * added map bias display on /statsdump command print
    * added partial GUID display on /statsdump command print
    * added partial GUID display on /players command print
    * fixed SR resets to 0 in some cases
    * added skill rating logging on map end
    * /statsdump is now printed on map end by default
    * sr now takes into account reconnection to calculate total time played
    * improved simple item visibility
    * fixed sudden nades/rnades disappear
    * fixed arty/airstrike falling sound doesn't cut off on impact  
    * fixed airstrike/artillery missiles hit sky boundaries
    * highlighted simple icon weapon that is currently being held
    * fixed satchel didn't disappear on player death
    * fixed unset mg spread was too high in standing stance
    * added /specuninvite command to uninvite spectator from speclocked team
    * added specinvite status display on /players command print
    * fixed shoutcaster logout didn't unfollow speclocked team
    * fixed taken objectives are now dropped on shuffle with no restart
    * fixed set weapon view origin was incorrect in spectator mode
    * fixed bad command byte, leading to sudden movement corruptions
    * fixed HP bonus was incorrectly displayed on first spawn
    * fixed weapon selection was lost after team swap/move
    * fixed empty name in debriefing player list when awarded players disconnect early
    * reverted max members per fireteam to original value (6) (for future feature implementation)
    * increased default max fps value to 125, adjusted fps value selection in menu
    * added chat mention highlighting using @ symbol
    * added name auto completion on tab press in message box
    * fixed phantom bullet tracers
    * fixed corpse were not properly interacting with floor

     

  2. merrychristmastm.png.d534e07804b7c73f1aa0374169851213.png

     

    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 :)

    • Like 9
    • Sad 1
  3. 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?

  4. 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

     

  5. ...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 ?

  6. 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 ...

     

  7. 1 hour ago, Mister J said:

    Does that mean we can't use any commands until then? Currently it's impossible to keep order on the server. Or is it an error that all commands are now gone?

    Had to teamkill Pirata today to stop him from mortaring Allied spawn.

    lol ...

    ok, it's fixed now

    • Thanks 3
×
×
  • Create New...