Author Topic: Multi-Stage Scripting Contest  (Read 20556 times)

 yesyes mmorpgs and school got me distracted i will post he task tomorrow
pm me if you please, wont let me pm mysel a remonder
« Last Edit: June 20, 2011, 08:47:36 AM by Destiny/Zack0Wack0 »

Sorry, haven't had access to a computer today.
EDIT: I can't organize this right now, I'll set up the next task on Friday. I'll let the task go for 7 days because I'm nice.
« Last Edit: June 22, 2011, 02:22:14 AM by Destiny/Zack0Wack0 »

I may/may not be able to work on this next task, depending on how much sanity my parents still posses.

I may/may not be able to work on this next task, depending on how much sanity my parents still posses.
That's OK, it'll be going for 7 days anyway. I'm thinking about task ideas and writing the guidelines now.

Round 4 - You have 7 days to complete it from 25/06/11 GMT+10
You must create an output event that fires a projectile at a position or named brick. (ie. spawnProjectileAt)
Your script must follow these guidelines:
 - Functions exactly like spawnProjectile on the brick only it will fire at a position or a named brick rather than a starting velocity.
 - The first argument should be the datablock type.
 - The second argument should be a text box to enter the name of a brick to fire the projectile at. If it is blank it fires it at the position mentioned in the next argument instead.
 - The third argument is a vector saying the position to fire at. Its only used if the named brick argument is blank.
 - The fourth argument is a vector to offset the velocity by.
  EDIT: The fourth argument can optionally be a number to scale the velocity by. This is easier if you want to do that instead.
Pretty easy to complete, I thought I'd make it easier than the other tasks considering the lack of final submissions.

Honorable vs Red_Guy
otto-san vs Resonance_Cascade
Munkey vs ::Matt::
Treynolds416 vs DrenDran
« Last Edit: June 25, 2011, 07:24:41 PM by Destiny/Zack0Wack0 »

Crap, vectors.

Time to learn a new trade.

Crap, vectors.

Time to learn a new trade.
Draw a diagram. It'll help, trust me.



Also for those who aren't too good at maths, I'll give you an important hint: Rise over run, or 'gradient'.

Round 4 - You have 7 days to complete it from 25/06/11 GMT+10
You must create an output event that fires a projectile at a position or named brick. (ie. spawnProjectileAt)
Your script must follow these guidelines:
 - Functions exactly like spawnProjectile on the brick only it will fire at a position or a named brick rather than a starting velocity.
 - The first argument should be the datablock type.
 - The second argument should be a text box to enter the name of a brick to fire the projectile at. If it is blank it fires it at the position mentioned in the next argument instead.
 - The third argument is a vector saying the position to fire at. Its only used if the named brick argument is blank.
 - The fourth argument is a vector to offset the velocity by.
  EDIT: The fourth argument can optionally be a number to scale the velocity by. This is easier if you want to do that instead.
Pretty easy to complete, I thought I'd make it easier than the other tasks considering the lack of final submissions.

Honorable vs Red_Guy
otto-san vs Resonance_Cascade
Irk89 vs Munkey vs ::Matt::
Treynolds416 vs DrenDran
mondays

But I changed up the arguments just a bit:

1. Datablock --- Obvious, and just like you said.
2. String for target brick name --- Once again, like you said.
3. Float for speed adjustment --- This is a useful feature, it replaces the not really needed 'substitue velocity' parameter.
4. Randomizing vector --- Like your offset vector, but a random vector is more useful, because if you wanted an offset, you'd just move the target brick.

Also, if there's a more efficient way to get a named brick, let me know.
« Last Edit: June 25, 2011, 09:46:20 AM by DrenDran »

aaaaaaaaaa could you kindly edit that out of your post and PM me instead, so no one else can see the script.

Is it okay if I go submit my FireAtBrick add-on to RTB now?
Seeing how it probably won't get approved until this round is out anyway.

Is it okay if I go submit my FireAtBrick add-on to RTB now?
Seeing how it probably won't get approved until this round is out anyway.
Just leave it to the day before the round ends, please.

Just leave it to the day before the round ends, please.
Oh fine.
I guess I'll add a "FireAtClosestPlayer" event.