xe0.9

[Vexorian]

this be update.

[Bobo_The_Kodo]

Umm, the sheep staff bugged up, and all the units got chain lightninged over and over for a long time afterwards

Replay attached

[Vexorian]

It is not really a bug I just forgot to remove the sandbox trigger it seems.

So, just disable the sandbox trigger, I may find time to do a quick fix update of the map without incrementing the version number, but I don't see much point in that.

[zen87]

just wondering, can we use the internal dummy allocation in xe? i missed GetACaster() and hopefully you can put that in xe too :)

*what i see for now the dummy allocation is bulk of textmacro and have no idea on how to use it -__-

[Vexorian]

Don't ever use the textmacros.

Right now the idea is to use xebasic's constant and create unit, I might add a GetACaster equivalent to xecast, but I am not sure about it, perhaps another module?

[zen87]

sure thing :) I just don't want to use multiple dummy recycling system when we can just group them into one >.<

it could be a dummy recycling module where xecast requires that dummy recycling module? well just suggesting, because lots of system out there have their own dummy recycling in their system and I don't want my handle count fly sky high...

[Vexorian]

Creating and removing dummies shouldn't increase the handle count.

[zen87]

Originally Posted by Vexorian

Creating and removing dummies shouldn't increase the handle count.

well... recycling does.... since dummies doesn't removed and stays for later use. Multiple dummy recycling in one map -> many dummies not removed -> handle counts fly

[zen87]

a little suggestion in xedamage:

JASS:

        // method .useSpecialEffect("effect\\path.mdl", "origin")
        // Makes it add (and destroy) an effect when damage is performed.
        //
        method useSpecialEffect takes string path, string attach returns nothing
            set this.usefx = true
            set this.fxpath=path
            set this.fxattach=attach
        endmethod

to

JASS:

        // method .useSpecialEffect("effect\\path.mdl", "origin")
        // Makes it add (and destroy) an effect when damage is performed.
        //
        method useSpecialEffect takes string path, string attach returns nothing
            if path!="" and path!=null then
                set this.usefx = true
                set this.fxpath=path
                set this.fxattach=attach
            else
                set this.usefx = false
            endif
        endmethod

well... because i globalized my xedamage to deal spell damage, so that i just call spell_dmg.damageTarget or spell_dmg.damageAOE when needed...

but sometimes i'll like to add some eyecandy when dealing the damage without affecting the global xedamage spell_dmg...

mainly because i'm trying to do this...

JASS:

    call spell_dmg.useSpecialEffect("some_effect","chest") //set the damage effect
    call spell_dmg.damageAOE( ... do aoe dmg ... )
    call spell_dmg.useSpecialEffect(null,null) //reset the damage effect, spell_dmg can be used for other spell damage now

urghhh... can get what i mean...?

[Vexorian]

you could just use two xedamage instances, that was the point of it.

[zen87]

hmmm, how about duplication?

JASS:

 local xedamage fire = DuplicateXEDamage(spell_dmg)
     //where spell_dmg is a global constant I made earlier

 //or maybe
 local xedamage ice = spell_dmg.duplicate() //returns a whole new duplicated instance

make life easier

[WNxCryptic]

If you're trying to duplicate a pre-existing damage, why not call the damage that already exists?

[zen87]

Originally Posted by WNxCryptic

If you're trying to duplicate a pre-existing damage, why not call the damage that already exists?

because the effect change is one side connection... you can set the effect, but once set you can't turn it off

btw vex, some tiny suggestion again:

JASS:

    method castInPoint takes real x, real y returns boolean
     local unit dummy
     local boolean b
        //! runtextmacro xecast_allocdummy()
        if (.customsource) then
            call SetUnitFlyHeight(dummy,.sourcez,0.0)
        endif
        call SetUnitX(dummy, x)
        call SetUnitY(dummy, y)
        set b = IssueImmediateOrderById(dummy,this.oid)
        //! runtextmacro xecast_deallocdummy()
        if(.autodestroy ) then
            call this.destroy()
        endif
     return b
    endmethod

sometimes we need to detect is the spell successfully casted, thus i was thinking of returning the order boolean would be a nice idea :)

[Fire-Dragon-DoL]

Is possible to use caster system toghther with xe? (i don't need it actually, but there are some nice functions in caster system which are not still implemented in xe)

Btw, xe is great...very well done, really!

[Vexorian]

yes, you can share the unit id and no function names overlap,