Creating an item when a tree dies

[ThE-eNiGmA]

I was fiddling around in the editor, and one of the requirements of my map is that when you cut a tree down, a bundle of wood is dropped. Problem is, there doesn't seem to be a generic "destructible dies" event. Why is this a problem? I can't detect when a tree dies so I can drop the wood, and I don't feel like grouping all the trees in little regions. I am trying to keep the code as streamlined as possible. Any ideas?

 

[Starlite]

uhm... why do you need that when you can do conditions

Tree
    Events
        Unit - A unit Dies
    Conditions
        (Destructible-type of (Last created destructible)) Equal to Summer Tree Wall
    Actions
        Item - Create <your item> at (Position of(Dying unit))

 

[ThE-eNiGmA]

i tried that. didnt work.

 

[Starlite]

hmm..... dunno then....
unless you make your trees units...
because you cant use destrictable-type or destrictible variables...

 

[ThE-eNiGmA]

making the trees units...would probably create all new problems. Now... i just thought of a clever workaround. What I do is allow the tree to be cut down, and the peasant can ferry it back to base. Every time he does, an item is created (a trigger detects wood coming in, and subtracts the wood and creatss a bundle of wood.)

 

[HoboJoe_5]

there is an event destructible dies dude
woops nevermind you want generic like not specific destructible dies nm

 

[Heptameron]

That limit of 64 destructibles is completely arbitrary... it's only there because Warcraft has to go through every single destructible... you can use this custom script in your initialization trigger if you want to do it anyway and don't create any destructibles afterwards.

Custom script:   set bj_destInRegionDiesTrig = gg_trg_[i]<your trigger name>[/i]
Custom script:   set bj_destInRegionDiesCount = -100000
Custom script:   call EnumDestructablesInRect(GetWorldBounds(), null, function RegisterDestDeathInRegionEnum)

(Note that your trigger name must uses underscores "_" instead of spaces.)

 

[pladams9]

Could you explain what those custom scripts do? Specifically I mean? I'd like to understand it for possible future use.

 

[Heptameron]

Could you explain what those custom scripts do? Specifically I mean? I'd like to understand it for possible future use.

Ah, okay. All right, well, when you use the regular "Destructible in region dies" trigger, Warcraft calls this function:

function TriggerRegisterDestDeathInRegionEvent takes trigger trig, rect r returns event
    set bj_destInRegionDiesTrig = trig
    set bj_destInRegionDiesCount = 0
    call EnumDestructablesInRect(r, null, function RegisterDestDeathInRegionEnum)
    return trig
endfunction

Which uses this function:

function RegisterDestDeathInRegionEnum takes nothing returns nothing
    set bj_destInRegionDiesCount = bj_destInRegionDiesCount + 1
    if (bj_destInRegionDiesCount <= bj_MAX_DEST_IN_REGION_EVENTS) then
        call TriggerRegisterDeathEvent(bj_destInRegionDiesTrig, GetEnumDestructable())
    endif
endfunction

The general thing it does is:

1. Set global variable A to the trigger we want to add these events to.
2. Set global variable B to 0, since we haven't added any events yet.
3. Run the RegisterDestDeathInRegionEnum function for every destructible in the region (like the "pick every destructible in region" actions in the Destructible category).

The RegisterDestDeathInRegionEnum function does this:

1. Add one to global variable B.
2. If B is less than or equal to 64, add the event for this destructible.

All my custom script does is emulate the first function... except instead of setting global variable B to 0, it sets it to a huge negative number... so it will take an extremely long time for it to ever exceed 64.

If you wanted to avoid this, you could just add "pick every destructible in region" action to your initialization trigger, and just add this custom script to it:

Custom script:   call TriggerRegisterDeathEvent(gg_trg_[i]<your trigger name>[/i], GetEnumDestructable())

 

[Red Beard]

Hehe.

You DID ask

 

[pladams9]

LOL, yes I did. OK, well it makes sense. Although, before he explained it I thought it was something else. I didn't realize that the problem was the 64 limit. I didn't even know that existed.

 

[Noobster]

I'sn't it possible to make trees drop items? Just click a tree twice, go to the items dropped tab, and Voila!

 

[Rad]

I'sn't it possible to make trees drop items? Just click a tree twice, go to the items dropped tab, and Voila!

Genious!

+Rep you beat custom script Lol

 

[Heptameron]

I'sn't it possible to make trees drop items? Just click a tree twice, go to the items dropped tab, and Voila!

For every single tree on the map?

 

[Starlite]

or if thats your only doodad drag over all of them, then double click on one.

 

[Heptameron]

or if thats your only doodad drag over all of them, then double click on one.

That is the equivalent of creating one trigger for every tree.

Not a good idea, really.

 

[Starlite]

no because then you just drag over all your trees and double click on one, change the field you want hit ok. then all of them have that same property

 

[Heptameron]

no because then you just drag over all your trees and double click on one, change the field you want hit ok. then all of them have that same property

Look at the Jass script that makes.

 

[Starlite]

how would i do that?
hey while your at it! whats a sticky thread?

ohhh dear... 31 points of rep in like 5 or 6 days... wow thats nuts...

 

[Heptameron]

how would i do that?

Terrain Editor, File > Export Script.

hey while your at it! whats a sticky thread?

Any of the threads at the top of this forum labeled Please Read: