WarCiTy 0.2.0

[Vexorian]

This is a quick and dirty editor for a map's wct file (The one that holds custom text triggers)

Initial version is able to mldly browse and edit the custom text triggers, note that right now there is no way for the program to tell whether a trigger is disabled o a comment or even what's the trigger name... But it does its job fine.

One good feature is that you can export and import these (the custom text) files as a special type of .j file, you can use this feature to process the custom text triggers all grouped into a single file. BTW, the syntax of the generated file is jass/vJass compatible, unless you had disabled triggers in your map that didn't follow the jass syntax or had redundant functions.

Next versions will also deal with the .wtg file and thus will be able to handle disabled triggers correctly.

Roadmap
** Initial version: can only support wct editing, ignores wtg, this makes it unable to add triggers, or actually know information related to the triggers.

Phase two: Will be able to handle .wtg if and only if there are no GUI triggers or GUI variables in the map, else it will go back to the limited mode we got in the initial version. This will allow you to create new custom text triggers, enable them externally (should be good against crazy WE not letting you enable them). Adding categories, controlling their adition order, etc.

Phase three: will automatically convert GUI triggers into custom text and GUI variables into a vJass compatible globals block. Then allow the stuff described in phase two on other maps, if some action/event/function is unrecognized (the map was done by UMSWE or WEU and you don't have a complete triggerdata.txt) it will still default to limited mode.

changelog:

0.2.0: Fixed a bug when saving maps with no custom script section comment.

[cohadar]

Correct be if I am wrong but would not it be much better for us who can use WE if we simple had global search/replace option in TESH ?

[Vexorian]

Probably, but before that becomes an alternative, it would actually have to be implemented. I think it would be ass hard to implement something like that in TESH since that requires somebody to access WE's own data structure holding the custom text...

Oh, another use, if you export the script then import it back it would automatically fix non-lame(windows) line breaks, I remember that tends to be an issue when apple users try to post their maps.

[emjlr3]

sounds great, interested in trying this when I can

so does this do syntax checks for you? TESH style highlghting, etc., or is simply like taking out the .j, editing it and putting it back in ( which would suck)

[Vexorian]

I don't think it does any of those things.

The main window just shows the triggers as when the old WE times, it is meant as a quick preview. Its main activity is to import/export the warcity script and then I like to use gvim to edit it, I guess somebody else could also use jasscraft on it, btw another possible use would be to generate those files and then have a tool that process them.

To prevent confusion, the .j file is not war3map.j but something it generates from all the custom text triggers, it is a special .j file with some //! tags to distribute the custom text triggers.

This is the first release and can only export the custom text in the 'limited' format, once I add .wtg handling support it will be able to do a lot of crazy things...

--
*new version bump*

[Rising_Dusk]

Can you not add the following two things to this --

• A replace and replace all feature built into the program.
• A list of all custom text triggers that you can view, rather than having to Cntl+N/L through them all to find what you want, just pick which ones to look at and label them by their trigger slot names.

Cool program, otherwise.

[Vexorian]

A list of triggers would just say trigger 1, trigger 2, trigger 3,... Reading the trigger names requires parsing the wtg which requires parsing some stuff that is a little over complicated, I blame GUI. Support for wtg is in the features queue though...

[Rising_Dusk]

Well that's good, it would really improve the usability of the program if those things were added. :)

[Zoxc]

You could just parse the nasty .wtg GUI :]

[Joker]

Darn, you cant see protected maps with this.

[Vexorian]

'protected' maps don't usually even have a wct file, so a wct editor sounds extremely unrelated to them.