Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
Next trigger exercise will come a few days after christmas. I love the progress I have seen in this thread and I hope there will be the same activity in the next exercise.
This is what I think is the biggest problem with the current system, together with the lack of sorting options. I would atleast be almost fully satisfied if they add a search box with the possibility to put in different search parameters and allow sorting of the game list after things such as time played, name and type.
"The battered marines took cover behind a broken down truck as countless enemy rifle rounds rained death above them. After having spent just a moment to regain their breath they looked towards their sergeant for further orders. The sergeant responded with a silent nod, something which filled the marines with dread, there was no hope and they were to make their last stand."
Weekly Trigger Exercise #2
This weeks trigger exercise is about creating a squad mechanic where the whole group of units behave as one entity. You can use any unit for the exercise from a classical marine squad to a swarm of scourge. While you can interpret the concept of a squad any way you wish I have listed a few possible features to help you get started.
The unit share any orders given.
The group goes into a specific shape whenever possible.
The whole unit shares a single health bar with units getting killed at specific intervals.
The squad fires at all units near a target unit.
Good luck! I am looking forward to seeing results!
You really should consider better names for your variables to make the code easier to read (or add comments). I will look at a working solution a little later today and come back to you.
635 separate triggers? There isn't even that many different event types and you have only got 12 functions. You must be repeating the same script several times.
0
Next trigger exercise will come a few days after christmas. I love the progress I have seen in this thread and I hope there will be the same activity in the next exercise.
0
Sure I can extend it atleast another week.
@StatusQ3: Go
A tip would be to utilize arrays to get the unit stats and past positions. Play around a bit.
@Shawn91210: Go
Looks good. Any special reason they sometimes take a weird path towards their target?
0
@emil604: Go
Here is a link towards a tutorial that covers this.
http://forums.sc2mapster.com/resources/tutorials/10948-data-simple-one-shot-linear-attacks/
0
@zeldarules28: Go
This is what I think is the biggest problem with the current system, together with the lack of sorting options. I would atleast be almost fully satisfied if they add a search box with the possibility to put in different search parameters and allow sorting of the game list after things such as time played, name and type.
0
@SouLCarveRR: Go
It's the return value if a units path to a location is blocked.
0
"The battered marines took cover behind a broken down truck as countless enemy rifle rounds rained death above them. After having spent just a moment to regain their breath they looked towards their sergeant for further orders. The sergeant responded with a silent nod, something which filled the marines with dread, there was no hope and they were to make their last stand."
Weekly Trigger Exercise #2
This weeks trigger exercise is about creating a squad mechanic where the whole group of units behave as one entity. You can use any unit for the exercise from a classical marine squad to a swarm of scourge. While you can interpret the concept of a squad any way you wish I have listed a few possible features to help you get started.
Good luck! I am looking forward to seeing results!
0
Does there even exist any constant roll modifier actors? I haven't seen any atleast.
0
@zeldarules28: Go
Nothing major, writing the galaxy script directly is for the most part solely for convenience.
0
Impressive, will be fun to play this when it gets released.
0
@HellGateSc2: Go
What is the value for FPS?
0
@HellGateSc2: Go
Which sort of timer are you going after and how often does it tick?
0
@GalacticBean: Go
If it is anything like C than sqrt does not except imaginary roots. If (h * h - 4 * g * k) becomes negative a domain error will occur.
0
@HellGateSc2: Go
You really should consider better names for your variables to make the code easier to read (or add comments). I will look at a working solution a little later today and come back to you.
0
@HellGateSc2: Go
You could calculate the time it takes for it to impact then calculate the distance it will have travelled by the next time tick.
0
@egodbout: Go
635 separate triggers? There isn't even that many different event types and you have only got 12 functions. You must be repeating the same script several times.