-
-
Notifications
You must be signed in to change notification settings - Fork 988
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
Planning mode sprite missing #2124
Comments
I vaguely recall this used to be the case (I only ever used planning mode in testing). If it's a deliberate design decision to remove it, I think this is fair too. But it may well be unintentional. |
@gfgtdf The future sprite is in full colour rather than being greyed out as it used to be. Otherwise, at least there's a unit there now. |
did you test that 1.12 has it greyed out? |
I don't have working 1.12 or 1.13 builds any more, but I do know that it was previously grey when I worked with planning mode in the past. |
Needs either an image mod suffix or to use one of the internal whiteboard animations. |
hmm my memory tell me the opposite unless you tested it i will assume 1.12 behaved just like 1.14.1 in that regard. |
It would be extremely weird in my view if the planning mode sprite were indistinguishable from a regular sprite. |
well you still have the red arrow pointing to that unit with the 'ghosted' unit in the orgin place, so it's not that hard to distinguish them. |
Is 'ghosted' supposed to mean translucent? It looks like normal unit transparency to me. Anyway, I suppose you were right after all - it's the planned origin that's greyed out, not the the planned destination. http://www.tuxarena.com/wp-content/uploads/2012/02/planning_mode.png |
fixes wesnoth#2124 (cherry-picked from commit 9277a6c)
When planning a move using planning mode, there is supposed to be a grey sprite left at the destination indicating where you planned to move a unit, but nothing shows up.
Noticed this on a previous 1.13 version though it still happens in 1.13.10. Works in 1.12. OS: windows 10
The text was updated successfully, but these errors were encountered: