-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Add documentation for new coord_point #42303
Conversation
0d35444
to
51235cc
Compare
"ms" and "sm" are dangerously similar. How about "local map" "lm" or "tile map" "tm". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The one change that really needs to be made is fixing the size of a submap.
To help people understand the game's coordinate systems and how to use the new point types, add some documentation Move the description of coordinate systems out of coordinate_conversions.h into a markdown file, and reference that new file from coordinate_conversions.h and coordinates.h.
Definitely don't want to use "local" here; that already means something else. It might make sense to just use "tile" |
51235cc
to
a67e0b3
Compare
Add vehicle coordinate system docs, clarify a bunch of stuff.
a67e0b3
to
f88fe08
Compare
|
||
The game is three-dimensional, with the axes oriented as follows: | ||
* The **x-axis** goes from left to right across the display (in non-isometric | ||
views). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it worth specifying that -X is to the left/west and +X is to the right/east or have we held people's hands here enough?
Summary
SUMMARY: Infrastructure "Add documentation for new coord_point"
Purpose of change
To help people understand the game's coordinate systems and how to use the new point types, add some documentation
Describe the solution
Move the description of coordinate systems out of
coordinate_conversions.h
into a markdown file, expand upon it, and reference that new file fromcoordinate_conversions.h
andcoordinates.h
.Describe alternatives you've considered
Putting it all in
coodinates.h
rather than markdown.Testing
No code changes.
You can read the rendered markdown here.
Additional context
Feedback welcome. It's hard to know what's obvious and what isn't when I'm the one who created all this infrastructure.