• 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.
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!
  • ✅ The POLL for Hive's Texturing Contest #34 is OPEN! Vote for the TOP 3 SKINS! 🔗Click here to cast your vote!
  • ✅ The POLL for Hive's Techtree Contest #20 is OPEN! Vote for the TOP 3 FACTIONS! 🔗Click here to cast your vote!

Fire Exit in case of 1.31 problems

Status
Not open for further replies.
I don't know where exactly to post it to help ppl who might experience the same issue: but beware: the new WorldEdit reads older trigger comments as triggers, and if you happen to use the same name for the comment as for the trigger itself, it reads the entry multiple times.
I then deleted the comments and suddenly got compile errors: the editor deleted the gg_TriggerName (for the comment!) and my trigger somehow was undeclared. No matter what I did to the trigger, the result was the same.
I copy-pasted all lines from that one to a freshly created trigger and deleted the original one to resolve the issue.

Update 1: also, enabling/disabling random seed in cinematic mode now messes up so many things...
Avoid these (or their variants):
set bj_cineModeSavedSeed=GetRandomInt(0,1000000)
call EnableUserUI(true)

Update 2: It works, just be more careful with your actions' order. Old WE tolerated some inconsistencies, but the latest version is more strict about the execution order.

Update 3: Using "channel" for all your custom made spells is even more important now. Check all your loose old spells which you carelessly created via regular spell modification, or be surprised that your custom target area spell (based off flamestrike) kills units in the area, even when the associated buffs and orders have been replaced.
 
Last edited:
I don't know where exactly to post it to help ppl who might experience the same issue: but beware: the new WorldEdit reads older trigger comments as triggers, and if you happen to use the same name for the comment as for the trigger itself, it reads the entry multiple times.
I then deleted the comments and suddenly got compile errors: the editor deleted the gg_TriggerName (for the comment!) and my trigger somehow was undeclared. No matter what I did to the trigger, the result was the same.
I copy-pasted all lines from that one to a freshly created trigger and deleted the original one to resolve the issue.

Update 1: also, enabling/disabling random seed in cinematic mode now messes up so many things...
Avoid these (or their variants):
set bj_cineModeSavedSeed=GetRandomInt(0,1000000)
call EnableUserUI(true)

Update 2: It works, just be more careful with your actions' order. Old WE tolerated some inconsistencies, but the latest version is more strict about the execution order.

Update 3: Using "channel" for all your custom made spells is even more important now. Check all your loose old spells which you carelessly created via regular spell modification, or be surprised that your custom target area spell (based off flamestrike) kills units in the area, even when the associated buffs and orders have been replaced.

Welp I guess I have to be careful on the altered melee map I'm making, thankfully I don't have much trigger comments yet. Thanks!
 
Status
Not open for further replies.
Back
Top