WarCraft III: World of WarCraft (Wc3:WoW) is the most accurate WoW replica mod for WarCraft III: The Frozen Throne, featuring many elements as WoW does. It is a Single Player Campaign and the WarCraft III engine does not allow Campaigns to be played online or even on LAN. Wc3:WoW is currently being developed by a group of developers who hope to become pro some day called Condemned Entertainment. Previously, the team was given the simple 'Wc3:WoW Team' title, but after realizing it wasn't a professional team title to stick with, the team name was changed. Right now, the leader of Wc3:WoW is Craka_J, who had led the project through tedious development for over 4 years.

Report article RSS Feed 1.24 Impact

The situation has just gotten a lot worse... or better. You decide.

Posted by Craka_J on Aug 5th, 2009

Blizzard Entertainment recently released a new patch for WarCraft III which mainly focuses on eliminating a function in maps that allowed them to store and release malicious content such as a Trojan Virus on a user's computer. There were several functions added for modders as well, amongst a few other things they included in patch version 1.24 like increasing the maximum map filesize on Battle.Net from 4MB to 8MB. It sounded like a great patch. However, the patch is flawed.

Because of the new patch, Wc3:WoW's GUI triggers were corrupt, bringing up an error message saying one or two triggers were not recognized/did not exist whenever I opened up the World Editor. Then a critical error window pops up and closes the editor.

To explain why this is an issue, the problem was the GUI triggers we used in Wc3:WoW. Apparently Blizzard removed the functions we used from the World Editor and it caused the editor to crash. If the triggers that were corrupt used JASS, no problem. It'd be an easy fix. However, it's GUI that is the problem. The World Editor processes GUI triggering while JASS is processed only as text, not as a sort of function, except when in-game of course. Anyway, the GUI triggers have potentially destroyed all triggering/coding in Wc3:WoW and now we need to recode EVERYTHING.

Luckily there's a good side and bad side to this calamity.
GOOD: Thankfully we were able to save the sounds, models, textures, object data, and the majority of the maps (we lost two pretty insignificant maps, no biggie) so really, all we lost were triggers and some scripted spells. The good side of that is that we planned to recode all the GUI triggers anyway. Too bad we didn't do it earlier though. Wc3:WoW will be coded from now and there will be no GUI triggers whatsoever. Not only because of the problems which are presented to us because of the patch, but also for security reasons and for making the mod perform better. In other words, leakless triggers from this point forth, although BETA Testers will be the only ones to experience memory leaks since the early coding part is usually messy.

BAD: We lost all the triggers and coding, meaning not even the developers can really alpha test Wc3:WoW and the BETA Testers of Wc3:WoW will have to wait even longer... sorry fellas. But it cannot be avoided. The only way around this is if we decided to work on the 1.23 version of Wc3:WoW which works only if you have version 1.23. Why don't we do that? Well, the new features in version 1.24 are really useful and future patches are expected to be even better, so we'd miss out on all of that. Plus, it's really doubtful that people will uninstall WarCraft III, reinstall it, then download patch 1.23 just so they can play Wc3:WoW.
Overall it's bad for everyone because this REALLY delays the release date - not like we even have one yet, but regardless it's being pushed back - even more and no one wants to wait any longer. How much longer? Who knows... depends on our development rate, but it could be another year before we release anything...

So there you have it. The WarCraft III patch version 1.24 nearly killed Wc3:WoW, but we're pushing forward to get it all done. This coding overhaul may take forever, but it's for the greater good and for the sake of this project's staying alive.

Post comment Comments
Nathanius
Nathanius Aug 5 2009, 7:15pm says:

kudos to you guys for doing the difficult, but right thing in this situation!

+2 votes     reply to comment
GunShip05
GunShip05 Aug 5 2009, 10:35pm says:

What's this about maps containing viruses?

+2 votes     reply to comment
xscottx019
xscottx019 Aug 5 2009, 11:19pm says:

Trust me I would un-install and then re-install, then get patch 1.23 just to play :D

+1 vote     reply to comment
Warlock_23
Warlock_23 Aug 6 2009, 1:13am says:

This always happens with any custom map *sigh*

+1 vote     reply to comment
Warlock_23
Warlock_23 Aug 6 2009, 1:14am says:
GunShip05 wrote: What's this about maps containing viruses?

When you download maps from another user on Battle.net the map could contain a script that could activate a trojan virus on your computer

+2 votes     reply to comment
the_refridginator
the_refridginator Aug 6 2009, 1:47am says:

why don't you just reinstall 1.23 and export the triggers you would use to a 1.24 version? that way you won't have to redo all the triggers, just the ones you planned to redo. unless it's too late for that already.

+2 votes     reply to comment
Craka_J Author
Craka_J Aug 6 2009, 11:19am replied:

It's kind of too late for that. We 'could' continue to update the 1.23 version until a stable 1.24 patch is released which won't sabotage our entire campaign, but it's somewhat an issue since we really needed to recode everything anyway for the sake of security, quality, and performance and at this point it just feels hopeless to go back to the 1.23 version which has a little less content on it.

+1 vote   reply to comment
the_refridginator
the_refridginator Aug 6 2009, 4:10pm replied:

well i don't mean update the 1.23 version, just haul everything over to 1.24 that isn't making the new patch crash... and then rework whatever you have to, and save whatever work you don't have to do... you know what i mean?

+1 vote     reply to comment
Craka_J Author
Craka_J Aug 6 2009, 6:06pm replied:

There's a lot we'd have to sort through and delete. Something our JASS Expert doesn't want to waste time doing. Recoding the mod is better anyway. We're using less libraries this time (or at least newer ones) and things will be more organized, clean, and pretty seamless.

+1 vote   reply to comment
Scarwing
Scarwing Aug 14 2009, 11:56pm says:

Ah this has to suck.

+1 vote     reply to comment
OutSpeedify
OutSpeedify Sep 29 2009, 5:04pm says:

GunShip this isnt gonna be virusses this is gonna bea COOOOOOOOL Mod lie my maps

+1 vote     reply to comment
Post a Comment
click to sign in

You are not logged in, your comment will be anonymous unless you join the community today (totally free - or sign in with your social account on the right) which we encourage all contributors to do.

2000 characters limit; HTML formatting and smileys are not supported - text only

Icon
Warcraft III: Frozen Throne Icon
Platform
Windows
Contact
Send Message
Official Page
War3wow.webs.com
Release Date
Released Apr 1, 2011
Mod Watch
Track this mod
News
Browse
News
Report Abuse
Report article
Related Mods
Related Games
Warcraft III: Frozen Throne
Warcraft III: Frozen Throne Single & Multiplayer Real Time Strategy
Related Groups
Condemned Entertainment
Condemned Entertainment Developer & Publisher with 4 members