Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ON=@Destroy for Chars Buggy?
Author Message
admin phoenix
Master
**

Posts: 354
Likes Given: 1
Likes Received: 23 in 13 posts
Joined: Mar 2012
Reputation: 3



Post: #1
ON=@Destroy for Chars Buggy?
Hi Folks,

haven´t the script here yet but the code is very simpel. I use it for my summon npcs and there are two problem. When I set the uid to the ref1 object it works but the trigger fires twice and in the second round I don´t have a uid so the console set me an error that it can´t find the ref1.tag0.summon.
I put this code to my e_allnpc event so that every npc got this event.


Code:
ON=@Destroy
IF (<flags>&statf_conjured)
      ref1=<findlayer(41).link>
      ref1.tag0.summon -=1
      ref1.smsg You summon creature has gone.
ENDIF

The fix around is

Code:
ON=@Destroy
IF (<flags>&statf_conjured)
  IF (<dvar0.summon_bug> == 1)
      local.uid=<findlayer(41).link>
      ref1=<local.uid>
      ref1.tag0.summon -=1
      ref1.smsg You summon creature has gone.
      var0.summon_bug=
   ELSE
      var0.summon_bug=1
ENDIF
ENDIF

Anyone can confirm this one?

gr

Phoenix

[Edit] I fixed it with another workaround with removing the memory item from the npc. This works now but it is also a bug.
(This post was last modified: 09-07-2012 12:03 AM by admin phoenix.)
08-24-2012 05:08 PM
Find all posts by this user Like Post Quote this message in a reply
Shaklaban
Master
**

Posts: 378
Likes Given: 0
Likes Received: 1 in 1 posts
Joined: Mar 2012
Reputation: 8

DOT

Post: #2
RE: ON=@Destroy for Chars Buggy?
hmm i don't understand first one, if you mean ref1 is not assigned you can use ref1=<owner>.
08-24-2012 05:33 PM
Visit this user's website Find all posts by this user Like Post Quote this message in a reply
Extreme
Grandmaster Poster
***

Posts: 1,140
Likes Given: 217
Likes Received: 89 in 76 posts
Joined: May 2012
Reputation: 20

SphereCommunity

Post: #3
RE: ON=@Destroy for Chars Buggy?
Yeah its bugged.
When I was scripting the Energy Vortex spell, when it disappear, it removes doubled followers.
Destroy is firing 2 times, very nice =D
I used a tag too to fix it.

STEPS BEFORE CREATE A THREAD
- Check the revisions log;
- Use the search button and use the keywords of your problem;
- Check the WIKI;
- Create a thread.
08-24-2012 10:07 PM
Find all posts by this user Like Post Quote this message in a reply
RanXerox
Master
**

Posts: 550
Likes Given: 1
Likes Received: 12 in 9 posts
Joined: Dec 2010
Reputation: 19



Post: #4
RE: ON=@Destroy for Chars Buggy?
Out of curiosity, log ARGN1 ARGN2 and ARGN3 and see if they somehow distinguish between the first and second execution of the trigger...
08-25-2012 05:27 AM
Find all posts by this user Like Post Quote this message in a reply
admin phoenix
Master
**

Posts: 354
Likes Given: 1
Likes Received: 23 in 13 posts
Joined: Mar 2012
Reputation: 3



Post: #5
RE: ON=@Destroy for Chars Buggy?
because Ben can´t produce this error and closed my bug report in the tracker, I push this thread up.
09-07-2012 12:03 AM
Find all posts by this user Like Post Quote this message in a reply
darksun84
Sir Spamalot
****

Posts: 1,687
Likes Given: 246
Likes Received: 162 in 151 posts
Joined: Mar 2012
Reputation: 35



Post: #6
RE: ON=@Destroy for Chars Buggy?
After some test, i noticed that it's not a problem of the @Destroy trigger

If we change the TYPE (t_spell) of the item inside layer 41 to another type, the trigger it's fired only one time!

So the bug it's related to summoning creature by magic spells i think.

Adding the trigger to a npc summoned by addnpc, and applying the flag conjured, the trigger it' till fired one timen(because it doesn't have the item on layer 41).

Other thing, if we remove the item on layer 41, the summoned (by magic) creature disappear, but the trigger it's fired only one time !

Same thing if we delete the creature with command .remove

The bug appear then when the creature is killed by .kill or by damage
(This post was last modified: 09-07-2012 04:13 AM by darksun84.)
09-07-2012 03:53 AM
Find all posts by this user Like Post Quote this message in a reply
Ben
Sphere Developer
*****

Posts: 612
Likes Given: 2
Likes Received: 123 in 70 posts
Joined: Mar 2010
Reputation: 18

SphereCommunity

Post: #7
RE: ON=@Destroy for Chars Buggy?
is this atleast with the latest build?

AxisII's current version: 2.0.4j
AxisII SourceCode on Github
AxisII up to date changelog
09-11-2012 01:07 PM
Visit this user's website Find all posts by this user Like Post Quote this message in a reply
darksun84
Sir Spamalot
****

Posts: 1,687
Likes Given: 246
Likes Received: 162 in 151 posts
Joined: Mar 2012
Reputation: 35



Post: #8
RE: ON=@Destroy for Chars Buggy?
yes!

WL_test.scp,26)Air Elemental 1516,1630,-13 01fc8
03:34:(WL_test,27)0
03:34:(WL_test.scp,26)Air Elemental 1516,1630,-13 01fc8
03:34:(WL_test.scp,27)0
09-12-2012 11:35 AM
Find all posts by this user Like Post Quote this message in a reply
Ben
Sphere Developer
*****

Posts: 612
Likes Given: 2
Likes Received: 123 in 70 posts
Joined: Mar 2010
Reputation: 18

SphereCommunity

Post: #9
RE: ON=@Destroy for Chars Buggy?
Problem found, problem confirmed! Error occures when the char is destroyed before the spell is over... the memory object is then destroyed and calls to destroy the char again as if it got dispelled Smile Not sure yet how to prevent it, but I'm working on it!

AxisII's current version: 2.0.4j
AxisII SourceCode on Github
AxisII up to date changelog
09-16-2012 12:29 AM
Visit this user's website Find all posts by this user Like Post Quote this message in a reply
Ben
Sphere Developer
*****

Posts: 612
Likes Given: 2
Likes Received: 123 in 70 posts
Joined: Mar 2010
Reputation: 18

SphereCommunity

Post: #10
RE: ON=@Destroy for Chars Buggy?
Should be fixed in build 1534

AxisII's current version: 2.0.4j
AxisII SourceCode on Github
AxisII up to date changelog
09-17-2012 02:06 AM
Visit this user's website Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)