-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Paths and Bridges Blocked by Friendly Units Should Always Be Visible to Other Friendly Units #78
Comments
I think that it has already been fixed by 7fd857c which uses a simpler way to implement walls and blockers in the interface. I didn't mention it but now the exits appear just like before. |
I tryed the latest master and it does not work properly - not for me at least. |
On closer inspection it seems that only the commands ctrl+tab and ctrl+shift+tab don't work properly. All other commands including tab and shift+tab seem to work just as expected. |
Control + Tab selects only targets useful to a peasant: "woods, gold mines, meadows, and repairable or buildable targets (damaged buildings, building sites, damaged catapults...)". At the moment, it isn't possible to build on a blocked path, so control + tab doesn't select a blocked path. Here are some possibilities:
|
A complicated thing is that a peasant shouldn't be able to build on an exit blocked by enemies, so maybe it's the player's job to unblock an exit before building on it. I will consider that a peasant can be an appropriate blocker, so an exit will always be selected by control + tab (unless there is a building on it, I guess). |
OK, sorry for that. My mistake. Thank you for the explanation. I guess I forgot that part in the manual. |
Oh, I forgot to say. The most important thing is that this was not a bug. |
Just a precision: it is possible to select and block an exit with units even if there is a building on it. I don't know, it could be useful if melee units are ordered to replace an almost destroyed wall. On the other hand, at this point, I don't know if blocking exits with units will prove useful in practice. |
Sorry, another issue related to this showed up. Now if you build a gate on a path and press tab you'll see that the gate got added, but the path is still present eventhough it no longer should be there. Similarly pressing ctrl+tab will will behave like there wouldn't be any gate on that path. Unbelievable. Perhaps it's the latest commit. |
OK, thanks for the explanation. 2016-05-25 19:53 GMT+02:00, soundmud notifications@github.com:
|
Hmm Yes, blocking units is really a useful thing. Especially, for block some paths or scape exit when you are attacking. For example, you attack your enemy, and you don’t want that the peasant of him can escape. Well, put a melee blocking the exit, and the peasant cant flee of the battle zone :3 This behavior is very used in starcraft. Two protoss zealots blocking a path, to difficult the zergling attacks. :3 From: soundmud [mailto:notifications@github.com] Just a precision: it is possible to select and block an exit with units even if there is a building on it. I don't know, it could be useful if melee units are ordered to replace an almost destroyed wall. On the other hand, at this point, I don't know if blocking exits with units will prove useful in practice. — |
I hope this is the last of the path and exit issues.
Let's say you have one peasant and that you want him to block a certain path - for example the path to the west. If you ordered him to block that particular path, he would go and block it nicely. The problem is however, that from the perspective of the user interface, that peasant would behave almost like a wall. The same would be true if you were to select more units at once and order them to block that exit.
If you were to decide later on that you wanted to block that exit with more units, you wouldn't be able to do it because the exit has already been blocked. The problem is that once a path or bridge is blocked by a unit or a group of units, you can't select it anymore and thus can't order any units to block it - not even friendly ones.
So, the point is that you can't send units to block an exit if that exit has already been blocked by other units. Maybe this is somehow similar to the friendly gate issue that has already been fixed.
Buildings behave fine - it's only moving units (such as peasants, knights or archers) that are causing problems.
The text was updated successfully, but these errors were encountered: