Jump to content

Photo

Damaging Sparkle Sprite Trail for the Sword beam... possible?

LWeapon Script 2.55

  • Please log in to reply
19 replies to this topic

#16 Bagu

Bagu

    Fandomizer

  • Members
  • Real Name:A.I. Bot Bottomheimer
  • Location:Germany

Posted 18 July 2020 - 12:32 PM

Figured it out, works very fine
(had to change the 'const int DAMAGETRAILDEFAULTCLK' from 30 to 6, because the distance between the spawned sparkle sprites was to far.

Now, it looks great!!!

Thanks so much,Zoria and Rob

You're great



#17 Emily

Emily

    Scripter / Dev

  • ZC Developers

Posted 18 July 2020 - 12:33 PM

No, don't change the DEFAULT clk! Leave that how it was. Put 6 is InitD[0] for the script, instead!


  • Bagu likes this

#18 Bagu

Bagu

    Fandomizer

  • Members
  • Real Name:A.I. Bot Bottomheimer
  • Location:Germany

Posted 18 July 2020 - 12:39 PM

Oh, ok
....yeah, I forgot that's variable by D0



#19 Bagu

Bagu

    Fandomizer

  • Members
  • Real Name:A.I. Bot Bottomheimer
  • Location:Germany

Posted 18 July 2020 - 08:03 PM

THANKS, ONCE MORE!!!
...just wanted to show you the result.

I used the script for my 3 golden Swords (Mastersword "transformations" by the Triforce powers).
These sacred blades call the force of the elemental Phoenix.
Heavenly Phoenix (Farore's Sword), Infernal Phoenix (Din's Sword) and The Phoenix of Light (Nayru's Sword)


uHwPcio.png

QwDSwtZ.png

CLuCRm6.png


  • Lüt likes this

#20 Timelord

Timelord

    The Timelord

  • Banned
  • Location:Prydon Academy

Posted 23 July 2020 - 05:36 AM

uhg, zoria....

Remove the 'this->Parent = this;' line. That's.... just completely wrong, and not something you can do.

 

The intent is that the new weapon's parent is the weapon that spawned it, for the purpose of future linking back to it.

 

e.g. this->X = this->Parent->X + x2.

 

LWPNPARENT is only set up to accept FLOAT, which happens to be dead wrong--I wrote it to accept only an item ID, but this is an edge case where an lweapon has another lweapon as its parent. It should be untyped. The script does not require this, but if you want to modify it in a running script based on its parent's properties, then that's a useful coordinate.

 

It may have consequences that I did not foresee, if it was legal, such as inheriting properties from the parent that are unwanted, but iit does need to be untyped. All ->Parent variables need to be untyped for this very reason, as some may lead back to npc, item, or *weapon. Even so, the user can override them, and I need to correct this. I do see possible clashes with the item ID for ParentItem, rather than ParentID, which I will admit is a general failing point of lweapons in general.


THANKS, ONCE MORE!!!
...just wanted to show you the result.

I used the script for my 3 golden Swords (Mastersword "transformations" by the Triforce powers).
These sacred blades call the force of the elemental Phoenix.
Heavenly Phoenix (Farore's Sword), Infernal Phoenix (Din's Sword) and The Phoenix of Light (Nayru's Sword)


uHwPcio.png

QwDSwtZ.png

CLuCRm6.png

 

Very nice. Glad to have been of help. My apologies for the blunders: I tend to forget what I have actually implemented at times. I've added thousands of new instructions, and at the end of the day, they occasionally blur together.


  • Bagu likes this



Also tagged with one or more of these keywords: LWeapon Script, 2.55

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users