Jump to content
Website Updates and Upgrades are still underway! We don't expect any further downtime, but we thank you for your patience as we restore themes and other elements including the Chatbox.

Xenalite

Member - (Inactive Duty)
  • Posts

    149
  • Joined

Posts posted by Xenalite

  1. 28 minutes ago, =VG= SemlerPDX said:

    Yea, but that's just a good reason to use a non-standard port, right?  We practice that at VG.  I don't think the dedi would get attacked "less" if there was another 'dummy' server on 5.9.23.136 with a standard FTP port, but I'll defer to the actual professionals here as always.

    Not really. Non-standard ports may filter out your background noise attacks, normal stuff you said happens every day. It does nothing for targeted attacks - these will easy find out every open TCP port on your IP. That's how I know how insecure your servers are. But the practice is not entirely stupid - these insecure servers are called honeypots and have logging enabled on them to catch would-be attackers, log their details, methods of attack to block them later on legit systems.

     

    Going back to Win 7 / 10 stuff though - you are frequently better off having Windows Update enabled in the background and it just pulls an update when it thinks it needs one. Security patches for vulnerabilities are important things. Feature updates are more likely to break stuff, but that's why you might not want to get preview / latest features as soon as they come out. While Win 7 will be out of support, they won't just magically drop dead - it just means when new vulnerabilities are discovered on this system, they will no longer be patched by Microsoft. With Microsoft being very open about their development recently, you are more likely to be protected from latest vulnerabilities on Windows 10.

    I always have a hard time understanding people's problems with Windows 10. It's almost like they'd break any system no matter what you give them. I bought a Win 10 Pro edition OEM for £25. I use default Windows Defender AV, enabled updates and don't browse the internet like a retard, and everything is fine for years now. I managed hundreds of VMs with various editions of Win 10 and Win Server 2016/19 and only 2 ever had issues post-update.

    • Upvote 1
  2. Ordered leaderboard of shame:

    Place  Tks Name
    -----  --- ----
        1 1473 Volod.41
        2  733 45th Golden_Days
        3  440 Kemerovo
        4  434 =VG= deathdealer
        5  425 .SUGAR.
        6  421 Alucardednoc
        7  412 TABARNAC
        8  396 Xenalite
        9  371 UA Evgneniy
       10  329 Ranger>>>12<<<
       11  322 Hellcruizer
       12  316 Lowkey95
       13  309 =VG= Skitalez
       14  305 Whiskey-Mike
       15  304 BLYAT Meaww
       16  295 Daniel75
       17  290 Condrad
       18  289 FinWeirdo
       19  271 Nexwizz
       20  264 43rd DannielsCz
       21  257 =VG= 0100011000101
       22  250 X0R
       23  227 Hsc20
       24  214 Avaga
       25  203 J4SON
       26  201 =VG= STARK58
       27  195 Skirmisher
       28  190 Stainburger
       29  189 Bugti47
       30  178 Karamara
       31  178 Ger-man
       32  169 =VG= Keed
       33  164 Warghost
       34  161 =VG= Kavelenko
       35  161 Lonewolf-PR
       36  157 Sgt. Dragon
       37  153 =VG= 22..12
       38  153 =ZF= Honeybadger101
       39  148 Spartanish
       40  144 =VG= Ryan.TT
       41  143 SSgt HaterOneActual
       42  129 =Ro= .Blizzard.
       43  129 Eurostep
       44  127 Johnny__Rico
       45  126 HTCY Kuro212
       46  124 PFC. Blackburn
       47  122 Zviking
       48  120 CptHawk
       49  115 2EZ
       50  114 Lon-Nolan
       51  112 Spoden
       52  112 Fishsticks
       53  110 MixedArsenal
       54  110 =VG= Acro1
       55   95 Z.Silva
       56   90 Magnum-{FR}-
       57   88 Batmeme
       58   83 Carkidd
       59   80 =VG= Asquirrel
       60   79 Saharian
       61   77 =VG= BinkleDinkle
       62   75 =AMPHETAMINE=
       63   75 Necrodude
       64   74 Kiddcar
       65   74 TimeTooTock
       66   69 JohnnyTightLips
       67   65 Crustysock
       68   64 Vipy TSMNF-Viper
       69   58 Grizzly.Wilson
       70   57 InchPincher
       71   55 Beachdog[PL]
       72   55 Agenteta
       73   53 Fiester
       74   51 PaloAlto
       75   46 Hoops-320
       76   41 Stormtruppen
       77   40 =VG= Fastj@ck
       78   40 FPSGeraud
       79   37 Rokk
       80   37 Wolfsschanze
       81   36 G0nz0
       82   34 =VG= Vanillapop
       83   34 TRYbol
       84   33 DarkCeltic
       85   32 Risiko94
       86   32 SpessNL
       87   31 Jarvin
       88   31 CNJ CodeNameJonathan
       89   31 Legionnaire93
       90   28 Banditbhbf
       91   25 TBF deadxangelqc
       92   25 Dagger61
       93   24 Chickenjason123
       94   24 Rev Cyanide_CN
       95   23 =VG= Sausag3
       96   23 Dr._Phil_Perlmutter
       97   18 =VG= Rotblut
       98   18 =VG= Orracis
       99   17 =VG= m823us
      100   16 SemlerPDX
      101   15 =VG= Melon_Muncher
      102   14 SoftBullet
      103   13 2Polev
      104   11 JCLA3114
      105    5 PWNED-Life
      106    5 =VG= bejaki
      107    4 Knifer
      108    4 PissBlitz

     

    • Like 3
    • Upvote 2
  3. Could we try playing COOP with players + bots on both sides? Some arguments for it:

    - Easier to seed maps with low pop - you get some bots to help you out.

    - Get to play Opfor.

    - Get to play more maps, which are very boring with bots on 1 side: Beirut, Saareemaa, Burning Sands etc

    - Harder difficulty - you don't know if enemy is a bot or human.

    - In general an interesting change to break up years of the same pattern. Veteran players know exactly what bots will do.

    - Other side gets to use area attack / deployables / smoke.

    • Upvote 1
  4. 2 hours ago, SSgt. HaterOneActual said:

    They say they fixed some shit...

    COOP

    • Fixed issues with kit selection for MEC.
    • Fixed crashes with vehicles going outside of map boundary.


    LEVELS:

    • Kashan Desert
      • COOP32: Fixed crash.
    • Beirut
      • COOP64: Fixed crash.
    • Outpost
      • COOP64: Fixed crash. Fixed combat zone issue for Polish team.
    • Operation Falcon
      • Fixed issues with vehicles not working correctly due to not being assigned to correct team.
    • Operation Soul Rebel
      • COOP64: Fixed crash.
    • Yamalia
      • Fixed deployables being very bright.

    COOP:

    • Added single operator variation of multiple vehicles that didn't have them yet.
    • Updated AI weapon usage ranges with various improvements.
    • Updated ZIS-3, ATS and SPG-9 ranges to be more responsive when used by bots.
    • Fixed chat block initiating too early and python timing issues.
    • Fixed vehicles not spawning on their correct spawn timer in COOP gamemode.
    • Fixed GB Scorpion BF2 reload sound not working.
    • Fixed PL T72 BF2 sounds not working.
    • Outpost Added COOP layer.

     

    This is from a year ago.

  5. 4 hours ago, =VG= Melon Muncher said:

    I thought about making a combat area that insta kills when you fly too close to the south border but it's not possible to do serverside.

    I did that in old BF2 with Python modding. It killed a player within a certain box area. Don't think the same is possible in PR.

    Also, killing the player doesn't do it - it's the vehicle that crashes the server. I once realized I won't make it and will fly sotuhbound, so I quickly suicided, and the F16 on Bijar still crashed it.

    • Like 1
    • Upvote 2
×
×
  • Create New...

Important Information

Terms of Use and Privacy Policy