- Joined
- Jan 12, 2011
- Messages
- 1,197
Have you ever encountered with or discovered any WC3 bugs? If you have, feel freee to post and discuss.
-
Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
-
Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
Anyone knows any Warcraft 3 bugs?
- Status
- Joined
- Aug 14, 2006
- Messages
- 7,602
You mean in basic game?
Community Moderator
- Joined
- Jul 14, 2012
- Messages
- 3,546
Blade master is OP.
- Joined
- Jun 20, 2009
- Messages
- 880
Blade Master is trash without high level Shadow Hunter or TC on his side.
Anyways, WC3 is pretty much bug free. There are only some graphical bugs left.
• While watching replays, sometimes the buildings that has been destroyed will still appear in the minimap.
• Sometimes when your Hero is targeted by any missile, and you TP away, the missile will follow you to the other side of the map. It doesn't deal any damage when it reaches you though.
- Joined
- Aug 14, 2006
- Messages
- 7,602
Nope. Still one of the best heroes there is, if not the best in a small type of games.
- Joined
- Jun 23, 2007
- Messages
- 4,066
hahahahaha
- Joined
- Apr 2, 2013
- Messages
- 3,956
Unit meshing when there's about 500 units fighting.
Spell Reviewer
- Joined
- Jan 18, 2005
- Messages
- 27,258
I only have a few minutes but here are a lot.
In JASS2, a local variable declared in a function using the local keyword is not reference counted when it is popped from the stack at function return. The result is that handles using such a variable can suffer a reference leak preventing a handle index from every being recyclable.
TriggerSleepAction does not wait the quoted 0.1 seconds in multiplayer. Network latency apparently results in it waiting considerably longer than the specified time for no apparent reason. Timers, another method of timing in JASS2, do not suffer this problem and will be accurate between clients.
Unit art that is near the absolute edge of the play field can cause a fatal error if the origin falls outside the play field.
Preload appears to execute command scripts with very poor input validation. It is possible to issue preload statements that are capable of generating or downloading files. By abusing security exploits in other programs or the operating system it is possible to install a worm into a system and thus compromise a system.
BattleNet does not validate custom games if they are logical. It is possible for people to join custom games as artificial (spoofed) names or for custom games to existing without any clients in them. In reality a host server could be used to advertise the same session over multiple servers, some of which are VPN Lans, as there is no internal authentication.
The way terrain mesh deformations are computed are not deterministic across different client builds and configurations. This will result in a game desynchronization between Mac and Windows users if terrain mesh Z is required to compute game state or if users on the same builds have different visual settings for physics (or whatever it is called).
The inbuilt save/load functionality does not correctly store game state. Saving loses critical state information such as timer timeout resulting in broken loaded games unless special effort is taken to store and rebuild the state using triggers. The two known trouble causers are Timers and variables with array index 8191 (which is lost).
Periodic timers that are paused and resumed will become once off timers. The periodic status of the timer will be lost resulting in it firing only once after the remaining time once resumed unless started again.
Timers will still execute their expiry function even after being destroyed. They must first be paused and then destroyed to be sure that an extra call of the function with a dead timer does not occur.
Dependency equivalents can be used to form an infinite loop which will cause WC3 to fatal error.
Tranquillity will continue to heal units even after they died resulting in dead units with life greater than 0.405. This will cause standard trigger checks for if a unit is dead to return a false positive (a unit is alive when it is actually dead).
Due to floating point error it is possible for heroes to lose movement speed and life/mana regeneration from hero attributes if large attribute quantities are involved.
Item abilities that add life and damage do not correctly update applied attribute when their level increases but do correctly remove the appropriate attribute amount for that level. this allows one to permanently modify unit attributes such as life, mana and damage and prevents such abilities being used as hero skills.
Shadow strike when set to 0 second period will apply the damage as fast as the game permits (several times a frame) resulting in excessive resource usage, usually to the extent the game will become a slideshow or apparently freeze.
Setting attack delay to 0 with an animation backswing of 0 will result in 8.3 (or something, the max attack speed) attacks per second but use excessive resources resulting in frame drop, slide show like performance or even apparent game freezes.
It is possible for a timer to be scheduled with a timeout less than a game frame. There is no practical or meaningful reason for this to be possible as it should not affect the results of the game in any way but can waste excessive resources.
Removing Locust does not remove all the unit flag modifications it applied. Units will still be left mostly in Locust mode unless a considerable list of hacky flag changing fixes are applied to it (in which case it still may not be perfect).
Units which have their type modified using chaos get all attribute modifications (tomes, items etc) reapplied to them and left permanently on their statistics.
Using Avatar and such unit type morphing abilities to change non-hero units to heroes and heroes to non-hero units is prone to causing a fatal error.
Non-hero units with inventory slots capable of using items will crash the game when they consume a tome that gives hero attributes.
Items that are consumed on pickup or killed by combat are never removed, instead they are left on the playfield as dead and can be considered a leak unless manually removed using triggers.
Destroying a trigger when event responses are still queued on it can result in a fatal error.
It is still possible to type cast variables using their in-memory values despite Blizzard stating it should not be possible.
Obtaining over 100% magic damage reduction will cause abilities to reheal you instead of making you immune. Any more reduction past 100% is equivalent to magic absorb.
Negative damage (healing) is still reduced the same as normal damage and not treated as healing (which ignores most reductions).
Firing Flaming Arrows past the maximum unit range manually will cause the caster animation to bug into a high speed state. The caster acts the same as usual.
Auto casting arrow skills modifies the unit attack rather than actually auto casting the ability. The result is extra range and cooldown from it is mostly ignored.
Buildings that are moved using SetUnitX/Y have their model and damage interaction area moved but pathing collision and selection circle still remains where it was before the move.
Some sources of damage, such as disease cloud or from goblin sappers, bypasses mana shield and deals direct life damage.
Creating a unit in a crowded area uses excessive resources as a displacement location tries to be determined. Frames may even be dropped as a result.
Using an ability with a target circle that has a stupidly large area of effect (of map wide scale or more) will cause the game to fatal error.
Various bugged art assets can cause the game to fatal error when they are created in view. Modified lightning as an anti-map hack tool is the best known example.
Strings are never destroyed once created. Every unique string will occupy memory until the end of the session and can be considered a leak if never used again.
Object editor data that is translated into a different format can persist between sessions and break future sessions. This is best known from wigitizer and how a game restart is required to play a different map.
Yeh and these were just some of the bugs.
In JASS2, a local variable declared in a function using the local keyword is not reference counted when it is popped from the stack at function return. The result is that handles using such a variable can suffer a reference leak preventing a handle index from every being recyclable.
TriggerSleepAction does not wait the quoted 0.1 seconds in multiplayer. Network latency apparently results in it waiting considerably longer than the specified time for no apparent reason. Timers, another method of timing in JASS2, do not suffer this problem and will be accurate between clients.
Unit art that is near the absolute edge of the play field can cause a fatal error if the origin falls outside the play field.
Preload appears to execute command scripts with very poor input validation. It is possible to issue preload statements that are capable of generating or downloading files. By abusing security exploits in other programs or the operating system it is possible to install a worm into a system and thus compromise a system.
BattleNet does not validate custom games if they are logical. It is possible for people to join custom games as artificial (spoofed) names or for custom games to existing without any clients in them. In reality a host server could be used to advertise the same session over multiple servers, some of which are VPN Lans, as there is no internal authentication.
The way terrain mesh deformations are computed are not deterministic across different client builds and configurations. This will result in a game desynchronization between Mac and Windows users if terrain mesh Z is required to compute game state or if users on the same builds have different visual settings for physics (or whatever it is called).
The inbuilt save/load functionality does not correctly store game state. Saving loses critical state information such as timer timeout resulting in broken loaded games unless special effort is taken to store and rebuild the state using triggers. The two known trouble causers are Timers and variables with array index 8191 (which is lost).
Periodic timers that are paused and resumed will become once off timers. The periodic status of the timer will be lost resulting in it firing only once after the remaining time once resumed unless started again.
Timers will still execute their expiry function even after being destroyed. They must first be paused and then destroyed to be sure that an extra call of the function with a dead timer does not occur.
Dependency equivalents can be used to form an infinite loop which will cause WC3 to fatal error.
Tranquillity will continue to heal units even after they died resulting in dead units with life greater than 0.405. This will cause standard trigger checks for if a unit is dead to return a false positive (a unit is alive when it is actually dead).
Due to floating point error it is possible for heroes to lose movement speed and life/mana regeneration from hero attributes if large attribute quantities are involved.
Item abilities that add life and damage do not correctly update applied attribute when their level increases but do correctly remove the appropriate attribute amount for that level. this allows one to permanently modify unit attributes such as life, mana and damage and prevents such abilities being used as hero skills.
Shadow strike when set to 0 second period will apply the damage as fast as the game permits (several times a frame) resulting in excessive resource usage, usually to the extent the game will become a slideshow or apparently freeze.
Setting attack delay to 0 with an animation backswing of 0 will result in 8.3 (or something, the max attack speed) attacks per second but use excessive resources resulting in frame drop, slide show like performance or even apparent game freezes.
It is possible for a timer to be scheduled with a timeout less than a game frame. There is no practical or meaningful reason for this to be possible as it should not affect the results of the game in any way but can waste excessive resources.
Removing Locust does not remove all the unit flag modifications it applied. Units will still be left mostly in Locust mode unless a considerable list of hacky flag changing fixes are applied to it (in which case it still may not be perfect).
Units which have their type modified using chaos get all attribute modifications (tomes, items etc) reapplied to them and left permanently on their statistics.
Using Avatar and such unit type morphing abilities to change non-hero units to heroes and heroes to non-hero units is prone to causing a fatal error.
Non-hero units with inventory slots capable of using items will crash the game when they consume a tome that gives hero attributes.
Items that are consumed on pickup or killed by combat are never removed, instead they are left on the playfield as dead and can be considered a leak unless manually removed using triggers.
Destroying a trigger when event responses are still queued on it can result in a fatal error.
It is still possible to type cast variables using their in-memory values despite Blizzard stating it should not be possible.
Obtaining over 100% magic damage reduction will cause abilities to reheal you instead of making you immune. Any more reduction past 100% is equivalent to magic absorb.
Negative damage (healing) is still reduced the same as normal damage and not treated as healing (which ignores most reductions).
Firing Flaming Arrows past the maximum unit range manually will cause the caster animation to bug into a high speed state. The caster acts the same as usual.
Auto casting arrow skills modifies the unit attack rather than actually auto casting the ability. The result is extra range and cooldown from it is mostly ignored.
Buildings that are moved using SetUnitX/Y have their model and damage interaction area moved but pathing collision and selection circle still remains where it was before the move.
Some sources of damage, such as disease cloud or from goblin sappers, bypasses mana shield and deals direct life damage.
Creating a unit in a crowded area uses excessive resources as a displacement location tries to be determined. Frames may even be dropped as a result.
Using an ability with a target circle that has a stupidly large area of effect (of map wide scale or more) will cause the game to fatal error.
Various bugged art assets can cause the game to fatal error when they are created in view. Modified lightning as an anti-map hack tool is the best known example.
Strings are never destroyed once created. Every unique string will occupy memory until the end of the session and can be considered a leak if never used again.
Object editor data that is translated into a different format can persist between sessions and break future sessions. This is best known from wigitizer and how a game restart is required to play a different map.
Yeh and these were just some of the bugs.
- Joined
- Apr 2, 2013
- Messages
- 3,956
I applaud to your list. How did you think of all those?
Community Moderator
- Joined
- Jul 14, 2012
- Messages
- 3,546
Level 7 Blademaster, level 3 Critical Strike, Wind Walk and Bladestorm I think. Killled a Level 10 Demon Hunter and almost killed a warden all whilst being attack by mountain giants and chimaera.
- Joined
- Aug 14, 2006
- Messages
- 7,602
Yeah. You're just proving my point.
Community Moderator
- Joined
- Jul 14, 2012
- Messages
- 3,546
That was what I was trying to do.
Mass Gryphon riders and three level ten heroes = OP.
Mass Gryphon riders and three level ten heroes = OP.
- Joined
- Aug 14, 2006
- Messages
- 7,602
Yeah, well, that goes over the top. Don't except to have that kind of setting in a normal game.
Community Moderator
- Joined
- Jul 14, 2012
- Messages
- 3,546
Most of the games I find on B.net are 8 player FFA with the winner the being the one who gets the above build.
Oh yes and steam tanks.
Oh yes and steam tanks.
Spell Reviewer
- Joined
- Jan 18, 2005
- Messages
- 27,258
I forgot the bug that if WC3 units fail to be displaced properly (or at the wrong time?) they cause a fatal error. This is most common with creating units using triggers inside stuff or resurrecting a destructible (eg a tree which has collision) underneath a unit.
- Joined
- Jan 12, 2011
- Messages
- 1,197
Wow, these bugs are all very interesting. Thanks everyone, but, of course, I welcome more facts about bugs.
Spell Reviewer
- Joined
- Jan 18, 2005
- Messages
- 27,258
I admit it would be nice to know the cause of the bugs (what was wrong with the programming) but without the source code it is not really worth the effort. Recreating some is hard enough, let alone step through assembly of the game process.
- Joined
- Sep 13, 2014
- Messages
- 106
A list of some of the interesting glitches in Wc3 (some are marked as working in old versions only) - Warcraft III/Tricks and Glitches - SDA Knowledge Base. (Ignore the thing about the mpqs, not really a glitch but useful knowledge to have for speedrunning) The most interesting glitch that works on current versions is, in the night elf campaign (esp the underground one with illidan), get healing wards. They can be placed in places you don't have map vision and allow you to reach places with Maiev's blink you are not supposed to have access to. Seperately, see this video:
Also, I don't remember if I posted anything on these already, I was just googling stuff and saw this page, and thought I should contribute.
Also, I don't remember if I posted anything on these already, I was just googling stuff and saw this page, and thought I should contribute.
Spell Reviewer
- Joined
- Jan 18, 2005
- Messages
- 27,258
That is because Blink itself was designed very loosely so that the Warden can react inaccessible places as part of another campaign mission where it was required. Sure the wards were an oversight but I have seen custom games mess up like that dozens of times.
- Joined
- Oct 18, 2008
- Messages
- 942
crypt lord
- Joined
- Aug 18, 2009
- Messages
- 4,097
Some of those are design questions, though. A couple of bugs play an integral part in wc3 mapmaking, too, since Blizzard failed to present viable alternatives.
Spell Reviewer
- Joined
- Jan 18, 2005
- Messages
- 27,258
They did in SC2, just not in WC3.
- Joined
- Jun 2, 2004
- Messages
- 849
SC2 is not a viable alternative for WC3 
- Status
