Basically, this is a file created by a modder that is loaded by the mapper, which displays changes to the map, comments, and priority of the change.
For modding, the mod enters a map, and changes things directly on the map. The modder can then save the changes as an "update" file. This update file (.oup or something) will contain the changes and other information for the mapper. When saving the update file, the mod will be given the opportunity to assign priority and add comments to a change in a note or set of notes, as well as general comments and suggestions. This information can also be used to automatically generate the standard "modding" post that mods currently have to manually write.
The mapper would then load the update file, and be automatically brought to each change. He or she can then "allow" or "ignore" a particular change. Comments and priority (Unrankable, strongly suggested, suggested, etc.) will be displayed once the mapper is brought to each change.
This system can be helpful for illustrating for the mapper what exactly is meant by a particular suggestion, eliminate the need for "Move notes to match this screenshot" suggestions, as well as aid in breaking down language barriers. It also streamlines the process of modding, with the mapper not having to switch between two windows while applying mods.
I made a similar suggestion earlier, about in-client modding, though this suggestion is different in that it features minimal changes to the current forum-based system, and would be easier to implement, requiring only the ability to read and write this new type of file, but retains many of the advantages from my earlier suggestion.
For modding, the mod enters a map, and changes things directly on the map. The modder can then save the changes as an "update" file. This update file (.oup or something) will contain the changes and other information for the mapper. When saving the update file, the mod will be given the opportunity to assign priority and add comments to a change in a note or set of notes, as well as general comments and suggestions. This information can also be used to automatically generate the standard "modding" post that mods currently have to manually write.
The mapper would then load the update file, and be automatically brought to each change. He or she can then "allow" or "ignore" a particular change. Comments and priority (Unrankable, strongly suggested, suggested, etc.) will be displayed once the mapper is brought to each change.
This system can be helpful for illustrating for the mapper what exactly is meant by a particular suggestion, eliminate the need for "Move notes to match this screenshot" suggestions, as well as aid in breaking down language barriers. It also streamlines the process of modding, with the mapper not having to switch between two windows while applying mods.
I made a similar suggestion earlier, about in-client modding, though this suggestion is different in that it features minimal changes to the current forum-based system, and would be easier to implement, requiring only the ability to read and write this new type of file, but retains many of the advantages from my earlier suggestion.
Also, once an update has been made, you can always revert back to the latest uploaded version, in case you don't like it. 