- Joined
- Jan 1, 2011
- Messages
- 1,540
I felt the need to write this stuff down, otherwise I would forget and this knowledge may be lost to the war3 modding community. The following will be an unordered list of bugs and their solutions. This list will probably grow over time as I remember them, or as other members provide their own list of bugs and fixes.
- Using slot status or controller status natives during initialization can cause desyncs.
- Solution: Don't do these comparisons until after the game starts.
- Unable to set a player name in multiplayer (Credit to Xace for discovering this)
- Solution: Loop through all players, and set their names using SetPlayerName() during initialization. This will allow the function to work at later times like it used to.
- Modifying some default frames will break replays
- Solution:
You will have to do this for every frame function that returns a handle and that does not exist in replays. You only have to do this once per frame. The location leak is intentional, do not clean it. If you are using lua, you may have to create a table storing these locations, otherwise the GC might free them, causing handle issues again.JASS:
local framehandle frame = BlzGetFrameByName("name",0) if frame == null then// You are in a replay and this frame doesn't exist call Location(0,0) //Generate a handle to replace the frame's handle endif //that was created in the game(
- Solution:
Last edited:

