Jump to content

wowgetoffyourcellphone

0 A.D. Art Team
  • Posts

    10.847
  • Joined

  • Last visited

  • Days Won

    532

Everything posted by wowgetoffyourcellphone

  1. In a 4-phase game (like my mod), I'd agree. However, the base game of 0 A.D. focuses on creating action as soon as possible. Scout Ships are super weak (or can be made to be more so).
  2. I'll mention that in my first draft the techs were a lot more impactful. ;*
  3. I would very much like to reduce warship size by 25%, which I believe would reduce collisions and weird overlapping noticeably (but of course not eliminate it, that requires more pathfinding work).
  4. I'd say almost 100% of games of 0 A.D.'s type have no garrison effects for ships. Because it's not a "crew." The ship already comes with a crew. The garrisoned are passengers, not rowers. This is possibly a concern, but we were proactive in mitigating this with the tech tree. See: Flaming Projectiles for those civs without Fire Ships or Siege Ships. There was some thought put into this, despite the implications in this thread. It's also funny that you say melee ships are OP when another much better player is saying arrow ships are OP. I'd be down for moving Siege Ships to Town Phase. So, my generic proposal would be: Phase 1 Fishing Boat Purse Seine Salt Curing Merchant Ship Scout Ship Lookouts Shipwrights Phase 2 Arrow Ship Melee Ship Siege Ship Phase 3 Arrow Ship Tech Melee Ship Tech Siege Ship Tech
  5. Tangentially related: https://gitea.wildfiregames.com/0ad/0ad/issues/7666
  6. Well, let's try the former before the latter. Yeah, we can rebalance this with health/armor/bonuses. I agree. I'd like to redo the tech tree. Also, there's a problem with presentation of the techs where in other games the tech that affects a specific unit is placed right below that unit. In 0 A.D. this is not possible. Please, someone code this. Asked for it for 10 years. Huh? What's this? AFAIK, every civ that had a siege ship before still has a siege ship. Possibly. My original design for this had Scout Ships available in P1. I forget why that was changed. But Scout Ships aren't supposed to be effective against other warships, at least. It's a scout ship. But perhaps it should have an attack bonus vs. civvie ships.
  7. Ima be honest whichall. Old system ain't coming back, lol. So, focus on making the new system better. Thanks @chrstgtr for his analysis and suggestions (I have quibbles, but w/e). Any new overhauled system is gonna be trash in the first iteration (see: capture/attack balance). This alpha changed a lot of things. Keep playing and give suggestions to improve the changes besides "changing it back." There are many valid reasons for the new changes that aren't invalidated by an awkward 1.0
  8. Well, at some point you have to actually design the game. Not everything can be an option.
  9. Ah, I assumed that's what you wanted for default. My bad.
  10. What would you do to achieve the current shift-click behavior? just deprecate it? No es bueno, senor.
  11. Checkboxes next to the objectives of the scenario, etc.
  12. It could very easily have been a more accurate simple design and done the same thing visually.
  13. The entire point is to blunt the capture->delete meta. Gaining the benefit of that building isn't a reason to capture it? The only reason in your mind to capture a building is to delete it? Do you not see the problem here? There are several techs in the base game that I find uninteresting or of only minor use, but I think building strength and capture strength are useful/interesting, especially if the capture->delete meta is changed.
  14. In my opinion, packing effects into the Phase up techs is super uninteresting. It's not like 0 A.D.'s tech tree is massive.
  15. https://gitea.wildfiregames.com/0ad/0ad/issues/7599#issuecomment-112460 Design discussion branched from here^ Some of my thoughts on the subject: Things I think will help overall: #7608 looks interesting. I'm thinking there could be another status bar below the capture bar for "Assimilation." There could be a "warm up" time called Assimilation where it takes a certain number of minutes for the usage of that captured building to become available. You've captured it, it's been denied to the enemy, and you've claimed its territory, but now you gotta wait a little while before you can actually use it. And similar to #7608, you can't delete it either unless you've Assimilated it. All of this wouldn't require any input from the player, so it's decently simple. As suggested by @real_tabasco_sauce Adding some toggle or option to choose default behavior for your units: Capture or Attack. If it's an in-game toggle, we could call it a "Policy," or else it can just be an Options menu item. I think in-game toggle is sexier, but Options menu item might be simpler (?). If an in-game toggle, you wouldn't have to swap in and out of the Options menu if you wanted to change the policy mid-game. I think (un-garrisoned) buildings should take longer to capture in general, and buildings easier to destroy with melee weapons. Maybe revisit the base capture points of different building types and the health/HP or armor values of various buildings. Just rebalance capturing vs. attacking. I don't think a fully-garrisoned building should be impossible to capture. We could revisit the GarrisonRegenRate values to prevent this. Higher base capture points, but lower GarrisonRegenRates seem desirable to me. My ideal game is still Attack by default, but if some solutions were implemented to make capturing better and attacking more viable, then I could live with Capture by default, especially if there was a toggle. If we make buildings more vulnerable to non-siege units, then we can compensate with a building health tech tree at the Civic Center: Craftsmen (common) -> Architects (common) -> Monumental Architecture (for "urban" civs). And if we make buildings less vulnerable to capturing (increased base capture points), we can add a couple capture techs to compensate: Military Cult (common; at the Temple) -> Plunderers (for "barbarian" civs; at the Temple), Siege Ladders (common; at the Fortress).
  16. That's true, but we already don't call them just "Indians" or "Chinese." We differentiate them already. Yes, later we could add the Guptas and Tang.
  17. I think this is too much info in the middle of the match when we can use that space for something else.
  18. How is anyone to know that no one is hiding it? lol If you are so ethical, why don't you support features that allow everyone to know what mods you are using? lol
  19. Wait a minute! Where is the one-boob armor in female form? I feel cheated.
  20. If someone were to make some mods isolating some of the features (and people can enable whichever features they'd like to see via mods), that would be super cool. Doing so might also create a basis for some pull requests down the line.
  21. It would be interesting if we could have a discussion about the linothorax. I'm of the view that it was white-washed leather rather than linen, where the quilted linen corselet came later. The term "linothorax" is so cool though that I'd still want to use it.
  22. The first shield pattern with the lame stripe really bothers me for some reason. There's zero creativity and it's strange.
×
×
  • Create New...