Jump to content

wraitii

WFG Programming Team
  • Posts

    3.399
  • Joined

  • Last visited

  • Days Won

    76

Everything posted by wraitii

  1. It actually does not. Compare: 200 HP, armour of 10 everywhere > you can take 200 / 0.9^10 => 573 HP of damage before dying 573 HP, armour of 0 => 573 HP of damage before dying. It's much easier to compare units if they all have a base armour of '0' and HP variations than if they have both.
  2. Agreed, it's a reasonable take. However, the current way ratings work waits for a message from all players until it actually rates the game (to avoid one user cheating, obviously). This means it can't rate a game where one user disconnects. Changing that without making it possible to cheat is not so easy.
  3. large-address-aware is used by default in releases and in the auto build, but not when compiling on your own. It's a flag to enable using more RAM than the default 32-bit limit on Windows, which iIrc is 2GB ?
  4. I fear the reason is a lot more human than you think: there was no "0 armour" anywhere, and so when standardising (mostly @Nescio's work) we still didn't use 0. I actually commented that somewhere on some diff, and I think it's agreed that we should probably use 0 armour. It's basically a series of unfortunate mistakes. Armour is an 'HP modifier', and to make things simple we should have a base HP and then sometimes positive/negative armour on top, but that's not really the system we have (e.g. champions have more armour than Citizen soldier, but that doesn't make sense, they should have more HP instead). --- edit: I'll point out that 0 A.D.'s used of 'exponential armour' is unique as far as I know. It is indeed very convenient: there is really no 'start' point, so you can have -10 or 30 armour and it works the same: 1 point difference is worth about 10% more/less HP. This property _is_ what makes it possible to use HP efficiently, but we still didn't
  5. Yes that's essentially my conclusion as well. I was actually struggling with the name quite a bit, skip_mod_compatibility_check seems a good proposition to me, thanks
  6. I have some project for a tutorial campaign (see that thread), but so far haven't uploaded anything actually concrete. I can make it available on GitHub if you'd like. -- As for campaigns itself, yes you just make a Json like the tutorial 'campaign' and then load scenarios. You don't necessarily need to bother much with triggers.
  7. I thought of that a bit and think those would be 'tags' for the users to look at, not really for the engine. Sure, this would help narrow down the compatibility, but at the end of the day I don't think we'd ever have a perfect system, and it seems like it would mostly complicate things. Which is why I went with this boolean "this does [not] change checksums". And yeah obviously we'd need to check the mods that we approve for signing, but that's not the only way people share mods.
  8. I have a revision for this: D3968. I would like to try and merge it before A25 (btw @nani you might have input on this?) However, it will likely rely on trust.
  9. Anything above 1 would make the units take "2 pathfinding tiles", and would likely make the pathfinding feel completely broken, unfortunately. In A25 I can try to increase the pushing range (since atm that makes the problem worse).
  10. To me, auto-explore is fine so long as it's better to scout yourself.
  11. Alright, I'm going to cut down your complaints by 50%: this is an issue that should be solved. There should not be racist slurs in the lobby. There should also not be cheaters, leavers, and a bunch of other things in the lobby. Am I going to do anything about it? No.
  12. Can't say I disagree. Maybe not 75%, but we could certainly use a 'Maps in need of work' category where we put the garbage. I think 'random' is more easily understood than 'procedural', so I'd rather keep it, but I'm probably OK with splitting the maps in more category for the time being, particularly removing some of the more special maps (arena, the one with no wood, ...) from the general random pool.
  13. My belief is that making it so that it takes time to switch from gathering to attacking mode for soldiers would help with balancing citizen-soldiers considerably. Because then each 'variant' can be considered sort-of-in-vacuum. I'm not sure 'hardcoding' strategies is the way to go, but maybe, you know. That being said, don't expect this to get in A25. I think the target for A25 will be to fix the most egregious issues with A24, so players are happier with the current state of the game, before running into an experiment that tweaks a core concept like this.
  14. [Usual disclaimer that 'WFG' is not a thing and this is just a bunch of people giving some of their free time] We don't have particular plans to address this, mostly because the people currently active are mostly devs who work on other things. That being said, we are stretched rather thin in terms of lobby moderators. It would make sense to have more, but as usual things aren't so simple, because giving moderator power to people implies trusting them, which implies knowing them somewhat.
  15. I must say I find it odd how most civs have no siege option in Phase 2, when you do get some turtling options (towers, etc.) That being said, I suppose it's still mostly eco growth at that point in theory and so making the fights about eco makes some sense. I agree with the notion that fights in 0 A.D. tend to disadvantage the attacker more than in say Age, since the attacker loses more eco. Increased loot might work to counter that. I think turn times are a bit of a decoy problem. I think if there were no archers in P1, you wouldn't notice it nearly as much. That being said, not against bumping them. ---- Still, I agree that late-game gets static easily, because defences are hard to break down. Personally, I think part of the problem is that garrisoning counters capturing much too strongly, making defensive buildings OP. I don't think we've addressed that yet. ---- As for game start, perhaps an option would be to make Citizen Soldiers take longer to train at the CC than at the barracks?
  16. Current plan is to revert to A23, as part of D3898. However, because of how turrets/visible garrisoning has been split from regular garrisoning, the visibly-garrisoned units no longer recover Capture Points. Which means the outpost will go neutral even if garrisoned. IMO, the solution is to remove the 'decay' feature of outposts, and barring changes that's likely what I'll do.
  17. Well, sorta. I think they'd be pretty ugly just scaled up, ideally we'd have moss-covered stones, more dead/rotting trees, more vine-looking stuff. For tropical environments we need completely different setups, too. And for perf reasons it'd be good if these meshes weren't hundreds of props, so we need some dedicated stuff.
  18. I do believe you could find some discussion on this, but you'd probably have to dig a fair bit. Fact is we also don't have 'impassable terrain texture', and a few other things that make 0 A.D. quite liberal in where you can walk. 0 A.D. isn't too dissimilar from Age 3 in my experience in how forests feel, though maybe trees didn't have obstructions in that game? Don't recall. Anyways, it's not completely unrealistic, and I don't think removing obstruction entirely would be necessary. I don't think most forests being passable is actually an issue, overall. However, I think we should have an easy option to make impassable forests, and that (to me) means undergrowth/old growth meshes to take up space and become impassable. I agree that it's annoying that we don't have that. ---- With that being said, and as I've stated before, I think our forests are pretty bad, particularly on random maps, since the trees are kind of all over the place, leaving too little room for construction and making dropside placement awkward. This ties in with forests being passable/impassable - impassable forests need meshes, and passable forests could probably be sparser (overall reduction in # of trees), but have more wood per trees. Fixing all this isn't trivial nor my priority of the moment, unfortunately.
  19. I disagree somewhat. I think the correct solution is to have impassable undergrowth entities, that are much bigger but still gatherable (though generating less wood). A wild forest isn't impassable because of the trees. Alternatively, having more low-trees that block movement naturally would also work.
  20. I think Petra is 'optimised' for the meta of a few alphas back, which would explain the difference.
  21. Definitely out-of-space because of the "continue campaign" button. Not sure what to do here. We could make the notice smaller, I suppose?
  22. Answering as a "team member", I'll say that the notion of "plan" for 0 A.D. is murky at best. We don't really have a well defined end-goal for the gameplay at the moment. The general notion was to have formations be a larger part of combat than in the Age of Empires series, though probably not as involved as Total War. ---- My personal opinion is that they're somewhat unlikely to be more than Age-of-Empires like, that is, a movement/micro helper. The current gameplay doesn't really benefit from formation, nor would they really work compared to not using them.
  23. TBH I think we went a bit too far on A23 with regards to anti-dancing. But I also don't think microing against javelineers or archers is a particularly good gameplay mechanic. That being said, a simpler variant of Hyperion's idea would be randomly changing to target other units close by. That might be enough to make hero-dancing less interesting. ---- On the topic at hand, I don't really mind lowering train rates a bit. My problem with 0 A.D. is mostly that economy grows exponentially, which makes it real tricky after the 15th minute, but well, it's a high skill ceiling. I would also be OK with higher turn rates, since I had originally proposed those anyways. If the player feedback is good, this seems like a go for A25. ---- I'm OK with reducing archer speed compared to jab for balance, but I think at some point we'll need to rethink these entirely. We haven't been able to _really_ balance archer (inf or cav) ever, and we probably need to give most civs a long-range and short-range option (or at least a long-range one). The advantage is just too high. I also really dislike how little damage spearmen deal to spearmen, and how tanky spearmen are in general, but that's another debate. ---- Edit -> Somewhat on topic, but I'm wondering if 0 A.D. standard starts shouldn't have _more_ units/buildings, kind of like the AOE2DE "Empire wars" mode. Since we're fast-paced anyways, maybe we should just cut the crap entirely.
×
×
  • Create New...