Jump to content

bb_

WFG Programming Team
  • Posts

    262
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by bb_

  1. When you are using AI's it is quite easy to achieve this: AI do not print (at least currently) anything in the command.txt except on the first line (that line gives match settings, further the replay is empty). So all you have to do is create some of those "first lines" (I guess you want to test the AI on a couple of times on the same map, for that you just need to change the seeds, such that every game is different) and put as many empty turns as you like afterwards, which will give you the wanted replays. (In principle you don't even need to have run to game to already have the "replay" ;))

  2. The footprint height value is passed by the getShape function in the footprint component. In the engine it is used in the VisualActor to set the height parameter of a CustomSelectionShape. This the fills some object retrievable by getSelectionBox and that is used in a couple of components. (f.e.in cmpPosition for the height offset of constructions)

  3. Never really experienced any OP-ness, maybe cuz I usually play ptol on naval maps :scratch_one-s_head:. Anyhow a suggestion: One could consider that building the lighthouse reveals the shore but retains the FoW and add a "tech" in the lighthouse to reveal all shores again for a little cost (similar to the bribing feature we have).

    • Like 1
  4. A patrol distance threshold would be  a fix for the auto dance indeed, but that doesn't solve the handdance. Te hard thing for a spam block script, is defining "spam", eg. if one want a unit to walk along a circle between two points, I wouldn't consider that spam, but a spam script probably will mark it as such. Maybe a solution would be a "minimal time for walk", so that units will walk very slowly on short orders, thus giving the arrows enough time to hit. One gotta think about the implications of that though...

     

    • Like 1
  5. The promotion issue could somewhat easily be solved by not allowing units to attack invincible units (that would also solve the catafalc arrow absorber). The dancing problem is much more complicated, since "homing missiles" or "splash" aren't ideal solutions either. I once tried implementing "turning times" for units, but that resulted in total chaos when moving large groups of units.

    • Like 3
  6. Implementing that isn't too hard once we can nuke the unitmotion component from unpacked siege (which requires the unitmotion rewrite and some refactoring), but one also needs to think of the gamplay aspect, as not rotating means it can only fire in 1 direction, so siege would become much weaker, I suppose.

    • Like 1
  7. @stanislas69 Doesn't seem that hard too implement in a meh way. Ideally however we should adapt the aura code so we can have these types of bonussus (as in currently we can add and multiply, but probably we want x speed for 1 unit, 1.5x for 2 etc.) Then in the same go garrisonned arrows could be implemented like that and we would be much closer to #4000. Also the unitAI needs to take care of units with unitMotion but without speed (see how unpacked sieges templates are hacked currently).

  8. They already do as said, but you have to use a specific formation explicitly, not the default "None" formation, with that every unit moves at his own speed. You can set formation by clicking the icons between the minimap and the selection info (so sorta bottom left-middle).

    • Like 1
×
×
  • Create New...