• 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.

spell not works

Status
Not open for further replies.
Level 28
Joined
Jan 26, 2007
Messages
4,789
If the spell was approved, it means that there's nothing wrong with it.
There isn't anything that could cause an error in that spell, there's an error when you imported it (which means you did something wrong).

You could give us a screenshot of what JassHelper is saying, that would greatly help us, it actually has a pretty good debug screen compared to other programs :D
But saying it's the spell is incorrect and that it wasn't you who did something wrong is a bit... I'll be careful with my words, but a bit conceited maybe?
 
Level 28
Joined
Jan 26, 2007
Messages
4,789
Oh, I thought you had an older version because that thread says
New JassHelper said:
New versions are intended to be absolutely backwards compatible with JassHelper 0.A.2.B
Which means they lied to us.

You can see that the debugger highlights the line private function InitTrig takes nothing returns nothing.
It also says "Change function name and use the initializer command".
Did you even try following those instructions?

Well, anyway. Here's what you need to do:
Change the line above to private function Init takes nothing returns nothing
(Now you've renamed the function from "InitTrig" to "Init").
Then scroll all the way to the top of that trigger and change the library-line to library Fear initializer Init requires PlayerChanger
And you're done.

(Do this for all triggers).

I hope you will learn to trust and follow the debugger more in the future :p
 
Status
Not open for further replies.
Top