Jump to content

real_tabasco_sauce

0 A.D. Gameplay Team
  • Posts

    2.684
  • Joined

  • Last visited

  • Days Won

    70

Posts posted by real_tabasco_sauce

  1. 1 hour ago, Acero said:

    I dont know if the fix is a simple xml template change or something more complicated. In the former case, maybe a comunity mod would be all we need to fix this long lasting problem.

    @real_tabasco_sauce

    I think it could be done in a mod. However, after seeing how the com mod split the community in a26, I think a different approach should be taken. If bugs are fixed in the community mod, then it becomes the better version of the game to play, leading to pressure for each addition to be a guaranteed improvement and decreasing the experimental potential of the community mod. I'll lay out my proposition for the community mod in that discussion.

    My understanding is that its too late to fix stuff like this for a27, but it absolutely can be fixed for release 28.

    • Like 4
  2. On 23/01/2025 at 9:37 AM, Gurken Khan said:

    The punctuation is effed. Every description I looked at had periods where I expected commas. Did it get verschlimmbessert automatically? Also "structure" capitalized?

    I hope this release doesn't get rushed out the door.

    How is it effed? I don't see these periods in your screenshot. Look closer? Or maybe highlight them for us?

    I don't remember the description for Boudica being changed in this alpha (edit: 3 years ago for hero garrison, 5 years ago for boudica aura). I think Structure might be capitalized because classes typically get capitalized in descriptions.

  3. 2 hours ago, Gurken Khan said:

    What is "Infantry"?

    Infantry are any foot soldiers.

    2 hours ago, Gurken Khan said:

    And what are "Auxiliaries"

    The cavalry are reskinned to auxiliary cavalry, which have no different stats compared to regular cav. 

    Its not really necessary IMO to have the auxiliary cavs in the structure tree, but conscript spearmen and the legionaries should be. However, this does result in a change in the number of units that appear in the GUI which is unsatisfactory to some.

  4. moving the discussion of champ cav back here, @Atrik @chrstgtr @Feldfeld

    I did some testing to compare the case where standard champ spear cav are outnumbered 2 to 1 by regular CS spearmen (40 spears and 20 champ cav). Both were not upgraded and unaffected by any team or civ bonuses.

    The -1 hack armor change in a27 makes for a more sizeable difference than I expected, with an average of 12 spearmen surviving the battle compared to an average of 8.3 champ spearcav surviving the battle in a26+com mod. It seems the decreased hack armor allows the melee rank ups to compound faster, which effectively punishes the champ cav player the longer they stay in a bad fight.

    • Like 1
  5. 3 hours ago, Atrik said:

    My opinion : a26 melee champ cavs should have been (very slightly) nerfed instead of buffed. They are already extremely dominant. In com mod since the decrease to x2.5, they simply feel totaly out of balance.

    They were not buffed significantly more than other melee units. I agree melee champ cav are out of balance, but is there widespread agreement that sword cavalry and spear cavalry are too? I can't say with any certainty that this is the case. That's why I think further balance changes should be more targeted than returning the counter to 3x.

    3 hours ago, Atrik said:

    after they lost ~17%.

    Spearmen kill melee champcav about 51% faster than in a26, but champ cav also do about 50% more damage overall. This leads to somewhat similar balance, except that in a26 melee champcav are OP because they are a nearly invincible damage sponge, while in the com mod they are OP because they are still pretty tanky but deal legitimate damage.

    With the hack armor change in a27 rc, spearmen kill champcav about 60% faster than they do in a26, which is 5.8% faster than in a26 + com mod. So we will see if the ~6% buff for spears is enough (which is probably wont be), and then we take the next step.

  6. 15 minutes ago, Atrik said:

    A archer need to shoot only 120 arrows to kill a champ cav, that's a bit better then a26 where it was 140.

    Ok joking here, i think it's normal that melee cavalry excel against ranged units especially champs, but i think since you still gave spears only a 2.5 dps multiplier against cavs, that's overall a notable buff from already op champ cavs in a26. My opinion is : buff counters instead of nerfing champ cavs stats. With current balance, it's certain that champ cavs will be way op.

    I'm in for the testing.

    Well there was a com mod version where we had 3x counter spearmen (after melee rebalance), and while it was indeed pretty effective versus champcav, they were a little too good vs the typical swordcav or spearcav rush. I had complaints that just 1 or 2 spearmen nullified a melee cav rush even when substantially outnumbered.

    So, I am keen to see how the -1 hack armor change plays out and then nerf HP to 280 if necessary. Changing the counter back to 3 affects too many other units, especially when most ppl agree its just melee champcav that are really the problem.

  7. Ok, we need to schedule a time window on Sunday where plenty of people can test. We really should do a full 4v4 so we can measure the impact of the extensive performance enhancements.

    My window begins at 6PM or 18:00 UTC until 2AM UTC the following day. I would just schedule other stuff around when others can join up. @Ginnungagap @MarcusAureliu#s Perhaps we can do a "Sunday PRO" TG on the a27 RC?

    Some gameplay items to keep an eye out for:

    • Capture balance: units defend capture attacks proportional to their capture attack, so women do not defend buildings from capture.
      • cavalry capture attack is decreased, yet balance may still be problematic.
    • Champion cavalry nerf is enough?
    • Champion variant balance: cataphract, chariot, longsword

    if you use windows and don't want to uninstall a26, you can follow this guide: 

     

    • Like 1
  8. I've thought about it before. Its an idea with a lot of grey area. Should they block vision too? How would the implementation work to try to shoot over the walls?

    I'm sure it could work, but it would take a lot of figuring out, and I'm not sure if it fits with the abstraction level of the game.

    @Grapjas this could be something interesting to try out with your mod.

    • Like 2
  9. I am most concerned about random maps. Skirmishes and scenarios are more responsible for being "pretty" imo, so if those should be reduced to ~40 maps of the upmost quality, I would be fine with it. With random maps, gameplay comes before beauty, so I'd hate to see good maps get junked because they look bad.

    You will notice with my very first post taking aim at river archipelago, I made a fan of this map upset. Personally, I think its better to keep these seldom-used random maps in the game unless they are truly redundant like Kerala.

    5 hours ago, Stan` said:

    Hiding maps behind options is as good as putting them in a mod IMHO

    Well they already are in the options. With the quick-play mode, I meant to instead put a selection of the best maps into the limelight for new users to quickly get a taste of cool looking maps.

    5 hours ago, Stan` said:

    It's not that many yes. But if you consider ten maps per alpha updated with an alpha every year that's still about 25 years of upgrade. :)

    Well, I'd argue not every random map needs an update. While I can only try to make maps pretty, I can definitely make them more enjoyable and balanced.

    • Like 1
  10. 9 hours ago, Stan` said:

    We have:

    • 81 random maps.
    • 74 Scenario Maps
    • 2 Tutorials
    • 77 Skirmish Maps

    To be honest, its really not that many. The situation could be greatly improved without removal with: better organizing map categories like I tried to do ("Default" category problem), and folding 2,4,6, and 8 player versions of skirmish maps into one map. I think the redundant maps could be removed entirely, and maybe some of the niche maps like snowflake sea rocks could be a good fit for community maps.

    Also, we haven't touched on what is a "quality" map. I think for random maps, playability is the most important aspect, with looks being secondary. However, for skirmish maps, appearance is more important than it is in random maps.

    While some random maps do not look pretty, they are quite fun. I think for this reason and others, it would be just fine to have the highest quality maps be front and center to the user, like through quick play, but keep all the maps accessible in game setup and the map browser.

    So my issue isn't with organizing and cleaning up maps, its just with the "remove first" approach.

    • Like 1
  11. Right, but removing a ton of stuff, even just temporarily, is not a great approach to that. We have new civs, UI improvements, options, and graphics that all contribute to quality.

    I could improve at least 10 random maps by a28, probably more. If you do the same for skirmish maps, we are already close to "done". My point is it shouldn't be a big project or overhaul, but instead a continued effort to do better upkeep for maps.

  12. 1 hour ago, wowgetoffyourcellphone said:

    Would people be more opening to cutting back the number of maps for Release 28 if I strongly emphasize that this would be a temporary thing? Because then each release after that would include more of the excluded maps back in, this time much improved and held up to a common standard. 

    why not instead just improve the maps without removing them first? We can certainly remove truly redundant maps.

    If the concern is bloat and excess options confusing players, then a "quick play" option might be good with a pool of the maps and other options made more streamlined. This could be the basis for a ranked mode too.

    • Like 1
×
×
  • Create New...