Warcraft III: Reforged Patch Notes - Version 2.0.3

So, I think they added some extra stuff in the hotfix that they added (at least it seems like they added a hotfix, I had another update a few days after my original comment). Mainly because the lag that I was experiencing before is gone, and the game overall runs smoother.
 
So many great fixes in here. I've found some random portraits still not showing their correct custom portrait, but the vast majority seem to be working now. Also, being able to use MDX files for custom campaign backgrounds is great. Thanks for giving us the choice to use the new webm file and the older mdx file backgrounds.
 
I am seeing a lot of failing to parse the war3map.w3i file. I wonder if this patch did something.

yep! they did update the w3i format in this patch to support a few new options in the editor:

1753518536137.png


shout-out to @Luashine for documenting the changes here:

the breaking part is probably the three int32 (for those zoom values in the screenshot) inserted between the int32 GameDataVersion and int32 NumberOfPlayers. otherwise, they just bumped the format version to 33 and added some map flags for those check-boxes.

they also updated the format for the war3campaign.w3f (which is like the w3i but for campaigns)--they added an int32 after the cursor int for the new option to choose which background version you want (0 => Default, 1 => Classic, 2 => Reforged). otherwise, they bumped the format version to 2 and added webm support, but they just re-used the "string: path of custom background screen" for that so it shouldn't be a breaking change.
1753520691911.png
 
  • Fixed an issue where music would overlap with music from a saved game


    It only took them 5+ years or something
Holy molly!

I have my own jukebox system in my maps, and you are telling me that for many years I kept blaming myself for that bug, and all this time it was Blizzard's fault?

I was innocent! I was innocent all along!!!! :goblin_cry::goblin_cry::goblin_cry:
 
I'm glad a lot of people are getting a lot out of this patch. But from what I've seen of it, I'm still not convinced. I haven't touched Reforged in five years now and there's nothing that convinces here that really draws me back.

But admittedly, I'm hard to please. Anything less than a classic/legacy client that preserves the preforged gamestate as much as possible will leave me unsatisfied. Something like what Community Edition already does but with official support.
 
Last edited:

Warcraft III: Reforged Patch Notes - Version 2.0.3

Blizzard said:
Warcraft III: Reforged Patch Notes
Version 2.0.3
July 17, 2025

Game Servers

  • Custom Game lobby advertisements now properly timeout 15 minutes after the most recent player has joined or left
    • This timer resets every time a player joins or leaves
  • Fixed an issue where some players with classic keys were having licensing problems
  • Fixed an issue where custom game invites were not working properly

General

  • Added a countdown timer to the UI for construction and training
  • Ctrl + C now camera tracks a selected unit instead of just snapping to location
  • Fixed an issue where some triggers would sometimes not be saved correctly
    • Existing saved games may still have this issue, but any new ones should now be saved correctly
  • Fixed an issue where going into a single player custom game would sometimes put you into a multiplayer lobby

Performance

  • Optimized AI functions for finding build locations
    • This should optimize how AI players look for places to build structures, resulting in better performance in games with a high number of AI players
    • Please watch for and report unexpected behavior changes
  • Optimized heavy particle counts of some Reforged VFX
  • Improved performance for rendering terrain

Visuals

  • Updated Reforged shaders. Players should see improved intensity of shadows and lighting
  • Based on feedback, we’ve lowered the brightness of units and portraits in Classic HD graphics
  • Replaced the classic main menu and campaign .webm backgrounds with .mdl renders
  • Environment Classic HD/Reforged toggles no longer control gold mines and fountains. The Buildings toggle now controls these
  • Fixed certain VFX appearing as white squares in Classic HD mode
  • Tree idle animation now enabled in Reforged environment
  • Added options for ambient occlusion and bloom in the options menu
    • Note that these settings will lower performance when enabled in 4K resolution
  • Fixed an issue where units with transparency were less transparent than intended when on water
  • Fixed an issue where custom unit portraits were incorrectly inheriting a portrait from their base units
  • Fixed an issue where icons for custom skins would sometimes show their base icons
  • Fixed an issue where units would sometimes be invisible after loading a saved game
    • Existing saved games may still have this issue, but any new ones should now be saved correctly
  • Fixed a few model files which were not correctly being included with the game

Audio

  • Fixed an issue where map music would sometimes continue playing at the end of a map, or during a cinematic
  • Fixed an issue where music would overlap with music from a saved game

World Editor

  • Custom campaigns may now use MDL files for mission select backgrounds
  • Increased doodad limit from 30000 to 130000. Use with caution!
  • Increased the draw distance in the World Editor
  • Fixed an issue with weather effect [RAhr] triggering permanent rain
  • Fixed an issue with the model viewer window being incorrectly scaled
  • Fixed an issue with the Summoned Units window being incorrectly scaled
  • Fixed an issue with Variables window column width not saving after closing the window
  • Fixed an issue where [AIsb] was not respecting the cooldown of its attached ability when used on an item
  • Fixed an issue where [AIf2] had hidden bonus damage and attack index data fields
  • Fixed an issue where Barrage upgrade was overwriting the projectile art of the primary attack
  • Fixed an issue where a unit that had a health upgrade and spellbook ability would die upon creation
  • Fixed the following natives:
    • The following changes affect many natives and fields, and are an attempt to fix some broader systems instead of individual bugs. Please report any bugs (or new fixes!) related to these changes:
      • Fixed dozens of broken BlzSetAbility____Field natives
      • BlzSetAbility____LevelField natives now attempt to forcibly refresh the ability’s data so changes are reflected. For example, orb of fire (AIf2) now has its damage bonus properly updated due to this change
    • BlzSetUnitIntegerField now supports UNIT_IF_PRIMARY_ATTRIBUTE
    • BlzSetUnitWeaponIntegerField now supports UNIT_WEAPON_IF_ATTACK_WEAPON_TYPE
    • BlzSetUnitWeaponIntegerField no longer causes a crash when trying to set a field related to an attack type the unit didn’t originally have
    • BlzSetUnitWeaponIntegerField now works properly with the following fields:
      • UNIT_WEAPON_IF_ATTACK_MAXIMUM_NUMBER_OF_TARGETS
      • UNIT_WEAPON_IF_ATTACK_DAMAGE_NUMBER_OF_DICE
      • UNIT_WEAPON_IF_ATTACK_DAMAGE_SIDES_PER_DIE
      • UNIT_WEAPON_IF_ATTACK_DAMAGE_BASE
    • BlzSetUnitIntegerField(unit, UNIT_IF_MOVE_TYPE, 2) now properly allows a ground unit to fly
    • Added a new field UNIT_RF_FLY_MAX_HEIGHT (ufmh)
    • BlzSetUnitBooleanField now properly sets UNIT_BF_HIDE_MINIMAP_DISPLAY
    • BlzSetUnitStringField now immediately updates the unit’s shadow when using UNIT_SF_SHADOW_IMAGE
    • BlzSetUnitRealField now correctly sets UNIT_RF_CAST_POINT and UNIT_RF_CAST_BACK_SWING regardless of when you spend your first skill point
    • ABILITY_RLF_CASTING_TIME now properly updates an ability’s casting time
  • The following features can now be found under Map Options
    • Added the ability to force players to use a specific zoom level
    • Added the ability to remove the ‘!’ from denying appearing
  • Added a new ability [Amgi]. This ability prevents bouncing missile attacks from bouncing to and from structures
    • Users will be able to modify the Targets Allowed field in this ability to modify which unit type will stop the bounces.
  • Added a new ability [AUa2]. This ability is the new version of Animate Dead that allows units to carry over their abilities

Hotkeys

  • Significantly increased the amount of bindable keys
  • Added new bindable commands for Menu, Game, Replay, and Observer commands
  • Added a Conflicts section in the hotkey menu to display any key conflicts
    • Clicking on a conflict will bring you the relevant hotkey
  • Added support for non QWERTY, non English keyboard layouts while using grid keys
  • Removed hotkeys for passive abilities
    • Hotkeys for learning passive abilities still exists
  • Unlinked Peasant and Militia hotkey conflict detection
  • Changed the ordering of mercenaries so that it is possible to assign QWER to every camp without conflict
  • Removed Pocket Factory from the list of Neutral Buildings
  • Removed Select Unit ability from the Tavern
  • Fixed an issue where Hero Select and Inventory keys were not detecting conflicts
  • Added Nether Dragon Roost to Neutral Buildings
  • Added Entangled Gold Mine to Night Elf Buildings

Multiplayer

  • Added a Makrura Snapper portrait
  • Fixed an issue with Arranged Team badges not displaying correct info
  • Fixed an issue with MMR and level not being displayed on loading screens
  • Fixed an issue with placement matches displaying incorrectly in the post-game screen
  • Added MMR data to Solo and Arranged Team Badges
  • Adjustments were made to how MMR gains and losses are calculated
    • Players have a hidden stat that is called variance. The higher the variance, the bigger the MMR swings (When a player starts their placement matches they have high variance, after many games, the variance bottoms out). In team games, the current system adds every players MMR and variance together. For example, in a 2v2 game, where one side is a 4500 arranged team, and the other side is a 4000 and 4200 rated random team, the system views it as a 9000 MMR side against a 8200 MMR side. We are changing this so that instead of taking the sum, the system now takes the average MMR and variance, so now the system will view the match as 4500 vs 4100
    • In addition to the above change, we are also doubling all MMR gains and losses
    • We are hoping these changes reduce the occurrence of extreme MMR gains and losses in some situations, while also spreading out the distribution of MMR. The team will continue to monitor this and make adjustments as necessary

Balance

General

  • All attacks with a ground area of effect attack have the Ward unit type added to their list of area of effect targets
  • Piercing damage against Heavy armor decreased from 100% to 90%

Human

  • Mountain King Bash will now be able to stun magic immune air units when attacking with an orb

Orc

  • Pulverize can now target Wards
  • Burning Oil can now target Wards

Night Elf

  • Wisp Lumber Gather rate decreased from 7 to 7.5 seconds
  • Archer health increased from 255 to 275
  • Pick up Archer, Mount Hippogryph, and Dismount cooldowns decreased from 30 to 5
  • Hippogryph Rider health increased from 780 to 800
  • Huntress glaives will no longer bounce to and from structures
  • Moon Glaives upgrade time decreased from 60 to 50

Undead

  • Units resurrected by Animate Dead now have access to their abilities they had when they were alive
  • Lich Frost Nova range increased from 700/700/700 to 750/750/750
  • Gargoyle Prioritize now toggles properly when in a group

Neutral

  • Pitlord Cleave can now target Wards
  • Dark Ranger Drain Life mana cost decreased from 50/50/50 to 25/25/25
  • Dark Ranger Drain Life self damage type changed from Magic to Universal. This will allow Life Drain to continue to transfer while the caster is magic immune
  • Tinker Pocket Factory spawn interval decreased from 5/4.5/3.5/3 to 4.5/4/3.5/3 per Engineering level
  • Tinker Cluster Rockets max damage per interval increased from 105/195/300 to 200/250/300
    • Cluster Rockets contains 4 damage intervals, so if a unit stays in the area for the whole duration of the spell, it will take 4 instances of damage. This change increases the max damage that can be spread across multiple units per interval.
  • Brewmaster Breath of Fire damage increased from 65/125/170 to 80/130/180
  • Brewmaster Breath of Fire max damage increased from 480/800/1200 to 600/900/1200
  • Brewmaster Breath of Fire initial area of effect increased from 25/25/25 to 60/60/60
  • Brewmaster Breath of Fire final area of effect increased from 125/125/125 to 175/175/175
    • Previously, Breath of Fire could hit units that were significantly farther away than the visuals of the spell suggested. These changes make it so that the area of effect are brought in line with the visuals. The area of effect parameter controls the initial width of the Breath, while the final area of effect controls the radius at the tail end of the spell. To compensate for the nerf to range, overall damage of the spell has been increased.
  • Brewmaster Breath of Fire damage over time from 7/14/21 to 10/15/25
  • Removed Vampiric Aura and Death Coil from Level 3 Skeletal Orc
  • Fixed an issue where the neutral variant of Brilliance Aura was not displaying decimal values in the tooltip

Bug Fixes

  • Fixed an issue with Tinker stacking the effects of regeneration from items when killed in Robo-form
  • Fixed an issue where Demon Hunter Immolation would continue to drain mana when turned off if Immolation is leveled during Hex
  • Units that are hexed will no longer have a short window where their items bonuses do not apply to them
  • Orb effects will now properly proc when units auto acquire targets.
  • Orb of Slow and Orb of Lightning will now function properly if bought while silenced
I still think they should revert back to 1.31. Than add all the things they did for reforged. Like campaing heroes for meele maps ect.... Cause fixing everything dosen't pay off at least for me when you have the already working version. Or why can't we have two version that both work online. But do what you want Blizzard.
 
Last edited:
I find bug editor:
After this function: call BlzSetItemBooleanFieldBJ( GetItemOfTypeFromUnitBJ(GetTriggerUnit(), ‘I00G’), ITEM_BF_CAN_BE_DROPPED, true )
any items is used when raised as a rune, which should not be the case.
A lot of these natives now modify the base object. i.e. apply to all objects of the type... we can only hope it'll be fixed.
 
I still think they should revert back to 1.31. Than add all the things they did for reforged. Like campaing heroes for meele maps ect.... Cause fixing everything dosen't pay off at least for me when you have the already working version. Or why can't we have two version that both work online. But do what you want Blizzard.
Reverting back to 1.31 is quite worthless. tulee had mentioned in the past that any later versions of Warcraft 3, specifically 1.31 and the ones closer to the release of 1.32 (the "gold" version of Reforged), have numerous bugs that were remain unresolved by the Blizzard team (like the gameplay breaking issue related to the triggers, black screen loop after exiting the game session, among vanilla campaign-specific issues). They were rushing to get Reforged out on the release date. Although some of those bugs were fixed post 1.32, Reforged 2.0. eventually happened and brought numerous bad bugs that were literally ruining the gameplay experience (like the invisible models and unit portraits in HUD not matching the actual model for no reason). So it's fair enough to assume issues people encounter in-game are because they are using Warcraft 3 patches higher than 1.26, which still have quite a great many bugs that are still there and remain unresolved. 1.26 is the latest "legitimate game patch" of Warcraft 3 developed by the original Blizzard team (as if it was the 2003) before 1.27 focused a lot about the development of "Reforged".
 
Reverting back to 1.31 is quite worthless. tulee had mentioned in the past that any later versions of Warcraft 3, specifically 1.31 and the ones closer to the release of 1.32 (the "gold" version of Reforged), have numerous bugs that were remain unresolved by the Blizzard team (like the gameplay breaking issue related to the triggers, black screen loop after exiting the game session, among vanilla campaign-specific issues). They were rushing to get Reforged out on the release date. Although some of those bugs were fixed post 1.32, Reforged 2.0. eventually happened and brought numerous bad bugs that were literally ruining the gameplay experience (like the invisible models and unit portraits in HUD not matching the actual model for no reason). So it's fair enough to assume issues people encounter in-game are because they are using Warcraft 3 patches higher than 1.26, which still have quite a great many bugs that are still there and remain unresolved. 1.26 is the latest "legitimate game patch" of Warcraft 3 developed by the original Blizzard team (as if it was the 2003) before 1.27 focused a lot about the development of "Reforged".
Well I think its not worthless reverting back they can fix those bugs if they revert too. They can add all the things they added to patch 2.0 of "Reforged"
 
Community Edition already created the perfect template for this IMO.

Community Edition already created the perfect template for this IMO.
Yeeah... I think Blizzard should do it.

Community Edition already created the perfect template for this IMO.
And what I mean by reverting back to 1.3.1. is to remove classic from reforged and start paching again.
 
@Pekisa7 Nobody's gonna do it. The whole reason they merged Classic and Reforged is to pull the old player base over (and to keep us happy / make it a gift to the oldies). Just like they did with Overwatch "2" and Valve did with Counter-Strike 2. In the always-online and multiplayer-first world of modern live service games, a high player count is the currency to measure games by. High online counts translate to microtransactions aka money.
If they won't budget developer time to make bugfixes today (this update was somewhat promising, not sure who to thank for this: management or individual devs), then they will not allocate any resources to an alternative bnet server.
 
@Pekisa7 Nobody's gonna do it. The whole reason they merged Classic and Reforged is to pull the old player base over (and to keep us happy / make it a gift to the oldies). Just like they did with Overwatch "2" and Valve did with Counter-Strike 2. In the always-online and multiplayer-first world of modern live service games, a high player count is the currency to measure games by. High online counts translate to microtransactions aka money.
If they won't budget developer time to make bugfixes today (this update was somewhat promising, not sure who to thank for this: management or individual devs), then they will not allocate any resources to an alternative bnet server.
I don't know why people keep pushing this "keep the playerbase together" line. The playerbase was split down the middle as soon as Reforged launched. There was a huge amount of people who couldn't even play the game to begin with due to how it bloated hardware requirements and HD Space. Plus the massive differences in menus and systems make the two versions feel almost like totally different games despite RF being a poorly implemented patch. It's clear to me that Blizz execs didn't care at all about splitting the playerbase and any thought from the tiny and overworked dev team about trying to preserve that was a fantasy at best. They didn't want to "pull the playerbase over" -- I doubt there was any plan at all, considering Reforged was basically already cancelled and only "finished" so they could get the preorder money.

With all of that negative stuff said, let's move on to the positives: Community Edition proves it's entirely possible to create a legacy client with all the functionality of 1.29/1.31 that's still compatible with Reforged content, and if they devoted professional time and resources to it I'm sure they could do something amazing, and in a relatively short and simple amount of time.

Since it seems the new team is listening to constructive criticism and fan requests, I highly recommend someone with access to the PTR forums float this idea there. It might not lead to anything, but at least there'd be a chance, and it'd be really cool to see!
 
I don't know why people keep pushing this "keep the playerbase together" line.
@Homor Actually I would like to not have it forced and then be left without choice. Whether with Reforged or CS2. I definitely would have chosen to remain on the classic patch. I sat there on different days for hours at a time on PTR 1.31.1.x Battlenet. At and after 1.32 release. All alone in the lobby. Not a soul in sight. That's PTR though. I was left so disappointed, I didn't come back until a year later. Back to 1.32.10. When or after the "Classic Team" had been disbanded and laid off :(

The positive thing (for me) is that I didn't have to buy Reforged and could continue using my old key. I still haven't. I don't think there's a feasible event that would sway me to buy Reforged HD key. The team would need to move mountains.

I was agreeing with you on why, while reading the reply. But then I had an argument why not: Blizzard kept hoping at an e-sports success. Arguably, Starcraft 2 died down, Overwatch with all that heavy e-sports-themed push remained imho a casual game. Was Reforged going to be the competitor to all these other highly competetive online PvP games? I barely know what's going on with WC3 melee scene, but I felt that Blizzard was getting people rallied up. Supporting streams and tournaments too. You know how much people hate(d) the new graphics design? What if the game was split up? How many of the melee community would split off to remain on Classic, interfering with the "esports title idea"?

I think of all people someone like @Kam could share the internal sentiment about why Classic and Reforged were merged to be one. Whether he can/is going to comment though?..
 
@Homor Actually I would like to not have it forced and then be left without choice. Whether with Reforged or CS2. I definitely would have chosen to remain on the classic patch. I sat there on different days for hours at a time on PTR 1.31.1.x Battlenet. At and after 1.32 release. All alone in the lobby. Not a soul in sight. That's PTR though. I was left so disappointed, I didn't come back until a year later. Back to 1.32.10. When or after the "Classic Team" had been disbanded and laid off :(

The positive thing (for me) is that I didn't have to buy Reforged and could continue using my old key. I still haven't. I don't think there's a feasible event that would sway me to buy Reforged HD key. The team would need to move mountains.

I was agreeing with you on why, while reading the reply. But then I had an argument why not: Blizzard kept hoping at an e-sports success. Arguably, Starcraft 2 died down, Overwatch with all that heavy e-sports-themed push remained imho a casual game. Was Reforged going to be the competitor to all these other highly competetive online PvP games? I barely know what's going on with WC3 melee scene, but I felt that Blizzard was getting people rallied up. Supporting streams and tournaments too. You know how much people hate(d) the new graphics design? What if the game was split up? How many of the melee community would split off to remain on Classic, interfering with the "esports title idea"?

I think of all people someone like @Kam could share the internal sentiment about why Classic and Reforged were merged to be one. Whether he can/is going to comment though?..
That's what I mean, and exactly what Community Edition does. You aren't forced to download a new version, you're allowed to play the one you want. That's what I want Blizzard to do: have two versions people can choose between, and you aren't forced to play one or the other.
 
Community Edition is currently dead. I mean afaik the last release was a long time ago with many improvements since then sitting unreleased. The channel activity died down. I'd be all for it.

I had played for some time on rubattlenet maaany years ago, but it's practically empty now. iccup hadn't worked when I tried to install it and it's dota-focused anyway. idk about the server with irina-bot. In the end, I want to have people to play with. Having like 10 custom game lobbies without variety or players to join some random map I might host - isn't gonna cut it for me. In the end, I am "forced" to follow. btw, gameranger had a following for Classic too.

It's the same issue of community gathering like for very old games. Technically you could play any old game - or in our case version, - if you assembled a group. Daily/weekly meetings all that. It requires a lot of (too much) coordination and winning people for your cause. That's all in the depths of Discords now... if it exists at all. (speaking of, have you heard of "unofficial" Reforged server? yeah that one exists too)
 
Community Edition is currently dead. I mean afaik the last release was a long time ago with many improvements since then sitting unreleased. The channel activity died down. I'd be all for it.

I had played for some time on rubattlenet maaany years ago, but it's practically empty now. iccup hadn't worked when I tried to install it and it's dota-focused anyway. idk about the server with irina-bot. In the end, I want to have people to play with. Having like 10 custom game lobbies without variety or players to join some random map I might host - isn't gonna cut it for me. In the end, I am "forced" to follow. btw, gameranger had a following for Classic too.

It's the same issue of community gathering like for very old games. Technically you could play any old game - or in our case version, - if you assembled a group. Daily/weekly meetings all that. It requires a lot of (too much) coordination and winning people for your cause. That's all in the depths of Discords now... if it exists at all. (speaking of, have you heard of "unofficial" Reforged server? yeah that one exists too)
Yes, player population (specifically the casual player population) is a huge reason why most people will not leave the latest Wc3 patch. I see it heavily in the custom campaign community. For casual players, dropping a CC file into the campaign folder in wc3 is complicated enough; trying to get them to try different patches of Wc3, which may or may not cause bugs in various custom campaigns, is something bordering on impossible. The number of bugs in the early "Reforged" release (1.32) may have been enough to push a large number of players to older community versions of wc3, but that momentum was never really taken advantage of, and a decent alternative never really took off.

With the recent versions of wc3 (especially 2.03+) becoming far less bug-ridden and essentially being able to play anything made on older patches minus maps using memory hacks or 3rd party editors, I am pretty confident the Battlenet App version of wc3 will basically remain the dominant version for the ENG-speaking community. The more maps/campaigns made on the latest patches, the more momentum anyone will have to overcome in order to return to older versions of Wc3.
 
@Pekisa7 Nobody's gonna do it. The whole reason they merged Classic and Reforged is to pull the old player base over (and to keep us happy / make it a gift to the oldies). Just like they did with Overwatch "2" and Valve did with Counter-Strike 2. In the always-online and multiplayer-first world of modern live service games, a high player count is the currency to measure games by. High online counts translate to microtransactions aka money.
If they won't budget developer time to make bugfixes today (this update was somewhat promising, not sure who to thank for this: management or individual devs), then they will not allocate any resources to an alternative bnet server.
So they gifted us a broken product. Then they all trying to make up for it by trying to fix it and they haven't fix half of the bugs. They shouldn't have megerd reforged and classic in the first place. And like Homor said why can't we have two versions of the same game. Also if they don't want to start from patching classic 1.3.1 onwards then they are being lazy.

I know i am being too harsh on Blizzard I am sorry. But I am just trying to fight for what I want. I know it depends on Blizzard whenever they are gonna return classic or still work on Reforged . But i am just a guy suggesting something they don't have to listen to me because in reallty they are a company who listen to their manager on what to do with Warcraft 3. So if they don't return classic on blizzcon 2026 i will likley compormise to work on my map in Reforged.
 
Last edited:
It'd definitely be good to have two separate versions, the "main" one and the "legacy" one. Just like Diablo 2 Resurrected handled it. The cool thing about a Legacy client is you wouldn't even have to maintain it or update it. Just get it to a "stable" version and then you leave it alone. This is a pretty standard thing and something you see a lot in the industry, and I have no doubt the original Reforged team wanted to do that originally before the game's budget got cut.
 
It'd definitely be good to have two separate versions, the "main" one and the "legacy" one. Just like Diablo 2 Resurrected handled it. The cool thing about a Legacy client is you wouldn't even have to maintain it or update it. Just get it to a "stable" version and then you leave it alone. This is a pretty standard thing and something you see a lot in the industry, and I have no doubt the original Reforged team wanted to do that originally before the game's budget got cut.
I agree with you that we should have two seprate version. A legacy and a main one. But I think they should update the legacy one too.
 
I agree with you that we should have two seprate version. A legacy and a main one. But I think they should update the legacy one too.
Only as much as necessary. Keep in mind, the Legacy version would exist to preserve the game how it used to be. That would ultimately mean not updating it anymore than absolutely necessary.
 
Only as much as necessary. Keep in mind, the Legacy version would exist to preserve the game how it used to be. That would ultimately mean not updating it anymore than absolutely necessary.
I understand. But I think its still necessary. I don't like the remastered version of War 3 . But what Blizzard decides what to do with War 3... They decide. I am just suggesting something. But they don't have to do it if they don't want to.
 
Since this thread has been hijacked by fringe pirate enthusiasts covering as Warcraft III justice warriors, here's a post that is on topic:
 
Since this thread has been hijacked by fringe pirate enthusiasts covering as Warcraft III justice warriors, here's a post that is on topic:
I just said what I wanted but Blizzard dosen't have to do it if they don't want to.
 
I just said what I wanted but Blizzard dosen't have to do it if they don't want to.
This is a thread for people to discuss the patch notes / give feedback. You keep asking for Blizzard to revert back to 1.31 or make separate versions of the game, which would split their time and energy between the latest and a "classic" version, as well as splitting the wc3 community up. I think if you give the latest patch a chance, you might find its in a far better state than 1.31 ever was, since in 1.31 they were rushing to push out the release of "reforged" and let a bunch of bugs go un-fixed in that version.
 
This is a thread for people to discuss the patch notes / give feedback. You keep asking for Blizzard to revert back to 1.31 or make separate versions of the game, which would split their time and energy between the latest and a "classic" version, as well as splitting the wc3 community up. I think if you give the latest patch a chance, you might find its in a far better state than 1.31 ever was, since in 1.31 they were rushing to push out the release of "reforged" and let a bunch of bugs go un-fixed in that version.
But it still full of bugs . I still think its necessary to revert to "Classic". At least for some fans of Warcraft 3 including me. I mean they could still fix those bugs if they revert back. I don't really like "Reforged", but I will give it a chance next year. If they fix it. If not then revert back to 1.31.. But if they don't want to I can't do anything about it. And its ok Blizzard. But I am still with my idea of reverting back. Peace.
 
But it still full of bugs . I still think its necessary to revert to "Classic". At least for some fans of Warcraft 3 including me. I mean they could still fix those bugs if they revert back. I don't really like "Reforged", but I will give it a chance next year. If they fix it. If not then revert back to 1.31.. But if they don't want to I can't do anything about it. And its ok Blizzard. But I am still with my idea of reverting back. Peace.
If there are bugs, then feel free to report them on this thread so Blizzard can see them and fix them. The small classic games team likely doesn't have enough people to test their patches in depth, so it's up to players to report the problems they find so Blizzard can fix them.
 
If there are bugs, then feel free to report them on this thread so Blizzard can see them and fix them. The small classic games team likely doesn't have enough people to test their patches in depth, so it's up to players to report the problems they find so Blizzard can fix them.
Maybe the correct Silvermoon priest portrait not shown when toggled?
 
Here's a little bug I wish they'd fix but probably not important to most people: custom scorescreen hero icons no longer work. If you set it to a custom icon in the object editor, it will just show a blank space in the scorescreen.

And a "feature" request: please make it possible again to customize other aspects of the scorescreen: 1) The player icon. In older versions of my WC1 map I replaced the player icons with WC1 versions of the footman & grunt icons and it looked pretty neat, but that's not possible anymore. 2) We used to be able to put custom images for the scorescreen background, but that's not possible anymore either.

While we're at it, please also make it possible to replace the race icons in the default melee loading screen. Would be cool to replace e.g. the Lordaeron logo with a Stormwind logo.
 
Since this thread has been hijacked by fringe pirate enthusiasts covering as Warcraft III justice warriors, here's a post that is on topic:
What does piracy have to do with any of this? Nobody was talking about pirating the game.

Just to get it on the record: I've never pirated Warcraft 3. I refunded it when Reforged came out because I didn't like it, but I kept the files I already downloaded and had backed up. What you're paying for when you "buy" Warcraft 3 is the right to use Blizzard's launcher and online service with it. Keeping your old files isn't piracy -- otherwise buying the game used or giving it to a friend would be piracy. I hope that clears it up.

Plus, you can still talk about the patch all you want. It's just that nobody replied to talk about it in a while.

Seriously dude, I think you're confused.
 
Last edited:
Look at the thread title and correct your statement.
You've been off-topic since forever.
And yes, many of these so called pre-Reforged white knights don't have the original game.
My comments aren't disruptive and can be easily ignored. I'm just talking about what I'd like to see in the future of Reforged is all. It's on-topic because we're talking about what changes Blizzard is making to the game and what we want to see. I'll drop the subject here since it's annoying people, but I don't think what I've been talking about is that disruptive.

Also, you need to stop being so disrespectful to people who have different opinions on this than you. Calling people "white knights" and accusing them of being pirates (which is off-topic) isn't the way to go. You don't need to fight with your fellow fans, you need to figure out a way the community can overcome their differences and come together. I really hate this hostile tone you're going for when nobody even insulted you.

But again, I've said all I wanted to say and I'll leave the thread alone. In the future, though, stop being so hostile.
 
My comments aren't disruptive and can be easily ignored. I'm just talking about what I'd like to see in the future of Reforged is all. It's on-topic because we're talking about what changes Blizzard is making to the game and what we want to see. I'll drop the subject here since it's annoying people, but I don't think what I've been talking about is that disruptive.

Also, you need to stop being so disrespectful to people who have different opinions on this than you. Calling people "white knights" and accusing them of being pirates (which is off-topic) isn't the way to go. You don't need to fight with your fellow fans, you need to figure out a way the community can overcome their differences and come together. I really hate this hostile tone you're going for when nobody even insulted you.

But again, I've said all I wanted to say and I'll leave the thread alone. In the future, though, stop being so hostile.
Parallel topics=/=on topic.
And don't take it personally. It's not only you writing partly related stuff, conversations spawned after such posts.
Please do not tell me what to do as I do not tell you more than to respect the rules and stay on topic, more so after you were first to be insulting calling me confused.
Also please don't self flagellate with the flail in someone else's hands.
You're being hostile yourself, not just in the post I replied to just now but in others where you sprawl about Blizzard and the Warcraft III devs.
But again, please stay on topic.
 
Parallel topics=/=on topic.
And don't take it personally. It's not only you writing partly related stuff, conversations spawned after such posts.
Please do not tell me what to do as I do not tell you more than to respect the rules and stay on topic, more so after you were first to be insulting calling me confused.
Also please don't self flagellate with the flail in someone else's hands.
You're being hostile yourself, not just in the post I replied to just now but in others where you sprawl about Blizzard and the Warcraft III devs.
But again, please stay on topic.
I meant no offense, I was simply trying to clarify my point. I didn't mean to insult you by saying you were confused, and in my native tongue such comments aren't insulting. I apologize if it came off rude.
 
I think if you give the latest patch a chance, you might find its in a far better state than 1.31 ever was
Last night while I was asleep I gave the latest patch a chance, to see how it was doing, in my dreams. In my dream, in order to make the menu 3D now instead of a 2D menu, they had replaced the menu with a warcraft 3 map that still had the Cinematic Mode UI around the top and bottom. And when we drag the mouse around the screen, it would hover over floating texts detected using trackables that acted as the main menu buttons, even though they had that comically grainy floating text font set up. But see the point was that they had finally started trying to make it more WC3 and less activision web menu. Thinking about it again now, like, even in that dream I had to kind of respect how much it showed they cared, you know?

But anyway I already tried it so I'm probably going to go back to the 1.2X patches today if I play some Warcraft 3 to be honest. I'm not a pirate, I bought the game 50 - 60 times.
 
Sorry if this is off topic, but another thing I find a bit weird is that there is no victory/defeat music for the WC1 and WC2 music. They're available from the WC1&WC2 Remastered games, so why didn't they add them to WC3 instead of playing a random regular music file in the victory/defeat screen?

Not really a bug, but certainly a big oversight (that probably almost no one cares about) in the 2.x version of the game.
 
The maximum number of tiles has been increased from 16 to 64!
The new tileset expansion in the new PTR patch (one of the JNGP's unique features) is somewhat a big addition for Reforged users.
Unfortunately, it's still a half-working. For now. There's a bug regarding that matter:

In short, if you are using more than 16 tiles in your map, the 17th onwards won't be applied.
After you placed the 16th one, every tile you placed will just loop back to the first 16.
Example: Lordaeron Summer Dirt and Northrend Ice being picked as 1st and 17th tiles. When you place the Northrend Ice, it will just display Lordaeron Summer Dirt instead.

(Haven't been playing Reforged just yet, but I'm very excited about new features in Reforged)

EDIT: My mistake, JNGP doesn't allow you to use more than 16 tilesets, unlike the current PTR patch.
JNGP only allows you to use mixed tilesets in just one map, but only 16 were allowed on your Terrain palette.
(Thanks to Elprede for a correction)
 
Last edited:
 
Back
Top