This topic was last updated by  The New Guy at 06/08/2017 06:10 pm

  • Author
    Posts
  • #1045

    The New Guy
    Moderator

    These suggested ranges & basic formulas help bring a semblance of balance & order to the rather under-defined and seemingly mysterious task of how to grant weapons, props, and items to the environments of HL2MP games that are to be ‘competition worthy.’ Please remember that the winner of the FiOS Grand Tournament as well as Valve as a whole (through their respective actions and more relevant inaction) did not ever consider HL2DM to be “competition worthy.” You, dear reader, may be of a different opinion – as I most certainly am – but the competitive Arena FPS scene as a whole would concur with honest assessment of “Micahwave.” The goal of these guidelines is to provide HL2MP games with a recursive ‘backbone’ that would support more relevant, more understandable, and ultimately more ‘watchable’ competitive play.


    Every hopeful ‘sport’ has to go through a process I am currently attempting to postulate – such as when the ‘NFL’ had to take a hard look at itself and incorporate a new ‘forward-pass’ additive that was widely-considered to be abhorrent at the time. The forward pass would slowly prove to NOT be a bad idea in any regard. I really wish Teddy Roosevelt was around today in order to knock some sense into to a few certain people (politicians) the same way he helped drive home the forward pass idea, but I digress.



    ----------------------------------------------------------------------

    NewGuy Map Classifications:

    ----------------------------------------------------------------------

    Despite what some of you may think, no map used in any league up to this point was ever ‘good’ for anything ‘more’ than a 2v2. Many leagues tired running a 4v4/3v3-based season in a misguided attempt to feel more like Valve’s preferred ‘skill-based’ product: “Counter-Strike: Source.” And honestly, an Arena Shooter in anything more ‘numerous’ than a 2v2 is hard to watch; as such, I would not recommend a mapper to even attempt to create a ‘big’ enough environment designed to support 4v4 play – but I also would never turn down the opportunity to play-test such a map. I’ll admit, I would be more enthused by such a prospect if it followed at least some of my guidelines, but I doubt anyone will put forth that kind of time for a ‘4v4 product’ that would never be used ‘as intended’ in this day-and-age of HL2DM.


    Anyways...


    Class 0 = 1v1 only.

    Class 0 Examples: dm_tigcrik, dm_biohazard, aim_arena, dm_fraggin, etc.

    (the only map in the above list that follows almost all NewGuy guidelines is dm_fraggin)


    Class 1 = 1v1 or 2v2.

    Class 1 Examples: dm_caverns, dm_lockdown, dm_helix, dm_airfusion, etc.

    (the only map in the above list that follows almost all NewGuy guidelines is dm_airfusion)


    Class 2 = 2v2 or 3v3.

    Class 2 Examples: dm_asylum_rc9 by Valar, and dm_rapidfire_r1/r2, by Abnoksious.

    (I relayed some crappy feedback to abnoksious with regards to rapidfire, as I thought people who had been playing longer than me at that time would know better. I was wrong. This map was also the very first map I ever provided feedback for; as such, it’s not a very polished map in terms of loadout – but still playable regardless. Asylum is far more ‘progressed,’ but still needs some work.)


    Class 3 = 3v3 or 4v4.

    Class 3 Examples: I have yet to find a map worthy of this ‘caliber.’


    Class 4 = 4v4 or 5v5 (And so on & so forth … I guess … idk.)


    ----------------------------------------------------------------------

    NewGuy Weapon Classes & Ranges:

    ----------------------------------------------------------------------


    Precision Weapons: Crossbow & 357_Magnum

    Support Weapons:   Shotgun & SMG (aka Chaingun – read blow)

    Hybrid Weapon:      Ar2


    The majority of weapons are separated into two distinct categories: Precision Weapons or Support Weapons, with the Ar2 able to fall under ‘either’ category with regards to where it spawns relevant to other weapons placed around it. The RPG is a control item, and I can’t imagine anything outside of a 5v5 (or greater) allowing for more than one RPG to spawn in a map. So effectively speaking, you only get 1 Rocket placement to work with. I could entertain the idea of more than one Lambda-Health or Red/Super-Charger, but I have some serious doubts. Read the Control Item section below for more information. Lastly, SLAMS don’t exist anymore. They just don’t. Never try to incorporate them. SLAMS were such a terrible idea which (unfortunately) exemplified how Valve would have preferred this game to remain a pointless ‘casual pub’ game, but the ability to catch-and-reset grenades showed that they grudgingly allowed it to become something more than that.


    As for why I have the SMG listed as a “Chaingun,” that relates to a separate (currently server-side) mod called Half-Life 2: Arena (hereafter referred to as HL2A;) regardless, I humbly (atypical of me, I know) ask & recommend to all mappers to please take the time to place SMG spawns in your map. For HL2DM, this eliminates the need to place smg1_ammo pickups (one less thing you have to account for with regards to preventing the 0-point spawn glitch,) and – as you will see when you apply my ‘gathering flow’ idea – it will ‘feel’ right to fill the ‘gaps’ between a 357 and Crossbow with something other than a Shotgun; otherwise, you will find yourself with too many gosh-darn shotguns in your map.


    By the way, the ‘gathering flow’ idea is rather simple in its interpretation, but can be somewhat tedious to implement at times. In essence, when a player gathers a weapon in a given map, he/she should next encounter a weapon of an ‘opposing’ or ‘complimentary’ type as the player moves (Bhops) around in a ‘path’ away from said gathered-weapon. So, if I am standing on a 357 spawn, going one way I should encounter a Shotgun, whereas going in another would (hopefully) land me a SMG/Shotty; furthermore, as I proceed from gathering one of those Support-Weapons, I should then stumble upon another Precision Weapon which would (hopefully) be a Crossbow. So the ‘flow’ of weapons would be Precision→Support→Precision→Support→Precision with the Ar2 being interchangeable with any part of that ‘chain.’ This may sound simple in theory, but it can be difficult in practical application. Virtually all players like to see this actually occur in maps, but all I ask is that a mapper make an attempt at this ‘gathering flow.’


    Now then, as for the Numerical Ranges:


    [ Class 0 Map ] Weapon Loadout Ranges:

    Crossbows               = [ 2 : 3 ]

    357s                          = [ 2 : 3 ]

    Precision Total        = [ 4 : 5 ]


    Shotguns                  = [ 2 : 3 ]

    SMGs                       = [ 2 : 3 ] (for HL2DM, never more than 2)

    Support Total          = [ 4 : 5 ]


    Hybrid Total (Ar2) = [ 1 ]



    [ Class 1 Map ] Weapon Loadout Ranges:

    Crossbows               = [ 3 : 4 ]

    357s                          = [ 3 : 4 ]

    Precision Total        = [ 6 : 7 ]


    Shotguns                  = [ 3 : 4 ]

    SMGs                       = [ 3 : 4 ] (for HL2DM, never more than 3)

    Support Total          = [ 6 : 7 ]


    Hybrid Total (Ar2) = [ 1 : 2 ]



    [ Class 2 Map ] Weapon Loadout Ranges:

    Crossbows               = [ 4 : 5 ]

    357s                          = [ 4 : 5 ]

    Precision Total        = [ 8 : 9 ]


    Shotguns                 = [ 4 : 5 ]

    SMGs                      = [ 4 : 5 ] (for HL2DM, never more than 4)

    Support Total         = [ 8 : 9 ]


    Hybrid Total (Ar2) = [ 2 : 3 ]


    You have probably noticed that the difference between the loadouts of all these map classes is a +(1) to virtually all respective values, and they would (theoretically) continue on that trend for bigger and larger maps. Unfortunately, the game has been pretty dead these past few years, otherwise there would have been plenty of competitive players who could have appreciated maps that did not feel like a “cluster-f***” back in the more ‘crowded’ & early days of the game. Remember playing a 4v4 on Biohazard in CAL? Or Avalon? Pepperidge NewGuy remembers. It was a very cringe-inducing chore.



    ----------------------------------------------------------------------

    NewGuy Item/Pick-up Ranges:

    ----------------------------------------------------------------------

    This includes “spam,” Large health kits, and suit batteries. Did I forget small health kits? No, I don’t think small health kits need to exist. Only reason they ever did exist was because HL2 was meant to be Single-Player only, and the variance in the different types of pickups you could gather was a positive feature for that Single-Player masterpiece. More variety = more intermittent reinforcement = more shots of dopamine = more brainy satisfaction stuff.


    Numerical Values:

    {Map-Class}+(1) = [ Orbs ]

    {Map-Class}+(2) = [ SMG_nades ]


    [ Class 0 Map ] Item Loadout(s):

    Orbs                           = [ 1 ]

    SMG_nades               = [ 2 ]

    +(15) Suit-Batteries  = [ 8 : 10 ]

    +(25) Health-Kits      = [ 10 : 12 ]


    [ Class 1 Map ] Item Loadout(s):

    Orbs                          = [ 2 ]

    SMG_nades              = [ 3 ]

    +(15) Suit-Batteries = [ 16 : 20 ]

    +(25) Health-Kits     = [ 20 : 24 ]


    [ Class 2 Map ] Item Loadout(s):

    Orbs                           = [ 3 ]

    SMG_nades               = [ 4 ]

    +(15) Suit-Batteries  = [ 24 : 30 ]

    +(25) Health-Kits      = [ 30 : 36 ]


    In essence, you take the numerical value of a given map’s respective (or intended) map-class and add +(1) to that value for the number of Orbs you should have; you would then add another +(1) to that value – or (naturally) just +(2) to the respective map-class – in order to ‘ordain’ the number of SMG_Nades that should spawn on the map.


    Why? Because reasons. Also, I was very inspired by how Sw0t approached dm_lostarena, and every sane person knows that scrims/matches on dm_lockdown would be far more watchable to a larger audience if spamming wasn’t so damn prevalent. Before any one tires calling foul – perhaps you should try a few maps I’m currently converting first and then decide. Virtually every new custom map considered for competition has been reducing the amount of “spam” that can be found for years. And do keep in mind that Valve pseudo-hates all of you and never anticipated that their source engine would have bunny-hopping, which allowed for far more gathering than initially anticipated. Not to mention they never designed a map for anything other than an 8-16 person pub. One could easily say that the idea of a HL2-Multiplayer game was a sudden afterthought, and they hastily threw together 3 maps (lockdown, overwatch, runoff) with Single-Player resources. Oh wait, “one” person did say that. Me. From here https://www.everythingfps.com/topic.php?id=1024.


    As for the Health/Suit values, I found a good sweet spot range for Class 0 maps via Kakujitsu’s converted pg_fragging_yard map. I then figured one should just double those ranges for a Class 1 map, as there would potentially be twice as many people playing (1v1 = 2-players ; 2v2 = 4-players ; Derp.) Those values would then increase for Class 2 maps by a factor of 50%, then potentially by another 25% for Class 3 maps, and then by 20% for the mythical Class 4 map (that will likely never exist,) and so on. In case you’re wondering as of now, in instances where those adjustments result in a decimal – one would always round upwards.


    I should also mention that this part of my “loadout ideas” is the relatively newest part, and the portion most likely in need of adjustment after testing. But, as I mentioned at the start of this post, this is my postulation of what needs to happen to make HL2MP games more competitively relevant and streamlined. I’ll keep learning hammer and converting maps, so if you’re going to provide feedback, do so after some decent play-testing time. I will not entirely entertain or address criticism based on “on-paper” evaluations. That being said, you’re all still welcome to gripe and whatnot. Thank you.


    ----------------------------------------------------------------------

    NewGuy Prop Formula Guidelines:

    ----------------------------------------------------------------------

    This is the oldest “NewGuy idea” and has gone through plenty of testing and tweaking. So I can say with a great deal of confidence that it is the most “solid” portion of this post. But, I have babbled enough already. There are 3 prop-variants which are all required to be usable in any map: Radiators, Boxes, and explosive-Barrels. The formula goes something like this:


    [{Largest single-value of a support-weapon type} (which is always shotguns in HL2DM)] +/- [(25%)] (or [{shotguns}*(0.75)] for the lower-range value of all prop types) followed by [{Map Class}+(1)] for the indestructible props’ (radiators’) upper-range → and then [{Map Class Value}+(2)] to establish the upper-range of both volatile props (barrels) and destructible props (boxes.)


    For all decimal values, one would always round upwards (ie; 9.25 = 10 props of a given type)


    If by some miracle people (other than me) try mapping for HL2A, the first part (value) of that seemingly over-complicated equation would be replaced by the number of “Chainguns” spawning in a given map if that value is > greater than > the number of Shotguns spawning in a given map. The HL2A version of tigcrik (adm0_tigcrik) will attempt to be such a case with (3) Chainguns and the same (2) shotguns found in dm_tigcrik_r2.


    [ Class 0 Map ] Prop Loadouts (given Support-Weapon single-value = 3) ::

    Radiators                   = [(3)*(0.75)] : [{(3)*(1.25)} + {0+1}]

    Radiator Range       = (2) To (5)


    Destructible Boxes    = [(3)*(0.75)] : [{(3)*(1.25)} + {0+2}]

    Destructible Range  = (2) To (6)


    Explosive Barrels      = [(3)*(0.75)] : [{(3)*(1.25)} + {0+2}]

    Explosive Range      = (2) To (6)



    [ Class 1 Map ] Prop Loadouts (given Support-Weapon single-value = 4) ::

    Radiators                   = [(4)*(0.75)] : [{(4)*(1.25)} + {1+1}]

    Radiator Range       = (3) To (7)


    Destructible Boxes    = [(4)*(0.75)] ; [{(4)*(1.25)} + {1+2}]

    Destructible Range  = (3) To (8)


    Explosive Barrels      = [(4)*(0.75)] ; [{(4)*(1.25)} + {1+2}]

    Explosive Range      = (3) To (8)



    [ Class 2 Map ] Prop Loadouts (given Support-Weapon single-value = 5) ::

    Radiators                   = [(5)*(0.75)] : [{(5)*(1.25)} + {2+1}]

    Radiator Range       = (4) To (10)


    Destructible Boxes    = [(5)*(0.75)] ; [{(5)*(1.25)} + {2+2}]

    Destructible Range  = (4) To (11)


    Explosive Barrels      = [(5)*(0.75)] ; [{(5)*(1.25)} + {2+2}]

    Explosive Range      = (4) To (11)


    For further extrapolation, a map like dm_lostarena likely will NOT use the possible/allotted maximum of (4) shotguns, and adm1_lostarena will also only have 3 Chainguns in addition to the 3 established Shotguns of the original map; therefore, dm_lostarena will (and should) have lower prop-values than dm_lockdown or even dm_airfusion. This all ties into how mappers will develop a ‘feel’ for their map as it develops. These ranges give mappers the options they need, while preventing maps from ‘going off the deep-end’ and outright destroying a (for better or worse) crucial part of HL2MP


    It’s simple – there is no one magic number for any kind of map as to how many props it should have. This idea is meant to be adaptive and flexible for mappers as they build. ALL MAPS do need to have all three types of props in order for it to ‘feel’ like a properly concurrent HL2 game across the very diverse maps (layouts) we have. I say this as someone that very much disapproves of the ‘gimmicky’ instant-kill properties of props, but those issues are to be laid at the feet of Valve. The development team could have balanced props like they did with frag_grenades (which is technically a prop with a fuse) since a player can ‘reset’ the timer of an enemy’s grenade that is being cooked within their Gravity Gun; likewise a player should have the ability to ‘knock’ an enemy’s held-prop from their Gravity Gun – forcing the enemy to drop said prop whilst also ‘disabling’ the enemy’s gravity gun for something like 0.5-1.5 second(s.) In such a scenario, the ‘enemy’ player would still be able to switch weapons. This would prevent (or could have prevented) the annoying ‘feature’ of being able to hold a (possibly gigantic) prop indefinitely, allowing players with slower minds/reaction times to achieve a ‘gimmicky’ frag.



    ----------------------------------------------------------------------

    NewGuy Control Item Values:

    ----------------------------------------------------------------------

    This last bit only strictly applies to HL2A maps, but may still help to give mappers an idea of what ‘Class’ of map they are likely to end up with – even in HL2DM. As you envision what theme your map is going to have, do remember that more control times = more complexity needed for a given map in order to allow for these critical items to be ‘housed’ or controlled.


    For HL2A:

    Red/Super-Charger         = (0.45) control

    RPG                                = (0.40) control

    Lambda/Mega-Health     = (0.35) control

    Yellow/Orange-Charger  = (0.30) control

    Green/Blue-Charger        = (0.25) control

    Delta Pickup                    = (0.20) control

    Ar2                                  = (0.10) control


    I would then add up all the ‘control points’ and if I end up with a sum > greater than 1.0 > then the map should be built to be a Class 1 map. If the control point total is less than or equal to 1.0, it’s possible for the map to be made into a Class 0 map, and – as you probably already guessed – if the total is greater than 2.0, then the map should be built to be ‘big enough’ to be a reasonable ‘Class 2 sized’ map. If find yourself so inclined to try and apply this Control Value idea to a HL2DM map, you have to allow yourself a loose interpretation of the ‘final sum.’ Such as 1.1 total control points being the maximum for a possible Class 0 map.


    HL2DM maps are so very strange, and due to the lack of official support, some strange things have been attempted. I’ve seen League 2v2’s on aim_arena to 4v4’s on biohazard. Player’s were desperate for something. Anything. And yet I wrote all this in 2017. Ugh. Well, many of you will think my efforts to be ‘too little, too late’ - and perhaps this is true. But for those of you who would like to try and make the game better, I welcome your feedback.


    #1047

    da11as
    Administrator
    Can you explain what each one of these does:

    Red/Super-Charger         = (0.45) control

    Lambda/Mega-Health     = (0.35) control

    Yellow/Orange-Charger  = (0.30) control

    Green/Blue-Charger        = (0.25) control

    Delta Pickup                    = (0.20) control


    #1048

    The New Guy
    Moderator
    Those items only appear in HL2A, but I guess I should have properly explained what they are regardless.
    I meant to make a separate thread which would explain what all is changed in HL2A, but I got lazy.

    Anywho, Red Charger = Device that gives you 200-suit (which is why I grouped it with a valve-stock SC,) but once 'opened' (by +use) there is only a limited window (currently 4 seconds, but may be subject to change after more testing) in order to 'charge' to that maximum 'suit-value.' After this window expires, the 'charger' is blocked off (effectively emptied or set to 0 HP) and then will re-spawn and become re-accessible after 45 seconds has elapsed. Essentially, the Red Armor that can only be completely 'gathered' once every 50 seconds maximum. As it currently stands in a sever-side mod, this charger is required to give health in addition to suit, but preliminary analysis from some modders tell me that (theoretically) the Red Charger can be reduced to granting (1) health for very (20) suit granted. Almost needless to say, I will keep all of HL2DM well informed about any new developments of HL2A.

    All the other chargers function the same way, but hold less suit.
    Armor/Suit is not "tiered" like in quake, but the 'chargers' color can correspond to their respective 'Quake-Armor counterparts.'
    As for the colors that seem 'new' when compared to Quake - such as the "Orange" and "Blue" chargers - they both have the same practical/effective properties as the "Yellow" and "Green" chargers they are grouped with respectively. The reason for the difference in their appearance/aesthetic is so player's can strategize (use "call-outs") more efficiently; ie: calling out "Orange" is easier than '2nd Yellow' or 'Front/Back Yellow.' Perhaps if any huge maps for 4v4 are made in the distant future, players might still have to say "Front/Back Orange" to their teammates, but alas, that's inherently easier to work with compared to a map that has 4 yellow chargers to
    strategize for. I'll outline more below:

    HL2A Chargers
    :
    ------------------------------------------------------------------------------------------------------------------------------
    1.) Red-Charger         = (200) suit / (4) seconds charge / Respawn @ (45) seconds
    2.) Orange-Charger    = (100) suit / (2) seconds charge / Respawn @ (35) seconds
    3.) Yellow-Charger     = (100) suit / (2) seconds charge / Respawn @ (35) seconds
    4.) Green-Charger      = (50) suit   / (1) seconds charge / Respawn @ (25) seconds
    5.) Blue-Charger        = (50) suit   / (1) seconds charge / Respawn @ (25) seconds
    ------------------------------------------------------------------------------------------------------------------------------

    As for the new (currently hammer/map-based) Pick-ups, aka "Instas" (meaning Instant-Pickup-Item,) there are only 2 of them - the "Lambda-Health" and the "Delta" - and they function similar to Quake's "Mega-Health" & "Yellow-Armor" respectively; but as of now, there are a few slight differences form their Quake-counterparts, and these pickups will only deviate further from Quake-established ideas as the HL2A Mod progresses. I guess I'll outline the current properties of these pickups and then outline what I "hope" they become in the future.

    HL2A Pick-ups: (current)
    ------------------------------------------------------------------------------------------------------------------------------
    1.) Lambda-Health  = (200) total health              / Respawn @ (65) seconds
    2.) Delta                = +(75) Health & +(45) suit   / Respawn @ (35) seconds
    ------------------------------------------------------------------------------------------------------------------------------
    1.) Currently the Lambda pick-up makes the gathering-player 200 health regardless of their HP upon gather.
      → HL2A does have a Quake-like 'Heath-Attrition' (decay) of [ -(1) health every (1) seconds ] when the player is > greater than > (100) health
    2.) Currently the Delta pickup is essentially (3) Large Health-Kits & (3) Suit-Batteries 'rolled into' one item
      → As of now, the max Health/Suit a Delta can render a gathering player would be (100/100)
      → HL2A does have a Q3CPM-like 'Armor-Attrition' (decay) of [ -(2) suit every (3) seconds ] when the player is > greater than > (100) suit

    ------------------------------------------------------------------------------------------------------------------------------


    HL2A Pick-ups: (desired)
    ------------------------------------------------------------------------------------------------------------------------------
    1.) Lambda-Health  = +(160) Health                  / granted over (4) seconds   / Respawn @ (65) seconds
    2.) Delta                = +(75) Health & +(45) suit  / granted over (3) seconds   / Respawn @ (35) seconds
    ------------------------------------------------------------------------------------------------------------------------------
    1.) The Lambda pick-up would give the player +(40) health per second for no more than (4) seconds with no maximum Health-cap or barrier
      → HL2A actual 'Max-Values' for Health & Suit are technically (999) / (999) - however;
      → The "Health/Suit Decay" increases by (4) for every (10) points when a player is > greater than > (200) of either resource
      → As such, a player that is somehow (300) Health would still lose -(1) health-per-second upon gathering a Lambda-Health
      → A player cannot gather more than one Lambda and have the +(40) health per second become additive - it only 'resets' the (4) second timer
    2.) The Delta pick-up would give the player +(25) health & +(15) suit per second for no more than (3) seconds to a max of (125) / (125)
      → The Delta pickup grants (2) actual effects to the gathering player, +(Delta_Health) & +(Delta_Suit)
      → If a given player is > greater than > (125) Health/Suit, the respective "+(Delta_Health/Suit)" effect is not triggered upon gather & any existing effects are terminated
    ------------------------------------------------------------------------------------------------------------------------------
    Lastly, regardless of any possible factors regarding a 'gathering player's' respective Health/Suit values at the 'point-of-gather,' if a player touches a Delta or Lambda, it is always 'gathered' and will respawn @ it's respective value; ie, a player can gather a pick-up and have it grant no real benefit. This is known as 'null-gathering' or 'spiking'

    I hope that covers everything you were wondering, Da1.
Viewing posts - 1 through 3 (of 3 total)

You must be logged in to reply. Login Here