Fixup Functionality in DarkRadiant

[greebo]

I guess most of you don't follow the bugtracker activities or SVN commit messages of DarkRadiant too closely, so I thought I'd open a separate thread. With the upcoming DarkRadiant 1.1.0 there is a limited fixup-functionality included, similar to the one offered by the perl script we already have. As opposed to the script, which in principle is processing any text file you throw at it, the DarkRadiant plug-in works on the currently opened map:

 

 

It works like this: in the menu Map there is the item Fixup map..., which asks you for a fixup manifest (our master fixup manifest is located in darkmod\devel\manifests\fixup. txt). DarkRadiant loads this file and replaces all occurrences in the current map, including shaders, models, entity classnames or spawnargs in general. Additionally, the plug-in searches all available entityDefs for editor_replacement spawnargs, and replaces the corresponding entityDefs.

 

 

So, long story short, if we ever declare an entity as deprecated in the future (e.g. in TDM 1.01 or TDM 1.13), we can just provide a fixup.txt for download, and mission authors feed that file into DarkRadiant's plug-in. Many folks don't even know what Perl is in the first place, so this might widen the user target group a bit.

[New Horizon]

Very nice.

[Springheel]

That sounds cool. I imagine mappers could even make their own fixup.txt if they wanted to do some kind of complicated search/replace (say replace a widely used asset with a new, better one)?

[greebo]

Yes, possible. The format is the same as the Perl script is using.

 

The only thing which is not possible for the plug-in is to traverse any .def or .skin files and change content there. DarkRadiant doesn't change any of those files by design, this will remain the responsibility of the external script.

[Crispy]

That's very cool. Nice work greebo.

[jdude]

Very useful!