Opened 21 months ago
Last modified 16 months ago
#6608 new defect
units should not use privileged knowledge of unexplored territory to reach a point
Reported by: | abian | Owned by: | |
---|---|---|---|
Priority: | Should Have | Milestone: | Backlog |
Component: | UI & Simulation | Keywords: | |
Cc: | abian | Patch: |
Description (last modified by )
- Action: I order a unit to go to a point that is not reachable through the known territory.
- Current result: The unit immediately calculates and follows the fastest route to that point based on perfect knowledge of the whole world, including the part unknown to the player.
- Expected result:
- Option A (ideal): The point is considered inaccessible terrain, so the unit goes to the nearest point that is reachable through known territory. This is very common in other games and what already happens when a unit is asked to move into truly inaccessible terrain (e.g. ordering a ground unit to move to the sea or to an inaccessible mountain).
- Option B: The unit does not move. This has the disadvantage that one can tell whether there is a route or not depending on whether the order is aborted or not, but it improves on the current situation where the fastest route is automatically followed.
Attachments (1)
Change History (5)
by , 21 months ago
follow-up: 3 comment:1 by , 21 months ago
Milestone: | Alpha 27 → Backlog |
---|
comment:2 by , 16 months ago
Component: | Core engine → UI & Simulation |
---|---|
Description: | modified (diff) |
comment:3 by , 16 months ago
Replying to Stan‘:
I'm not sure how that can be implemented and whether it's good for performance or not to do that.
How about a workaround for most of the clearly undesirable cases? For example, if the calculated/fastest route is more than 4 times longer than the straight line and more than half of the calculated/fastest route is unexplored terrain, then B (abort the order), else continue as usual.
comment:4 by , 16 months ago
People might be confused by their unita not moving. Btw sorry I think I took your account on Phabricato as spam and deleted it.
Note:
See TracTickets
for help on using tickets.
I'm not sure how that can be implemented and whether it's good for performance or not to do that.