I'm also curious to give it a try, but I wonder, did you improve the points mentioned by Mozared in all the previous maps? I also feel I need a good challenge for any map to be interesting (I'm master league in melee), will the maps just feel way too easy? Sometimes, even when the main objectives are relatively easy, secondary objectives or achievements can be made hard as hell... :)
What if you create the actors by catching an actor event Behavior.FooBar.on You can then apply the behavior by triggers and choose which player is the behavior's owner. From that, the actor filters should work.
We don't have all the information to know what's going on, but here's my two cents.
If your ability is transient or without any casting/channeling/finish time, it will be done instantly and the unit will immediately start doing something else. So even if you tell it to play animation X, it might attack the next tick and then switch to playing the attack animation. Catching the abil.foo.SourceCastStart event is all good, but try making the casting or finish time non-zero.
The fixed point arithmetic uses 12 bits after the radix point, not 13, for a resulting accuracy of 1/4096.
This is required by the fact that healers/repairs and such are applied 16 times a second and we need to keep track of cost and time accurately, without the end results getting off due to rounding every game tick.
A maximum of 524288 HP is far beyond anything SC2 will ever need. Personally, I think it's just stupid to have units deal 3000 damage per hit and having 500000 life anyway.
Even when one uses a region with positive/negative areas, what the engine actually does is trying up to 32 times to find a point that isn't included in any negative area. After 32 tries, it returns null (No Point).
Rather than looping indefinitely, you could try up to X times and if it fails, wait a short moment before trying again.
Really, removing a dead unit doesn't instantly remove the "dead" actor? Strange, I'm surprised...
What about this : in the actor's events, register a new event so that when it receives a signal X (name it whatever you want), it calls SetVisible 0. From trigger code, send that signal to the unit's actor.
Edit: Actually, where does this crater come from? Is it really the unit's main actor, or is it a new actor created when the unit dies? (UnitDeath event, Create actor Y)
Oh. Then separate the buff into two buffs : one with effects that never expire, the other with a duration. You only disable the one with effects when appropriate. When the duration buff expires, you run an effect that removes the other buff.
Ah yes, a search for the unit being built should work... The only glitch is that if two units start building at the same time, the searches may mix up the two targets.
Since the actor system doesn't seem able to link builder and unit built, I'll give this a try and see how it works out. Thanks!
Add a validator to the lesser buff's "Disable" array, so that the presence of the better behavior disables the other. A disabled behavior isn't removed, it's just inactive and its effects will resume when the behavior is enabled again.
PointGetHight() is relative to terrain, and WorldHeight() gives you the terrain height at the specified 2d point. The sum of both should give you the absolute height.
Though, I could be wrong but as far as I know, all the actor messages to set an actor's height don't seem to work. For static heights, Site Operation actors can be used instead...
Hi,
I would have added these few icons to an existing "icon collection" thread, but the original authors of the threads haven't logged in since >6 months to update the first post ( and what's the deal with the thread "Skill/Spell/Ability Icons" being sticky when the author hasn't been seen in 15 months? ).
Icons are free to use, they come from my old Flagship Battle map and the new one not yet published. There's no need to give credits if you use them (if you really want to, I guess you can credit "Stragus" or "Alexis Naveros").
Have fun!
That's a lot of doodads. If you are going to cover the world with hexagons, I would either :
- Use a bigger "grid" models that contain a lot of hexagon tiles.
- Or use textures, modified ones, with visible hexagon edges painted on them.
0
Eh 7th mission already, nice.
I'm also curious to give it a try, but I wonder, did you improve the points mentioned by Mozared in all the previous maps? I also feel I need a good challenge for any map to be interesting (I'm master league in melee), will the maps just feel way too easy? Sometimes, even when the main objectives are relatively easy, secondary objectives or achievements can be made hard as hell... :)
0
What if you create the actors by catching an actor event Behavior.FooBar.on You can then apply the behavior by triggers and choose which player is the behavior's owner. From that, the actor filters should work.
0
We don't have all the information to know what's going on, but here's my two cents.
If your ability is transient or without any casting/channeling/finish time, it will be done instantly and the unit will immediately start doing something else. So even if you tell it to play animation X, it might attack the next tick and then switch to playing the attack animation. Catching the abil.foo.SourceCastStart event is all good, but try making the casting or finish time non-zero.
0
The fixed point arithmetic uses 12 bits after the radix point, not 13, for a resulting accuracy of 1/4096.
This is required by the fact that healers/repairs and such are applied 16 times a second and we need to keep track of cost and time accurately, without the end results getting off due to rounding every game tick.
A maximum of 524288 HP is far beyond anything SC2 will ever need. Personally, I think it's just stupid to have units deal 3000 damage per hit and having 500000 life anyway.
0
For the record... It's not very convenient working from images to see what's going on, next time you could try "Copy as text" and pasting.
0
You may just have to loop through.
Even when one uses a region with positive/negative areas, what the engine actually does is trying up to 32 times to find a point that isn't included in any negative area. After 32 tries, it returns null (No Point).
Rather than looping indefinitely, you could try up to X times and if it fails, wait a short moment before trying again.
0
Really, removing a dead unit doesn't instantly remove the "dead" actor? Strange, I'm surprised...
What about this : in the actor's events, register a new event so that when it receives a signal X (name it whatever you want), it calls SetVisible 0. From trigger code, send that signal to the unit's actor.
Edit: Actually, where does this crater come from? Is it really the unit's main actor, or is it a new actor created when the unit dies? (UnitDeath event, Create actor Y)
0
Icons are 76x76, wireframes are 140x140
0
Oh. Then separate the buff into two buffs : one with effects that never expire, the other with a duration. You only disable the one with effects when appropriate. When the duration buff expires, you run an effect that removes the other buff.
0
Ah yes, a search for the unit being built should work... The only glitch is that if two units start building at the same time, the searches may mix up the two targets.
Since the actor system doesn't seem able to link builder and unit built, I'll give this a try and see how it works out. Thanks!
0
Add a validator to the lesser buff's "Disable" array, so that the presence of the better behavior disables the other. A disabled behavior isn't removed, it's just inactive and its effects will resume when the behavior is enabled again.
0
In triggers, "Remove unit".
0
PointGetHight() is relative to terrain, and WorldHeight() gives you the terrain height at the specified 2d point. The sum of both should give you the absolute height.
Though, I could be wrong but as far as I know, all the actor messages to set an actor's height don't seem to work. For static heights, Site Operation actors can be used instead...
0
DDS file here
DDS file here
DDS file here
DDS file here
DDS file here
DDS file here
DDS file here
DDS file here
DDS file here
0
That's a lot of doodads. If you are going to cover the world with hexagons, I would either :
- Use a bigger "grid" models that contain a lot of hexagon tiles.
- Or use textures, modified ones, with visible hexagon edges painted on them.