Map Merger: различия между версиями

Текущая версия от 03:46, 25 июля 2022

Guide to contributing to the game > Guide to mapping

/tg/station uses a tool called the Map Merger to make map changes easier for maintainers to review and less likely to conflict with map changes made by others.

There are a few ways of running the tool. If you have trouble or need help, ask in #coderbus. You may find a visual guide here.

Summary: for best results, open the tools/hooks/ folder and double-click Install.bat to install the hooks, which will handle things automatically.

TGM format conversion

The "map merge" operation describes the process of converting a map file written by the DreamMaker map editor to:

Use a format more amenable to Git's conflict resolution, called "TGM" and originally developed by Remie. The TGM map format is like the standard Dream Maker map format, but arranged differently, meaning Dream Maker is able to open TGM maps.
Keep the size of the difference between the old version and the new version of the map as small as possible.

This is accomplished by referencing the changed version of the map against the old version stored in the Git history.

Use as a Git hook (recommended)

Install the hook: Open the tools/hooks/ folder and double-click Install.bat
- Linux users: run tools/hooks/install.sh

Once complete, the map merger will run automatically every time you commit in Git. The console log can be reviewed if there are any errors.

Or: Run manually before committing

You can also manually run a .bat file just before each time you commit:

Ensure you have saved all your changes
Open the tools/mapmerge2/ folder and double-click Run Before Committing.bat
Commit

If you forgot to map merge

For first-time contributors who committed map edits without map merging, a script is available to automatically commit a fix to your PR branch:

Ensure you have no unsaved changes
Open the tools/mapmerge2/ folder and double-click I Forgot To Map Merge.bat
Push your branch

Automatic conflict resolver

We also have a rudimentary conflict resolver to cover some cases that the TGM conversion couldn't prevent.

When run, the console output will indicate whether further manual action is needed, including conflicting coordinates.

Use as a Git hook

Install the hook: Open the tools/hooks/ folder and double-click Install.bat
- Linux users: run tools/hooks/install.sh

Once complete, the conflict resolver will run automatically every time you merge in Git.

Or: Resolve conflicts on an in-progress merge

If you are using a Git GUI which does not run the hook on merge, you can also run the conflict resolver on an in-progress merge by request:

Open the tools/mapmerge2/ folder and double-click Resolve Map Conflicts.bat
- Linux users: run tools/hooks/dmm.merge --posthoc

Note that to use this, you must merge your updated local master branch into the branch with conflicts so that your Git GUI reports a conflict on the map file.

Implementation details

Information on the tool's implementation is stored with the code.

Contribution guides
Hosting	Hosting a server • Setting up the database • Working with /tg/station as an upstream repository
Contributing	Guide to contributing to the game • Setting up git • Downloading the source code • Reporting issues • Changelogs
Coding	Understanding SS13 code • SS13 for experienced programmers • Code docs • Coding standards • Getting Your Pull Accepted • Binary flags‎ • Text Formatting • MySQL
Mapping	Guide to mapping • Map merger • Guide to door access
Spriting	Guide to spriting • Resolving icon conflicts
Wiki	Guide to contributing to the wiki • Wikicode • Autowiki

@@ Строка 1: / Строка 1: @@
-Before any change to a map, it is good to use the Map Merger tools. What these do is cut down the number of lines which Dream Maker thinks have changed, since it usually interprets any change to the map as a rewrite of all ~8000 lines.
+: [[Guide to contributing to the game]] > [[Guide to mapping]]
-The Map Merger tools presently only work for windows as they utilize .bat files.
+/tg/station uses a tool called the '''Map Merger''' to make map changes easier for maintainers to review and less likely to conflict with map changes made by others.
-If you have difficulty using these tools, ask for help in [[Community|#coderbus]]
+There are a few ways of running the tool. If you have trouble or need help, ask in [[Community|#coderbus]]. You may find a visual guide [https://hackmd.io/@tgstation/SyVma0dS5#Git-Hooks here].
+'''Summary''': for best results, open the <code>tools/hooks/</code> folder and double-click <code>Install.bat</code> to install the hooks, which will handle things automatically.
+== TGM format conversion ==
+The "map merge" operation describes the process of converting a map file written by the DreamMaker map editor to:
+# Use a format more amenable to Git's conflict resolution, called "TGM" and originally developed by Remie. The TGM map format is like the standard Dream Maker map format, but arranged differently, meaning Dream Maker is able to open TGM maps.
+# Keep the size of the difference between the old version and the new version of the map as small as possible.
+This is accomplished by referencing the changed version of the map against the old version stored in the Git history.
+=== Use as a Git hook (recommended) ===
+# '''Install the hook''': Open the <code>tools/hooks/</code> folder and double-click <code>Install.bat</code>
+#* Linux users: run <code>tools/hooks/install.sh</code>
+Once complete, the map merger will run '''automatically''' every time you commit in Git. The console log can be reviewed if there are any errors.
+=== Or: Run manually before committing ===
+You can also manually run a .bat file just before each time you commit:
+# Ensure you have saved all your changes
+# Open the <code>tools/mapmerge2/</code> folder and double-click <code>Run Before Committing.bat</code>
+# Commit
+=== If you forgot to map merge ===
+For first-time contributors who committed map edits without map merging, a script is available to automatically commit a fix to your PR branch:
+# Ensure you have no unsaved changes
+# Open the <code>tools/mapmerge2/</code> folder and double-click <code>I Forgot To Map Merge.bat</code>
+# Push your branch
+== Automatic conflict resolver ==
+We also have a rudimentary conflict resolver to cover some cases that the TGM conversion couldn't prevent.
+When run, the console output will indicate whether further manual action is needed, including conflicting coordinates.
+=== Use as a Git hook ===
+# '''Install the hook''': Open the <code>tools/hooks/</code> folder and double-click <code>Install.bat</code>
+#* Linux users: run <code>tools/hooks/install.sh</code>
+Once complete, the conflict resolver will run '''automatically''' every time you merge in Git.
+=== Or: Resolve conflicts on an in-progress merge ===
+If you are using a Git GUI which does not run the hook on merge, you can also run the conflict resolver on an in-progress merge by request:
+# Open the <code>tools/mapmerge2/</code> folder and double-click <code>Resolve Map Conflicts.bat</code>
+#* Linux users: run <code>tools/hooks/dmm.merge --posthoc</code>
+Note that to use this, you must merge your updated local master branch into the branch with conflicts so that your Git GUI reports a conflict on the map file.
+== Implementation details ==
+Information on the tool's implementation is stored with [https://github.com/tgstation/tgstation/blob/master/tools/mapmerge2/ the code].
-== Using the tools ==
-{|
-|-
-|'''1. Install Java'''
-|If you don't have Java already installed it can be downloaded from: [http://www.java.com/en/download/index.jsp]
-|-
-|'''2. PATH Java'''
-|To test if Java is in your PATH, open Git Bash and type "Java". If it says "unknown command" you will need to add JAVA/bin to your PATH. See here for how: [https://www.java.com/en/download/help/path.xml]
-|-
-|'''3. Prepare Maps'''
-|Run "Prepare Maps.bat" in the tools/mapmerge/ directory.
-|-
-|'''4. Edit your map'''
-|Make your changes to the map here. Remember to save them!
-|-
-|'''5. Clean map'''
-|Run "Run Map Merge.bat" in the tools/mapmerge/ directory. Don't worry if it says there are ~8000 differences, just ignore that for now.
-|-
-|'''7. Check differences'''
-|Use your application of choice to look at the differences between revisions of your code. If it's reading ~8000 line differences then you've done something wrong, go back and try again.
-|-
-|'''8. Commit'''
-|Your map is now ready to be committed, rejoice and wait for conflicts.
-|}
-[[Category:Guides]] [[Category:Game Resources]]
 {{Contribution guides}}