Easy Making Projectiles

I simplified my system for people who wanna make custom projectiles to use.
Atm it only support projectiles like objects, unless u mess with the internals.
Cus u can make alot with the internals, but its harder so keep on the basic system outside.

Anyway, download it those who are interested, the triggers are examples with comments. Its reeeaally easy to setup and add new stuff ^^

Download, try out and tell me if its easy to use so far
NOTE: this require u to have JassNewGenPack

UPDATED: I TURNED THIS INTO A RABBIT HUNTING DEMO ^^ And the triggers are real simple

well let see... xD

Hoooo weee... this shit is so bugged =\ have you test it ? it freezes my PC for sever 10 seconds =\

+ minimal possiblitys... currently uninteresting.

ingame or in WE lol

I just want to know one thing,
will it crash if I send projectile out of map borders?

If it does not crash I will use it.

it doesnt, cus projectiles will be removed then
also credit if u want :) btw i like ur story about jass and MUI... :D ur a good writer, maybe u can write movie script for me sometime

ingame... the peasants... are makeking alot of shit =\ + i got video artefacts O_O (it's happends under extreme "video" stress)

Hehe, this is great, I was just about to make this thing myself
and now I can use yours

This is what people call "in the right time in the right place"

I won't credit you because I am evil :P

hehe just kiddin, here have some rep.

EDIT:
After detailed inspection I discovered a couple of flaws.

1. OOMS is in map header.
This is just untolerable, transfer it to trigger. (I did it and it worked)

2. vector struct? lowercase V ??? NEVER start structs with lowercase - fix that
search replace would do enough.

3. System is too big. This is because it is not one system but couple of systems together.
For example Vector manipulation can be separated into it's own system.

4. Documentation is just horrible.
You need at least interface comments, here is an example how to do it:

Hidden information: JASS: // struct CollectionXX // .isEmpty() -> boolean // .size() -> integer // .contains(integer) -> boolean // .add(integer) -> boolean // .remove(integer) -> boolean // endstruct // // struct IteratorXX // .noNext() -> boolean // .next() -> integer // .remove() -> nothing // endstruct or even better like this: JASS: interface Collection method isEmpty takes nothing returns boolean method size takes nothing returns integer method contains takes integer e returns boolean method add takes integer e returns boolean method remove takes integer e returns boolean method iterator takes nothing returns Iterator endinterface interface Iterator method noNext takes nothing returns boolean method next takes nothing returns integer method remove takes nothing returns nothing endinterface

One final question what happens if I use this to jump with my hero out of map bounds?
Will he get removed or killed? If he gets removed you need to fix that.

he will... and btw dont look into my internals in the system. it isnt as u see :)

exactly...

cohadar don't be a such clever teaching ass <_<

and btw MaD[Lion] hmmm =\ try to create 200+ (i don't how many your CPU supports) (the most premitive projectiles) and add and message to the end of unit-loop function (which moves the projectiles) =)

i mean you got (as for me) to many operations in 1 thread... so after some projectiles it will crash (reach the oplimit). so be causious.

Who would want to make 200+ projectiles in the first place?

i can go to 200 projectiles easily with only using OOMS, but this is the simplified version, not meant to be fast, just to be easy to use, for people who wanna make jumps and khockbacks ect :)

Oh I simply can't help it, it is stronger than me.

MaD[Lion] I really want to use your system,
Could you please shape it up a bit.
it has good potential but it is unfinished
and without interface,
and I simply cannot use any system that does not have clean interface.

I would be glad to give you comments as you work your way out
to make this an industry-standard

EDIT:
rule #1
If it is not easy to use than it is not a system.
rule #2
If it has no interface than it is not easy to use therefore it is not a system
rule #3
If it has no good comments it is not good enough to be published

This is not a system, just something i made for a friend to use. But feel like releasing it here for people who want to.

I dont ahve interface cus i dunno wat it does exactly and what good it gives for simplifications.

Updated btw, and again, dont look inside the system, everything u need is described outside it. Unless u wanna make something complex then u need to understand the system. But this system is for new users tat want fast result. So just copy paste ^^

You don't need to have real interfaces from vJASS

You can also have a list of functions from your system
somewhere in the starting comment. (with short descriptions)

That way users can just view that list and get a quick understanding of what system does, or if you use the system but forgot some function name,
you can simply look in the list instead of searching it in the system code.

And please put some versions to your maps,
so people know when you actually put a new one.

And don't simply remove the old map when you post new,
you should keep at least one previous version attached
some people might need old versions,
or they simply want to compare and see what you changed.

Oh and also write down your changes so people don't have to guess.