Loading...
  OR  Zero-K Name:    Password:   

Why did mobile artil get set to hold pos?

3 posts, 327 views
Post comment
Filter:    Player:  
sort

2 years ago
Just curious.

I reverted most of it in config, but I don't get why I would want artil to not be moving back by default when enemy forces are creeping on.

Which specific interaction prompted this change? Was someone messing around with raiders moving back and forth to continuously make artil reposition?

If I have artil I am usually attacking something specific so it would ignore that kind of play, or I'm attack moving it so I specifically want them to move back and forth.
+1 / -1


2 years ago
To me this question assumes more intention than exists. There isn't a document somewhere that spells out why all the defaults exist. They're the way they are because that is the way they were left the last time someone looked at them. If there was an inciting event behind any of the changes, then it has been forgotten. That is assuming there even was a change, and not just a value inherited from BA 15 years ago.

The main principal behind this sort of thing is that units shouldn't look broken at Level 0 ( https://zero-k.info/Forum/Post/226780#226780 ). This includes units seemingly not doing what they are told, and doing 'unreasonable' things on their own. This is augmented by observing what people struggle with, especially new players. I can't just use my own judgement because I prefer to have everything set to hold position by default.

It's particularly hard to give an answer because the question seems to be wrong. I just tried it, and the only artillery that defaults to hold position, and that can fire while moving, is Merlin, Envoy and Lance. Here are some ad hoc reasons that this makes sense compared to, say, Sling:
  • As a strider, we expect people to have few Merlins and to pay more attention to them. It is also quite reasonable to want a Merlin to fire from less than maximum range, to counteract its spread.
  • Lance is prone to missing and teamkill if it fires while moving, it also takes a long time to turn around.
  • Envoy makes the least sense, it was probably just forgotten when whatever change went through.

Git log would know.
+2 / -0

2 years ago
I reinstalled the client a week or so ago. It's possible things didn't change and I simply forgot that I had previously set the default behaviors on my previous install.

Either way no big. It's easy to change the defaults.
+0 / -1