## About The Pull Request
The recent overhaul of UpdatePath's documentation contains a
discrepancy. Currently, it mentions that the line
`/mob/living/basic/mouse{name="Tom"} : /mob/living/basic/mouse/tom{name
= @SKIP, @OLD}` will keep all the old variables except for 'name'. This
format is slightly incorrect, and will actually cause the UpdatePaths
script to error and not complete its task at all.
By cross-referencing some pre-existing scripts in the folder, as well as
actual testing, the correct way to write this would be the following:
`/mob/living/basic/mouse{name="Tom"} :
/mob/living/basic/mouse/tom{@OLD;name=@SKIP}`
Note the use of a semi-colon instead of the comma, the removal of
spaces, and the use of `@OLD` _before_ `@SKIP`. **Each of these cases
are important and affect the outcome/success of the script!**
* UpdatePaths Readme - Reforged
I'm a bit tired after typing for the last hour so apologies if some of this stuff is unreadable. Basically, I just took time to add a small blurb about UpdatePaths in MAPS_AND_AWAY_MISSIONS.md, as well as write out examples on how you can properly use every single function UpdatePaths might have. I'm probably missing something? I think I got everything though. Let me know if I should be consistent somehow, but I did deliberately choose different test-cases per example because it's nearly impossible to come up one "generic" fit-all situation that illustrates every possible use of UpdatePaths (to my small mind).
Anyways, hope this helps.
* i fucked up with the TGM format
augh
Updates the UpdatePaths Readme to have more information
Hey there,
Several people were relying on this to teach them about UpdatePaths, and it missed out on a bunch of needed information (such as the important of including `@OLD` in order to ensure that you do not discard old variables (properties)) when you transfer from an old path to a new path. I added that in, as well as leveraged the capabilities of it being a MD file to get some nicer looking formatting in as well.
Puts the scripts for Update Paths in a "scripts" subfolder, labels them all according to their associated PR for easy sequential updating on paths, and provides a readme for how to use the tool and how to make the scripts for it.
I don't know what the label would be for this.
* Organizes the Update Paths tools folder and provides a readme
* Clarified adding more than one path update in the readme
* swaps the rtf with a markdown file
* renames the most recent updatepaths and throws it into the folder
