System Throw System

[GooS]

>my system is for realistic throw effects and jumps

And yet when I target a moving unit it wont be thrown to that specific position. I don't know why I dont know JASS. But thats what happens (for me) and I think that should be fixed, If this only happens for me, then sorry, somethings wrong with my WC3.

btw why are you using a skill that targets a specific person instead of an AoE?

 

[Trollvottel]

no problems for me

 

[waaaks!]

i tried the demo map, and used the throw unit spell, but it doesnt throw the unit, instead knock backing it with no arc

 

[Cohadar]

Maybe he forgot to use crow form,
it also help if you lift a unit a little from the ground before you throw to prevent false groundhit detection.

 

[Trollvottel]

weird thing. it works for me perfectly, with arc.
anyway, heres a new update, more values to get in the functions:
TTHROW_ThrowUnitAndDo(args)
TTHROW_ThrowAndDo(args)

now you can refer to the Z-angle and the speed.

[Merge]
bump


any comments, tips or bugs? and no mod looking at this?

 

[cr4xzZz]

Library name looks ... well, awful. Can't you change it to something else?
Other than that it seems fine. Rly nice. ^^

 

[emjlr3]

an option could be given for homing projectiles(or another whole function for homing), because this is a projectile system, not a "throw" system, its name sohuld reflect what is really does

I really disliek your function naming, or rather, your library name, TS would be satisfactory I think

I think you should have used realistic gravity settings, 300 just screams "reality check"

it should be noted that this is not compatable with PUI, which most ppl will dislike I think

just looing quickly here, you could store GetUnitIndex, rather then grabbing it over and over

as opposed to chaning input values, it would be smarter to tell the user htey made a mistake

and that is just with ThrowAndDo

possibly more to come later

 

[konerboy]

thank you i'm gonna need that for a Rocket laucher (bazooka)

+rep

 

[Trollvottel]

it should be noted that this is not compatable with PUI, which most ppl will dislike I think

why is it not compatible? i think it uses PUI??!

I think you should have used realistic gravity settings, 300 just screams "reality check"

well if its a normal value (9.8) youll have to use very low speed

 

[emjlr3]

yea don't know what i was thinking with the no-PUI bit, it uses PUI, scratch that

 

[Trollvottel]

minor update:
- new name
- small bugfix
- projectiles can't leave the map area now, so the game won't crash
- in the userfunc you will refer to the UnitIndex with INDEX.

 

[Trollvottel]

~Bump

 

[Trollvottel]

bump

 

[ichti]

I tried this spell, But it don't work properly (i hope).
When i have throwed the first unit, and cast the spell again, it just throws with the corpse of the first throwed unit? i don't hope that the way it is meant to be..
And when the corpse is gone it just says "WARNING: PUI - Bad unit handle"

 

[Trollvottel]

thats just because you throwed the dead unit. in the example trigger i set the unit to throw to this preplaced unit and then kill it. and if you use pui for dead units with debug mode on its a bad unit handle.
uploaded a new version, the units fly better now. and you can set the start height for the units

 

[Trollvottel]

new bugfix

 

[thelosthero]

I can't edit the triggers for some reason...every time I try to edit them, even If I disable and try to enable them, it displays error messages.

The erorrs shown for when I try to enable the CastTest trigger displays the following:

Spoiler

21 errors:

Line 21: Expected end of line
Line 24: Expected end of line
Line 26: Expected a code statement
Line 28: Expected a code statement
Line 29: Expected a code statement
Line 30: Expected a code statement
Line 31: Expected a code statement
Line 32: Expected a code statement
Line 33: Expected a code statement
Line 34: Expected a code statement
Line 44: Expected a function name
Line 45: Expected a name
Line 46: Expected a variable name
Line 47: Expected a code statement
Line 50: Expected a code statement
Line 51: Expected a code statement
Line 52: Expected a name
Line 53: Expected a name
Line 54: Expected a code statement
Line 55: Expected a code statement
Line 56: Expected a code statement

Note, I only posted the CastTest errors because there was only 21 messages and I couldn't copy and paste the error messages(I typed all of them in the spoiler word for word) the TPS trigger alone has 272 errors.

I'll list the code for the differnt types of errors to help you out.

Line 21: Expected end of line

 //TESH.alwaysfold=0

Line 26: Expected a code statement

endfunction

Line 44: Expected a function name

call TPS_Throw(GetTriggerUnit(), 'h000', angle, TPS_GetSpeedToDis(distance, angleZ), angleZ, 400, true, 150)

Line 45: Expected a name

call RemoveLocation(loc)

Line 46: Expected a variable name

set loc = null

 

[Trollvottel]

do you use the normal editor or Jass Newgen Pack?

 

[thelosthero]

Normal, Im guessing thats the problem?

 

[Trollvottel]

yes.
the map uses vJass which is unuseable for the normal editor. so you cant save. if you use the Jass Newgen Pack it should work