Like it says, I wanna make an autocast ability in the zerg hive with a 90s cooldown. When enabled it reveals all enemy battlecruisers in map and shares their view. So far I've got the validator (will be battlecruisers and carriers) and used the preordain behavior from HotS but I got no idea wich type of ability or effects to do this. I though of a search effect (enum area) with a 500 radius that applies the "apply behavior" (preordain) to the units that fulfill the validator.
Rollback Post to RevisionRollBack
I like the lore. Check my latest projects at:
My Profile and My Team
You can also use a Persistent effect or a Buff if this should run automatically with no user input, or as a toggleable "aura". In that case put the Search in the Periodic Effect field of the Buff/Persistent.
I made your first suggestion because i wanna make it a single shot cooldowned ability from the hive. It uses a search effect with an apply behavior effect wich applies the reveal behavior to the units that fit with the search filters. That works and the units get the behavior, but they aren't revealed.. :(
I'm uploading the map in case you wanna check it out and find something. It has a couple of "cheat" triggers you should see them first.
This seems to be a problem with the Reveal behavior type. Aside from you having set the filter to Required: Heroic which should exclude all units on the map an entirely empty filter seems to remove the behavior immediately.
Judging by the button tooltip you don't just want to visually reveal the unit itself (which probably could be done via actors), but want to lift the fog of war on the unit and its surroundings.
The Oracle uses a Buff type behavior with the "Reveal" flag checked and a Persistent effect on the target unit to reveal a fixed AoE around it (Reveal Flag: Unfog, Reveal Radius>0)
The only way I know for truly sharing vision with a single unit is an Interact ability, which would require a much more complex setup: You'd have to give the ability to the target, then order it to use the ability on the caster, and issue a second order to cancel the ability when the effect is meant to expire. There's no Transient flag for this ability type, so either it's always on or this won't work at all with a fully functional unit.
Also your ability won't autocast, you'll have to set the Autocast Range to 500 too. You might have to set the Arc to 360 as well since the Hive can't turn.
Slightly off-topic: If you're making cheat triggers make sure you have an on-off toggle. Placing Observers is a simpler solution for localised map vision such as checking the buff, and can also be used for AI players if you don't want to give them a global maphack.
Hmm I just solved it thanks to you. Forget the heroic filter, in my map the unit is massive heroic and armored i forgot to change it. You're right, I changed the reveal behavior type to buff and in behavior tab>modify flags: there's a reveal and a share vision flags. I checked them both since I wanna see what the unit sees. No need for actors or anything else, I'll just make one actor dependent from the behavior to give it a visual effect. I also changed the autocast stuff you told me and it works great now.
Off topic, Sorry about the cheats, i just made them quickly to upload the map, plus the units in my map are detectors with huge range so observers would have to be invulnerable and well it's more time invested in that than the actual ability.
The comment about cheats and Observers was specifically aimed at making demo maps, I meant it less as a complaint and more as a heads up for next time. If you do use triggers I recommend sharing player vision over a map revealer if the AI is also meant to attack your cloaked units (combat tests etc)
If you have an actual, playable custom game mode it's almost always better to use triggers, with a bit of planning ahead you can add debug routines to gameplay-relevant triggers too.
Thanks for the heads up, I'm not really that good with triggers anyway, that's why I try to use more data even though it gives lag at some point. I've got no idea of how to debug..
Rollback Post to RevisionRollBack
I like the lore. Check my latest projects at:
My Profile and My Team
To post a comment, please login or register a new account.
Like it says, I wanna make an autocast ability in the zerg hive with a 90s cooldown. When enabled it reveals all enemy battlecruisers in map and shares their view. So far I've got the validator (will be battlecruisers and carriers) and used the preordain behavior from HotS but I got no idea wich type of ability or effects to do this. I though of a search effect (enum area) with a 500 radius that applies the "apply behavior" (preordain) to the units that fulfill the validator.
Ability: Effect-Instant->Search->Apply Behavior
You can also use a Persistent effect or a Buff if this should run automatically with no user input, or as a toggleable "aura". In that case put the Search in the Periodic Effect field of the Buff/Persistent.
@Photoloss: Go
I made your first suggestion because i wanna make it a single shot cooldowned ability from the hive. It uses a search effect with an apply behavior effect wich applies the reveal behavior to the units that fit with the search filters. That works and the units get the behavior, but they aren't revealed.. :(
I'm uploading the map in case you wanna check it out and find something. It has a couple of "cheat" triggers you should see them first.
This seems to be a problem with the Reveal behavior type. Aside from you having set the filter to Required: Heroic which should exclude all units on the map an entirely empty filter seems to remove the behavior immediately.
Judging by the button tooltip you don't just want to visually reveal the unit itself (which probably could be done via actors), but want to lift the fog of war on the unit and its surroundings.
The Oracle uses a Buff type behavior with the "Reveal" flag checked and a Persistent effect on the target unit to reveal a fixed AoE around it (Reveal Flag: Unfog, Reveal Radius>0)
The only way I know for truly sharing vision with a single unit is an Interact ability, which would require a much more complex setup: You'd have to give the ability to the target, then order it to use the ability on the caster, and issue a second order to cancel the ability when the effect is meant to expire. There's no Transient flag for this ability type, so either it's always on or this won't work at all with a fully functional unit.
Also your ability won't autocast, you'll have to set the Autocast Range to 500 too. You might have to set the Arc to 360 as well since the Hive can't turn.
Slightly off-topic: If you're making cheat triggers make sure you have an on-off toggle. Placing Observers is a simpler solution for localised map vision such as checking the buff, and can also be used for AI players if you don't want to give them a global maphack.
@Photoloss: Go
Hmm I just solved it thanks to you. Forget the heroic filter, in my map the unit is massive heroic and armored i forgot to change it. You're right, I changed the reveal behavior type to buff and in behavior tab>modify flags: there's a reveal and a share vision flags. I checked them both since I wanna see what the unit sees. No need for actors or anything else, I'll just make one actor dependent from the behavior to give it a visual effect. I also changed the autocast stuff you told me and it works great now.
Off topic, Sorry about the cheats, i just made them quickly to upload the map, plus the units in my map are detectors with huge range so observers would have to be invulnerable and well it's more time invested in that than the actual ability.
Woks like a charm.. I uploaded the map.
The comment about cheats and Observers was specifically aimed at making demo maps, I meant it less as a complaint and more as a heads up for next time. If you do use triggers I recommend sharing player vision over a map revealer if the AI is also meant to attack your cloaked units (combat tests etc)
If you have an actual, playable custom game mode it's almost always better to use triggers, with a bit of planning ahead you can add debug routines to gameplay-relevant triggers too.
@Photoloss: Go
Thanks for the heads up, I'm not really that good with triggers anyway, that's why I try to use more data even though it gives lag at some point. I've got no idea of how to debug..