|
Written by MOTORMOUTH
|
|
Monday, 09 November 2009 11:35 |
Today's question for staff feedback was posted by fallsjager in The Barracks: "You need to do something about AOs getting pulled CRS! HC puts an AO on brussels, we get inf in place to mole it per request then AO gets pulled 30 minutes later. There needs to be a minimum time for AO's where players are spawned in."
 DOC: We’ve spoken on this issue previously. No one likes having their mission killed because an objective changed even though the nature of changing strategic and tactical conditions means that over time some objectives must change before they reach a resolution. What we’ve said in the past is that we have a desire to make objectives and origins dynamic relative to missions run to or from them. This would function to make it possible for a mission from one origin and sortied against a specific objective to remain active even if the origin of the home brigade or the objective it is sending the mission against were to change while the mission were under way. It requires a fair degree of backend and HOST work as well as the client changes to enable such an evolution, but any perceived lack of progress on this should not be interpreted as “of no interest to us”; It is simply a matter of the limited dev and coder time currently being allocated to more pressing projects. |
For instance, in time zone 3, the number of AOs often fluctuates between 1 AO limit and 2 AO limit repeatedly. Often AOs are forceably removed when good battles are underway.