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

Update outdated/unclear parts of the mapping guide #358

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

dylanstrategie
Copy link

After many headaches trying to follow the mapping guide as written and not understanding why it's not working properly, I am humbly offering these updates to make it easier for people like me who are just starting on SS14 mapping to understand what's going on:

  • Map ID needs to be relatively high to avoid colliding with existing IDs. I've heard that most people just straight up use 1000, so updating all the IDs to that to establish best practices (+ explainer as to why)
  • loadmapacts is deprecated, it is now mappingclientsidesetup
  • Trying to be a bit more clear how to force your map and start it both on Tools and Release build
  • Adding the power command to the quick setup, since it's extremely useful in most cases
  • Explain that saved maps go into the Content.Server folder more clearly, and you have to manually move them to Resources/Maps later.
  • Explain that the Content.Server saved map has to be manually deleted later on, or it will persist.
  • Very slightly improve the explanation of the map image tool to make it clear where you need to run it, especially if you don't use VS.
  • Update the pipe color hex codes to the ones actually used on the live version. Those "muted" pipe colors have not been used for a long time and it's impossible to find the hex codes otherwise.

Copy link
Contributor

@Partmedia Partmedia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your documentation update. A few minor nitpicks.

src/en/space-station-14/mapping/guides/general-guide.md Outdated Show resolved Hide resolved
src/en/space-station-14/mapping/guides/general-guide.md Outdated Show resolved Hide resolved
Comment on lines -193 to +199
- Waste loop: #990000 (dull red)
- Distro loop: #0055cc (subdued blue)
- Air: #03fcd3 (cyan)
- Mix: #947507 (brownish)
- Waste loop: #FF1212FF (red)
- Distro loop: #0335FCFF (blue)
- Air: #03FCD3FF (cyan)
- Mix: #947507FF (brownish)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like that we're changing the standards because mappers can't read the standards, but fine.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've checked multiple maps and everyone is using raw colors instead of the custom distro/waste colors

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's not what I said, but it's fine.


3. Make changes
3. Make all your changes.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I always recommend implied second person as adding "you" and its contractions does not add clarity. In this particular case "changes" does not add any new context by having the reader own them. If you feel this needs more clarity, then I would recommend specifying "mapping changes," but that can also be implied by the context.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some of this file uses explicit "you", some of it does not. As far as I am aware docs does not have a standard. I would recommend picking one. That is either use "you", its contractions, and possessive indicators everywhere or nowhere. IMO, "you" never adds context that cannot be had when it is omitted, so there is no reason to add it.


4. If needed, run `fixgridatmos GID`
4. If you have created new rooms, run `fixgridatmos GID` before saving.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

step 4 occurs before 5. "before saving" is implied, so only add this if it causes project loss if forgotten.

Same feedback for "you".


## Common Tools and Commands
* <kbd>SHIFT-Click</kbd>: place a **line** of tiles/item/anything with a snap grid
* <kbd>CTRL-Click</kbd>: place a **square** of tiles/item/anything with a snap grid
* By default, the `P` ("Pick") key will select the entity or tile currently under your mouse for placement.
* By default, the `P` ("Pick") key will select the entity or tile currently highlighted under your mouse for placement.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

last writer but, mouse -> cursor.

2nt person


After this, run the command `dotnet run --project Content.MapRenderer {your_map_id_here}`, with the game map prototype ID. You can also set command line arguments through your IDE and run it that way. The image should be inside Resources/MapImages once completed.
After this, run the command `dotnet run --project Content.MapRenderer {your_map_id_here}` in your IDE or Git CLI, with the game map prototype ID (case-sensitive). You can also set command line arguments through your IDE and run it that way. The image should be inside Resources/MapImages once completed.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If users do not know where to run a command, then it is also likely that their environments are not setup correctly. If including where, then include how or more specifically a link to how.

2nt person


4. If you have created new rooms, run `fixgridatmos GID` before saving.
4. If new rooms were created, run `fixgridatmos GID`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The passive voice was used. The passive voice is a bit weaker and less clear than the active voice. It was also good to clarify that this should be run before saving.

@dylanstrategie
Copy link
Author

Aaaa, should I use active voice or passive voice then ? I can't do both and most of the guide that I haven't touched alternates between both

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

Successfully merging this pull request may close these issues.

3 participants