You can't have variable values such as you're describing in Data. Your best best would be a switch system using different levels of shield strength. Otherwise triggers would be necessary.
You can use lots of lesser attacks to trigger the modify limit. I'm not sure whether it will keep triggering if you uncheck the flag you mentioned. Will test.
A good tutorial although I have two thoughts on it.
First, bluntly put, it's a nice giant wall of text with a scattering of bolded words that is slightly less than appealing to look at, let alone read. It would be better if you separated it into a specific component for each data object with sub-components for each field you change.
Second, I feel like the tutorial would be effective if you explained how to create the auto-harvesting behaviour from scratch instead of just duplicating a few values. Your method doesn't explain why it works and anyone can just write a text saying duplicate this, this, and this then tweak some numbers. People don't learn by being handed a calculator and a near-finished equation and being told to solve it, they learn by taking the raw problem then working it through step by step.
I would just use an Effect - Instant ability in this case. The ability would use an Issue Order effect to force the unloading of a unit and the Transport ability would order the civilian to morph the moment it's unloaded.
Make your ability add a Buff behaviour to the target which stuns and also has the Combat - Damage Response - Modify Fraction field set to 0 and the Combat - Damage Response - Modify Limit field set to however much damage you want the shell to absorb before dying. The first field modifies the amount of damage the unit takes to 0% and the second is the life of the shell. For stopping the attack if it's a friendly unit you might be able to use an Issue Order effect in the Combat - Damage Response - Exhausted field which proper targeting.
Modify the Beam so that it is created between the Search Area effect and the caster. By the looks of it the beam is currently being created as a result of the Damage effect which is how the Snipe is suppose to be and as a result it's being created for each unit found by the search.
You could give the Hydra Den a behaviour that periodically runs an effect that validates to see if either upgrade is researched and if so orders the Hydra Den to morph then removes the buff.
It sounds like your weapon isn't connected to the turret properly. Make sure the weapon has a turret on the unit object and make sure the turret has an actor.
Make the Behaviour run the persistent effect periodically, not the persistent run the issue order. The issue order can't find the target point, that's why it's not working. Just make it target the Target Point and leave the Effect: part blank.
I have HotS, the reason I can't view the map is because I do not have access to my computer.
0
You can't have variable values such as you're describing in Data. Your best best would be a switch system using different levels of shield strength. Otherwise triggers would be necessary.
0
@ArcaneDurandel: Go
You can use lots of lesser attacks to trigger the modify limit. I'm not sure whether it will keep triggering if you uncheck the flag you mentioned. Will test.
0
A good tutorial although I have two thoughts on it.
First, bluntly put, it's a nice giant wall of text with a scattering of bolded words that is slightly less than appealing to look at, let alone read. It would be better if you separated it into a specific component for each data object with sub-components for each field you change.
Second, I feel like the tutorial would be effective if you explained how to create the auto-harvesting behaviour from scratch instead of just duplicating a few values. Your method doesn't explain why it works and anyone can just write a text saying duplicate this, this, and this then tweak some numbers. People don't learn by being handed a calculator and a near-finished equation and being told to solve it, they learn by taking the raw problem then working it through step by step.
I hope you don't me being critical.
0
Use Requirements to hide the upgrade button once the upgrade has been queued or better.
0
I would just use an Effect - Instant ability in this case. The ability would use an Issue Order effect to force the unloading of a unit and the Transport ability would order the civilian to morph the moment it's unloaded.
0
Make your ability add a Buff behaviour to the target which stuns and also has the Combat - Damage Response - Modify Fraction field set to 0 and the Combat - Damage Response - Modify Limit field set to however much damage you want the shell to absorb before dying. The first field modifies the amount of damage the unit takes to 0% and the second is the life of the shell. For stopping the attack if it's a friendly unit you might be able to use an Issue Order effect in the Combat - Damage Response - Exhausted field which proper targeting.
0
Does each copy of the unit require a different model?
0
Modify the Beam so that it is created between the Search Area effect and the caster. By the looks of it the beam is currently being created as a result of the Damage effect which is how the Snipe is suppose to be and as a result it's being created for each unit found by the search.
0
Check the Cargo flag in the UI - Status Bar Flags of the unit's actor.
0
You could give the Hydra Den a behaviour that periodically runs an effect that validates to see if either upgrade is researched and if so orders the Hydra Den to morph then removes the buff.
0
You cannot create scaling values using pure data. You will have to use triggers as well.
0
@MaskedImposter: Go
Not really. You could give all the abilities to each unit then use buffs to enable certain ones.
@Commanderrr: Go
It's an interesting concept but I feel like the balancing issue would be the hardest part to it.
0
Both the colossus and the immortal are not turnable. In the unit flag field check enable the turnable flag though that will break how they move.
0
It sounds like your weapon isn't connected to the turret properly. Make sure the weapon has a turret on the unit object and make sure the turret has an actor.
0
Make the Behaviour run the persistent effect periodically, not the persistent run the issue order. The issue order can't find the target point, that's why it's not working. Just make it target the Target Point and leave the Effect: part blank.
I have HotS, the reason I can't view the map is because I do not have access to my computer.