Skip to content
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

request: flag to disable slope transition between hexes for creating "stairs" #53

Open
GoogleCodeExporter opened this issue Jul 19, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Currently, elevation differences of 11 or more are needed to form cliffs
between adjacent hexes. This means it's impossible to form a decent-looking
staircase that leads up along a wall or cliff, as for the most part this
staircase will warp into a long slope.

A terrain flag (call it "auto-cliff"?) to enable cliff-formation between a
hex and it's neighbors at any elevation would allow map designers to create
well-formed stairs. This would just affect the graphical representation,
the movement would still be handled normally (and be possible based on
height difference - a neighbor more than 10 elevation units apart would
form a "natural" cliff and that should remain unclimbable).

Original issue reported on code.google.com by [email protected] on 25 Oct 2007 at 7:34

@GoogleCodeExporter
Copy link
Author

Some more thoughts:

Instead of a boolean flag this could be an integer value of elevation 
difference at
which to create a cliff. This could be a terrain configuration property, so the
editor doesn't have to deal with it in its UI.

Suggestion: "maximum_slope" (default 10)
At an elevation difference of maximum_slope or less, the graphical 
representation
would be just like it is now (slope to the neighboring hex). Above that it 
would form
cliffs.
For the wall terrain, the maximum_slope could be set to 3 or 2 (need some
experimentation in the editor). I expect that it is desirable for all walls to 
form
relatively borders with their neighboring hexes - not only for forming stairs.

A per-terrain default would be more KISS than a per-hex situational flag.

Original comment by [email protected] on 26 Oct 2007 at 10:19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant