[Solved] Trigger disabled: Expected a code statement

Status
Not open for further replies.

Pharos

P

Pharos

<ISSUE RESOLVED>
I don't usually post here, so if I can make my post any neater, tips would help in the future, but on to the situation:

I'm attempting to create a spell (an AoE freeze based off entangling roots) and there seems to be a problem with my custom scripts which remove memory leaks.

Here's what I have.
  • Frozen Paradise
    • Events
      • Unit - A unit Starts the effect of an ability
    • Conditions
      • (Ability being cast) Equal to Frozen Paradise
    • Actions
      • Set FPCaster = (Triggering unit)
      • Set FPCasterPoint = (Target point of ability being cast)
      • Set FPTargetGroup = (Units within 500.00 of FPCasterPoint matching ((((Matching unit) belongs to an enemy of (Triggering player)) Equal to True) and (((Triggering unit) is A structure) Equal to False)))
      • Custom script: Call RemoveLocation(udg_FPCasterPoint)
      • Unit Group - Pick every unit in FPTargetGroup and do (Actions)
        • Loop - Actions
          • Set FPTargetPoint = (Position of (Picked unit))
          • Unit - Create 1 FROZEN PARADISE DUMMY for (Triggering player) at FPTargetPoint facing Default building facing degrees
          • Unit - Add a 1.00 second Generic expiration timer to (Last created unit)
          • Unit - Add Frozen Paradise (DUMMY EFFECT LEVEL CHANGEABLE) to (Last created unit)
          • Unit - Set level of Frozen Paradise (DUMMY EFFECT LEVEL CHANGEABLE) for (Last created unit) to (Level of Frozen Paradise for FPCaster)
          • Unit - Order (Last created unit) to Night Elf Keeper Of The Grove - Entangling Roots (Picked unit)
          • Custom script: Call RemoveLocation(udg_FPTargetPoint)
      • Custom script: Call DestroyGroup(udg_FPTargetGroup)

So when I try to "Enable Trigger", the editor tells me that on each line where the custom scripts are, "Expected a Code Statement"

How can I get my trigger functioning?
 
Last edited by a moderator:
Fixed that part of the trigger now, though there still seems to be the issue of the trigger not enabling.
 
Huh, so it was just an error caused by capitalization.. How silly of me. Your assistance is much appreciated, I will edit OP to fixed now.
 
Status
Not open for further replies.
Back
Top