Reset Editor Registry

[Daffa]

I doubt this is of much use, but I hope it can be useful for some, as I use this personally to assist me in switching versions (so I can start campaign making again).

 

[deepstrasz]

Who made this?

 

[Daffa]

Wrote this myself, should I use some sort of signature in the bat file or something?

Technically, one with knowledge of BAT and Regedit can recreate this themselves.

 

[FeelsGoodMan]

This is quite easily doable without the use of a bat file, and doesn't take a long time to do. Maybe you can improve it a bit by for example creating new Warcraft III entries with Dword 32 value "Allow Local Files" set to 1 so people don't have to restart their Warcraft 1.31 (or lower) every time they want to switch between editors.

EDIT: I'm also pretty sure you will have to delete "HKEY_CURRENT_USER\SOFTWARE\Blizzard Entertainment\Warcraft III" when you switch between editors, I see that you don't do that with this bat file.

 

[Daffa]

This is quite easily doable without the use of a bat file, and doesn't take a long time to do. Maybe you can improve it a bit by for example creating new Warcraft III entries with Dword 32 value "Allow Local Files" set to 1 so people don't have to restart their Warcraft 1.31 (or lower) every time they want to switch between editors.

EDIT: I'm also pretty sure you will have to delete "HKEY_CURRENT_USER\SOFTWARE\Blizzard Entertainment\Warcraft III" when you switch between editors, I see that you don't do that with this bat file.

Well yes, I mean if people know regedit, this is a cake
I'm just lazy, that's all

Forgot about that local files stuff. I'm adding that along with automatically setting the Has Been Run to 1 for a faster first run after BAT is used.

As for the Warcraft III HKCU, it doesn't need to be removed when changing editor versions. So far, from my tests, I have yet to need to deal with that (I always just go delete World Editor keys and that's it). I even test the "test map" button which corresponds to WCIII the most and it seems to function properly, at least from my tests.

Now, give me time to update this ...

EDIT: DONE!

 

[Daffa]

V1.1:

• The following keys have been added automatically for comfort: "Has Been Run" (skips the first load), "Allow Local Files" (enables the local files feature), and "Minimap" keys (there are three of them).
• The key addition from the previous point can be canceled by closing the program when the program asks if you want to add those keys.
• Added a text to show that I truly am the one who wrote this short BAT script sigh guess this do?

 

[FeelsGoodMan]

As for the Warcraft III HKCU, it doesn't need to be removed when changing editor versions. So far, from my tests, I have yet to need to deal with that (I always just go delete World Editor keys and that's it). I even test the "test map" button which corresponds to WCIII the most and it seems to function properly, at least from my tests.

Hmm just tested and apparently this is unnecessary yeah. I change back and forth quite frequently but have never bothered to test if only deleting the world editor entry works lol.

 

[Daffa]

Hmm just tested and apparently this is unnecessary yeah. I change back and forth quite frequently but have never bothered to test if only deleting the world editor entry works lol.

Still, it encourages me to check the other way around. So yeah, I'm glad you raised such points ^^

 

[FeelsGoodMan]

Still, it encourages me to check the other way around. So yeah, I'm glad you raised such points ^^

Actually since it's not necessary to delete the Warcraft III entry then I guess allow local files 1 is also unnecessary since it never gets deleted.

 

[Daffa]

Actually since it's not necessary to delete the Warcraft III entry then I guess allow local files 1 is also unnecessary since it never gets deleted.

Wait, wouldn't Allow Local Files be in World Editor keys not Warcraft III keys? Or did I misremember again? :O

 

[FeelsGoodMan]

Wait, wouldn't Allow Local Files be in World Editor keys not Warcraft III keys? Or did I misremember again? :O

I have mine in the Warcraft III entry and it works fine with the editor too.

 

[Daffa]

I have mine in the Warcraft III entry and it works fine with the editor too.

Well, I guess that settles it then
Too lazy to change that, whatever

 

[Ravager16829]

Technically, for me, the World Editor 1.29 is still functionable despite I have two copies of W3 (1.29 and 1.31).
I really need this tool for using 1.31's World Editor, but I'm still doubt that 1.29's WE is broken upon switching back and forth (Couldn't load War3.mpq).

 

[Daffa]

Technically, for me, the World Editor 1.29 is still functionable despite I have two copies of W3 (1.29 and 1.31).
I really need this tool for using 1.31's World Editor, but I'm still doubt that 1.29's WE is broken upon switching back and forth (Couldn't load War3.mpq).

As far as testing goes, no test has caused any corruption with the war3.mpq, but I might be wrong.

 

[Xetanth87]

Very useful! But does it keep Trigger Display Colors and other preferences?

 

[Daffa]

All keys below WorldEdit is eradicated. What do those contain though?

I'm not sure if I can retain all these reference data, unless I can find a way to duplicate the subkeys and delivers it around as needed till it returns. Even then, I have to identify 1.31 and 1.32 exclusive entries.

 

[Xetanth87]

In WorldEdit there is a 'Trigger Display Colors' subfolder. If you remove every entry from WorldEdit but leave this folder intact then you only need to change your preferences which is ok since there are like 5 checkboxes you need to tick. Trigger Display Colors keeps the information about what color should be attributed to each type of trigger (Unit, Game, Player, Animation etc.) and removing it means needing to change every single color again.

 

[Daffa]

In WorldEdit there is a 'Trigger Display Colors' subfolder. If you remove every entry from WorldEdit but leave this folder intact then you only need to change your preferences which is ok since there are like 5 checkboxes you need to tick. Trigger Display Colors keeps the information about what color should be attributed to each type of trigger (Unit, Game, Player, Animation etc.) and removing it means needing to change every single color again.

I will try to add support for preserving this additional information.

 

[BogdanW3]

The only key that actually prevents pre-1.32 World editors from starting is "Tool Windows". Zero other keys have to be changed for that.
For the game itself the situation is a bit different: The user data directory has to follow an outdated format only in 1.28 and only in 1.26 would you need to reset some graphics adapter settings.

Allowing local files is a nice addition though.
If "reg" doesn't have a simple way to only delete one key, I'd instead recommend replacing this script with a reg file with this content:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Blizzard Entertainment\Warcraft III]
"Allow Local Files"=dword:00000001

[HKEY_CURRENT_USER\Software\Blizzard Entertainment\WorldEdit]
"Tool Windows"=-

 

[Daffa]

The only key that actually prevents pre-1.32 World editors from starting is "Tool Windows". Zero other keys have to be changed for that.
For the game itself the situation is a bit different: The user data directory has to follow an outdated format only in 1.28 and only in 1.26 would you need to reset some graphics adapter settings.

Allowing local files is a nice addition though.
If "reg" doesn't have a simple way to only delete one key, I'd instead recommend replacing this script with a reg file with this content:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Blizzard Entertainment\Warcraft III]
"Allow Local Files"=dword:00000001

[HKEY_CURRENT_USER\Software\Blizzard Entertainment\WorldEdit]
"Tool Windows"=-

I think REG can delete subkeys as needed. I will make adjustments to this new information. As for pre-1.31 cannot be opened after using 1.31, what's up with that?

 

[BogdanW3]

I've never had pre-1.31 fail to open before while 1.31 could, so it could be one of the setings I've not messed with enough to cause incompatibility, if anyone encountering that issue could export their WorldEdit folder as a .reg that might be useful to narrow down to a single or a couple of keys

 

[Daffa]

Very well. I will use this information to create a more reliable bat file then.

 

[eejin]

Simple, but useful to point people to when they want to use the older editor. One remark is that the download is double zipped so you have to unpack twice. Would be nice if that was fixed.

 

[Daffa]

Simple, but useful to point people to when they want to use the older editor. One remark is that the download is double zipped so you have to unpack twice. Would be nice if that was fixed.

Hive does not allow .bat files, so I think that's something beyond my ability.

 

[Luashine]

Are there more keys than "Tool Windows" that lead to a crash? Here's my solution, I didn't know about yours: [Solved] - world editor broken??

 

[BogdanW3]

Are there more keys than "Tool Windows" that lead to a crash? Here's my solution, I didn't know about yours: [Solved] - world editor broken??

Only "Tool Windows" crashes the WE, and I made a .reg file to make that even more painless, posted in this thread above.

 

[YubelHaouJudai]

Thanks to you, i was able to use my World Editor again. Thank you very much!

 

[JCarrill0]

Thank you for such a useful tool. For someone (like me) who uses 1.27b patch a lot for playing game in the oldschool days.

 

[warpten090]

Still workable. Good program

 

[Daffa]

Thanks

Still workable. Good program