Is there any way for a variation to be selected only ONCE, without having to create my own variation system. For example: every time my actor unit is revived he/she gets a new model. Well to me, this looks really lame since you might have died as a female and were revived as male.
Right, I understand that. But perhaps you understand it better than I, do you know of any way I can prevent that? All I really see is a default unit event which sets a new reference for the actor when the unit is revived. However, I don't actually see where the unit is created (or destroyed, upon death, for that matter) when a unit is revived. Maybe I'm just overlooking it, but it feels like I'm missing something since it makes no sense to me.
Check the events for Orphan and Unit Death that uses a Destroy event action.
The events top 5 (No. 4) the Unit Revive event.
Seems Unit actor destruction is now linked to the unit, was not like that in the past. Use a Model type actor as an avatar that is not destroyed buy just hidden on death.
Rollback Post to RevisionRollBack
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
Check the events for Orphan and Unit Death that uses a Destroy event action.
The events top 5 (No. 4) the Unit Revive event.
Thanks a lot for helping! However, I'm still a bit confused. I'm going to ask a lot of questions, so I'll take this opportunity to apologize in advance. :D
I looked for events with Orphan and Unit Death, however I did not find any inside the unit events+, or should I be looking in a different actor? I see the Unit Revive event, it is setting the Reference System: "Host Turret Body" to the Alias "_Selectable". That makes sense, but I don't see how the unit is being destroyed upon death? Did you mean I need to look for this "Host Turret Body" actor and find the event that is destroying it? I can't seem to find the actor it is referencing there.
Seems Unit actor destruction is now linked to the unit, was not like that in the past. Use a Model type actor as an avatar that is not destroyed buy just hidden on death.
What do you mean by: "linked to the unit?", does that mean the actor is destroyed internally without requiring an event to do so? So I would need to use a model type actor that is not destroyed but just hidden on death, interesting. If that's true then it shouldn't be too hard to fix this problem.
Hmm, upon making that actor how do you propose I should link it to the unit actor? I would imagine just creating the model actor when the unit is created and setting up a reference for it would suffice. However, I'm not sure that it would be the best way to do it.
Use a global reference and a reference set event action to set the hosting to the unit again on revive.
I've never used a global reference before, but I'll give it a shot. Although that would pose a problem: wouldn't I need a global reference for each unit that I want to keep the same model variation? If so, then I'm not sure this will be practical enough to work.
Yeah I see that, that kind of defeats the purpose of even using the default system for me personally. I think I'm going to just use behaviors that apply a variation and then validate the unit to determine which model to swap out for. It sounds like the same amount of work and I get the added benefit of being able to determine which variation I'm using through a validator.
Thanks for all of your help though, I learned a lot!
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Is there any way for a variation to be selected only ONCE, without having to create my own variation system. For example: every time my actor unit is revived he/she gets a new model. Well to me, this looks really lame since you might have died as a female and were revived as male.
If the old actor is destroyed and created again it will have a chance to be different.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
@DrSuperEvil: Go
Right, I understand that. But perhaps you understand it better than I, do you know of any way I can prevent that? All I really see is a default unit event which sets a new reference for the actor when the unit is revived. However, I don't actually see where the unit is created (or destroyed, upon death, for that matter) when a unit is revived. Maybe I'm just overlooking it, but it feels like I'm missing something since it makes no sense to me.
Any hints? :D
Thanks for the response!
Check the events for Orphan and Unit Death that uses a Destroy event action.
The events top 5 (No. 4) the Unit Revive event.
Seems Unit actor destruction is now linked to the unit, was not like that in the past. Use a Model type actor as an avatar that is not destroyed buy just hidden on death.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
Thanks a lot for helping! However, I'm still a bit confused. I'm going to ask a lot of questions, so I'll take this opportunity to apologize in advance. :D
I looked for events with Orphan and Unit Death, however I did not find any inside the unit events+, or should I be looking in a different actor? I see the Unit Revive event, it is setting the Reference System: "Host Turret Body" to the Alias "_Selectable". That makes sense, but I don't see how the unit is being destroyed upon death? Did you mean I need to look for this "Host Turret Body" actor and find the event that is destroying it? I can't seem to find the actor it is referencing there.
What do you mean by: "linked to the unit?", does that mean the actor is destroyed internally without requiring an event to do so? So I would need to use a model type actor that is not destroyed but just hidden on death, interesting. If that's true then it shouldn't be too hard to fix this problem.
Hmm, upon making that actor how do you propose I should link it to the unit actor? I would imagine just creating the model actor when the unit is created and setting up a reference for it would suffice. However, I'm not sure that it would be the best way to do it.
Again, thanks so much for all your help!
Sorry, one above that.
When the unit dies the actor automatically orphans and destroys itself.
Use a global reference and a reference set event action to set the hosting to the unit again on revive.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
@DrSuperEvil: Go
Ahh I see, that's what I figured. Although, that's kind of lame, I wish that wasn't the case.
I've never used a global reference before, but I'll give it a shot. Although that would pose a problem: wouldn't I need a global reference for each unit that I want to keep the same model variation? If so, then I'm not sure this will be practical enough to work.
Thanks again for the help!
If it is every unit that would get tough.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
Yeah I see that, that kind of defeats the purpose of even using the default system for me personally. I think I'm going to just use behaviors that apply a variation and then validate the unit to determine which model to swap out for. It sounds like the same amount of work and I get the added benefit of being able to determine which variation I'm using through a validator.
Thanks for all of your help though, I learned a lot!