I attempted a super super simple use of mobile grids. To make an explosion happen directly north south east and west of a zergling.
At first it seemed to work fine, but then as you move the zergling around, the shape gets distorted as you can see below:
What's going on here? The map consists of five triggers, so it should be really easy to open it up and see what I'm doing wrong.
It's kind of hard to describe the bug, but if you open up the map, you'll see how it usually explodes, and how sometimes it'll explode in a funny shape, and then start exploding properly again.
Attachments:
None.
Because you used "kill" to kill the wraith, Starcraft will not create an air unit in the wraith's location until the next trigger cycle.
Basically, the wraith explosions are messing up the grid.
EDIT: My solution: create and kill all of the wraiths in one trigger.
Post has been edited 1 time(s), last time on May 17 2009, 11:29 pm by ForTheSwarm.
None.
Because you used "kill" to kill the wraith, Starcraft will not create an air unit in the wraith's location until the next trigger cycle.
Basically, the wraith explosions are messing up the grid.
Ahh, that's very interesting. Thanks
Do you know how many ticks (hyper trigger cycles, 1/12th of a second) it takes for a wraith that's killed to disapear completely, and no longer mess up the grid? From these results we know that it's at least 48.
Does this number vary from air unit to air unit?
None.
Do you know how many ticks (hyper trigger cycles, 1/12th of a second) it takes for a wraith that's killed to disapear completely, and no longer mess up the grid? From these results we know that it's at least 48.
Units are completely killed after one trigger loop.
None.
EDIT: My solution: create and kill all of the wraiths in one trigger.
Tried it. It doesn't work. What now?
EDIT: Well, what would probably work. Is first centering four locations, then creating and killing a wraith at each of the locations.
But I would really like to know why the map doesn't currently work, and also what exactly is triggering this. It seems to start acting weird when I move diagonal or something. What could be causing that?
Attachments:
Post has been edited 1 time(s), last time on May 18 2009, 1:35 am by scwizard.
None.
Here.
I reformatted your triggers so they would work.
Things I did:
-Changed hypers from 3 to 5. (It makes me feel better.)
-Moved the comment to the second last position (The one right before "Preserve Trigger")
-Erased Your timer Triggers, and Erased your Grid triggers.
-Made another DC Timer set of triggers
-Made another Grid. (I avoided the use of GIving, and just created the devourers.)
-
Your Fatal Error:::: You had the location size too big. It was a 2x2 Terrain Square location size, so I reduced it down to 1x1 Terrain squares. The corners were overlapping on the devourers.
And For god sakes lad, make comments for your Death Counters. Even though the Unit itself has the name Timer, It's better if you give the entire trigger a comment as well, so I don't have to read through it all.
EDIT:::::: The whole "Death of a wraith" thing is complete garbage. The map titled "Fast Attempt" has no timer, and it works fine to prove it.
Guys, if you do not know the answer to a question, do not guess.The other edits are for colors.
Attachments:
Post has been edited 4 time(s), last time on May 18 2009, 2:14 am by Pyro682.
None.
Things I did:
-Changed hypers from 3 to 5. (It makes me feel better.)
-Moved the comment to the second last position (The one right before "Preserve Trigger")
Handwriting lol
-Made another Grid. (I avoided the use of GIving, and just created the devourers.)
Thanks for the tips on good practice. I've heard about giving being one of the laggiest actions.
-Your Fatal Error:::: You had the location size too big. It was a 2x2 Terrain Square location size, so I reduced it down to 1x1 Terrain squares. The corners were overlapping on the devourers.
Oh, so that was the problem. Thank you very much.
And For god sakes lad, make comments for your Death Counters. Even though the Unit itself has the name Timer, It's better if you give the entire trigger a comment as well, so I don't have to read through it all.
More handwriting lol.
EDIT: The whole "Death of a wraith" thing is complete garbage. The map titled "Fast Attempt" has no timer, and it works fine to prove it.
Guys, if you do not know the answer to a question, do not guess.The other edits are for colors.
Fucking signed. Seriously stop wasting my time people.
Anyways I'm not going to try changing my handwriting unless I release a concept map or something. And then I'll probably do some sort of handwriting poll to find out what people prefer.
None.
Handwriting? You mean you're typing these suckers out? If not, what do you mean by "Handwriting"??
None.
Oh, handwriting refers to the difference in programming styles. How you format your comments. What you name your variables etc.
There's no right or wrong style of handwriting, but it's possible for certain handwriting styles to be considered sloppier or neater than other handwriting styles.
So what I was saying, is that this applies to starcraft maps to. For instance whether your put your comment at the top of your actions, or in the second to last position, or in the last position, doesn't effect the workings of the map, it's a handwriting difference. Just like naming of variables would be a handwriting difference in C.
None.
Lol, i put my comments on the very bottom.
None.
No. My handwriting is always right.
lol
None.
ForTheSwarm
Vrael -- It is, and I could definitely use a company with a commitment to flexibility, quality, and customer satisfaction to provide effective solutions to dampness and humidity in my urban environment.
