Map Merger: Difference between revisions

Latest revision as of 03:19, 29 March 2023

BeeStation 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 the Discord.

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.

Contribution guides
General	Development, Downloading the source code / hosting a server, Guide to git, Game resources category, Guide to changelogs
Database (MySQL)	Setting up the database, MySQL
Coding	Understanding SS13 code, SS13 for experienced programmers, Binary flags‎, Text Formatting, Guide to signals
Mapping	Guide to mapping, Map merger, Exploration Ruins
Spriting	Guide to spriting
Wiki	Guide to contributing to the wiki, Wikicode

@@ Line 1: / Line 1: @@
+BeeStation 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.
-Before any change to a map, it is good to use the Map Merger tools. In a nutshell, it rewrites the map to minimize differences between different versions of the map (DreamMakers map editor rewrites a lot of the tile keys). This makes the git diff between different map changes much smaller. More recently a new way of laying out the map was invented by Remie, called TGM, this helps to further reduce conflicts in the map files.
+There are a few ways of running the tool. If you have trouble or need help, ask in the Discord.
-This is good for a few reasons
+'''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.
-) Maintainers can actually verify the changes you are making are what you say they are by simply viewing the diff (For small changes at least)
+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.
-) The less changes there are in any given map diff, the easier it is for git to merge it without running into unexpected conflicts, which in most cases you have to either manually resolve or require you to remap your changes
-However - to do all this is going to require you to put some elbow grease into understanding the map merger tool.
-If you have difficulty using these tools, ask for help in [[Community|#coderbus]]
-== Using the tools ==
-{|
-|-
-|'''1. Install Python 3.5 or greater'''
-|If you don't have Python already installed it can be downloaded from: [https://www.python.org/downloads/] - make sure you grab the latest python 3, again, it must be 3.5 or greater
-|-
-|'''2. PATH Python'''
-|This step is mostly applicable to windows users, you must make sure you ask the windows installer to add python to your path.
-| [https://file.house/DA6H.png]
-|-
-|'''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 - TGM.bat" in the tools/mapmerge/ directory.
-|-
-|'''7. Check differences'''
-|Use your git application of choice to look at the differences between revisions of your code and commit the result.
-|-
-|'''8. Commit'''
-|Your map is now ready to be committed, rejoice and wait for conflicts.
-|}
-[[Category:Guides]] [[Category:Game Resources]]
 {{Contribution guides}}