[Idea] [system] (vJass) CustomMissle

[Berb]

I haven't actually seen the system (I suppose you haven't either), so I guess both of our comments are kind of irrelevant. I was merely saying that it sounds like he's just being lazy and using xe.

 

[Anachron]

Well, if you call it lazy when I use open-source system that are already made and fit my needs then yes, I am lazy. For all others I am just using the opensource stuff because its open-source and exactly what I am looking for.

About the xe-stuff: I will use xepreload, xefx, xedamage and xecast in the missle system. I don't see why I have to recreate it myself.

You guys really miss the point in doing opensource librarys.

 

[Berb]

Well what you're suggesting sounds more like a module for xe than an open-source library.

 

[Anachron]

It is.

 

[JeffreyQ]

Alot of cool features there. But if you want to make a good system. Make it standalone that is compatible with the rest. Because importing vJass is already pain in the ... Importing a useful system requires more importing of other system is just...

If you can try to make it standalone. I might actually use it. Most of the time i skip vJass spells/system is because they have a bunch of things to import before i can actually use something.

Just my opinion though. Subscribed [:

 

[Anachron]

But the point in importing the system is that you don't have to do everything for your own.

 

[JeffreyQ]

I remember you said the same thing to one of my system where you won't be bothered to import to use since it is such troublesome when one only need to copy and paste triggers. So i am just giving you the same idea. Make it easier for people to import and this system will be good [: Just my idea though. It is always good to make things easier for importing stuff since you said you are going to replace xe on your 1st post, you should stick with your idea.

In the end is up to you [: i will still be looking forward to this project.

 

[Berb]

In my projectiles library I make things like TimerUtils optional, allowing users to choose their own level of requirement.

 

[Anachron]

Open-source systems should never be optional.
Only modules should be optional. You may have missed the point of opensource.

 

[Berb]

How would making optional requirements hinder its functionality in any way?

Open-source systems should never be optional.

What exactly do you think Vexorian added the optional keyword for then?

Everything done in the World Editor is open-source, and there are plenty of scripts that use the optional keyword on their requirements. There is no excuse to not maximizing the diversity of your code. The only explanation is that you don't want to make it optional so its easier to code.

Either way I've posted the code to my Projectiles library in a separate thread for optimization criticism.

 

[Anachron]

You either use stuff that is open-source or not. Why should you make something for your own if you could just require an opensource library?
I mean I really need xe, I could do it on my own too, but thats exactly contraproductive to the xe-concept.

 

[Berb]

Well do what you want, I'm not trying to argue with you.

 

[CHA_Owner]

--==BUMP==--

So Anachron how the missile system coming along?

 

[Anachron]

Not so good xD:
Switching the systems awkwardly now.
(For example, I did a CustomFilter system)

 

[Darkt3mpl3r]

failed on the very first arc movement.... better not try to continue then :F

I can help out with that if you want.

 

[Berb]

I'm thinking of releasing my projectiles system after its been re-written.

 

[Anachron]

How long do you need? ^^

 

[Berb]

Not long. I was just doing some tests yesterday (I've been optimizing it like crazy) though to see how well the unit-enumeration worked with spread-out units (because with a pack of 70+ units it obviously lags a bit) and it seems to handle 250+ projectiles without dropping much frame-rate (and this is on a relatively out-dated computer). Of course, having 330+ units visible at once is rather stressful on the processor in the first place.

The only problem that arose was trying to get projectile-projectile collision working perfectly, though I do not think it will be included in the system (this release, anyways) because my understanding of continuous collision detection is insufficient, and the alternative option is less efficient.

I should really post a submission thread though so I can get some feedback as to the functionality that the system should include. Currently projectiles have "options" for different sorts of functionality, for instance if you do set someProj.activeUnitCollision = false the projectile will not longer execute the .onUnitCollision interface method.

It should be soon though.

Oh, I also need to add some projectile-enumeration functions so that the user can reference the projectiles he creates without having a direct reference to them.

 

[Anachron]

But that isn't that much functionality. What else do you have?

 

[Berb]

Well the interface methods are:

method onFinish
method onBirth
method onUnitCollision
method onGround

Other than that, you can modify the projectile by using these "setup" variables:

boolean activeUnitCollision
boolean activePitchRotation

The active-pitch-rotation was recently brought over from an extension struct so that I could remove the onLoop virtual method (since it is very inefficient), and should typically be used with the dummy.mdx model with various pitch animations.

real collision
real scale
real timescale

These are available to the user to modify values in real-time. Scale modifies the size of the projectile, time-scale modifies the "slow-motion" effect on the projectile (allows the projectile to be stopped, slowed down, or sped up in the middle of its flight). Collision simply affects the radius of the projectile.

The projectiles are initialized by specifying a unit (you do not have to imitate WarCraft III projectiles, instead you could make a unit a projectile to simulate a "jump" or something) and then launched by method doLaunch which takes various parameters to setup the projection sequence. It uses vectors for the starting point/ending point however if the ending point is changed in the middle of the flight it will activate projectile "homing".

The dynamical aspect of the system comes from the fact that projectile is a data-struct that can be extended, opening the door to any user-customizations. By default, the projectile struct doesn't require a "source" unit or a "target" unit, instead these things can be added by extending the struct. For example:

struct war3missile extends projectile
    unit    source      = null
    unit    target      = null
    
    method onFinish takes nothing returns nothing
        call UnitDamageTarget(source, target, ...)
        call .destroy()     //* If .onFinish is not declared, this is done automatically.
    endmethod
endstruct

Once you've launched your projectile, what you have declared here will dictate how the projectiles reacts when predefined events take place. For example, when the projectile is "finished" its trajectory, it will cause the specified source unit to damage the specified target unit.

To be honest this isn't a system for noobs, and I'm not trying to show off how many things you can do with it, because the possibilities are end-less. If the user extends the projectile struct he/she can pretty well do whatever he/she wants with it.

 

[Anachron]

Okay guys, I am reviving this.

The main library has again been rewritten, now I don't use XE anymore.
XE is a really old system right now and shouldn't be used.

The new system allows the following interfaces (right now):

        private stub method onUnitTouch takes unit theUnit returns nothing
        endmethod
        
        private stub method onCollide takes thistype theCollider returns nothing
            call .destroy()
        endmethod
        
        private stub method onFly takes nothing returns nothing
        endmethod
        
        private stub method onStart takes nothing returns nothing
        endmethod
        
        private stub method onEnd takes nothing returns nothing
        endmethod
        
        private stub method accelerate takes nothing returns nothing
            set .moveSpeed = .moveSpeed + CM_PERIOD * .acceleration
        endmethod
        
        private stub method flyCheck takes nothing returns boolean
            return true
        endmethod

 

[Catch_ya]

The OnStart is every 0.02 second? Or do you declare a global real in the setup trigger which will be the interval?

lol 700th post.

 

[Anachron]

OnStart is after the missle is actually being created.
You can initialize your own stuff at that point.

Congratulation on 700ths post.

 

[Catch_ya]

OnStart is after the missle is actually being created.
You can initialize your own stuff at that point.

Oh I see, actually I meant OnFly.

Congratulation on 700ths post.

Thank you.

 

[Anachron]

Oh yes, onFly is basically every CM_PERIOD seconds.
(Its a global 'public' variable which can be accessed from anywhere)

 

[Catch_ya]

Oh yes, onFly is basically every CM_PERIOD seconds.
(Its a global 'public' variable which can be accessed from anywhere)

Hehe that was what I was thinking.

EDIT: What about updating the first post. =)?

 

[Justify]

Well, I like the names from Vex much more.
No one cares if you steal "loopControl" or "onUnitHit", but the names... ugh, don't like them.

 

[Anachron]

Currently I have replaced onFly with onLoop.
And onUnitHit != onUnitTouch.
OnUnitHit is when the missle is reaching the target unit, not when its touching any.

 

[CHA_Owner]

very nice sounds very promising

 

[Anachron]

Yes thanks

 

[The Reborn Devil]

/me prepares to reject as soon as this comes out.

 

[CHA_Owner]

/me prepares to reject as soon as this comes out.

ummmmm if you reject this when it comes out i will go on killing spree and your first

 

[Catch_ya]

/me prepares to reject as soon as this comes out.

Reason?

 

[Anachron]

There is none xD

 

[Berb]

Because mine will be released by then. Its actually done I'm just too lazy to write up a paragraph about it.

 

[Justify]

There are millions of them out and there are even more people who could create good ones, no reason to reject anything.

 

[Anachron]

Uh well, if you don't get it, it's a joke (kind of a game I and TRD am playing).

 

[Justify]

Don't worry, I did, just refering to Berba

 

[Berb]

Boom, head-shot.

 

[Anachron]

But please, this is off topic.

 

[Anachron]

Hey guys
I have finished another milestone. The first preview comes soon.
I already made homing, target and soon arc and collision detecting comes as well.
Stay tuned.

 

[Berb]

Homing for homies. I'm really curious to see how you went about doing your homing --and your collision. I'm staying tuned!

 

[CHA_Owner]

Hey guys
I have finished another milestone. The first preview comes soon.
I already made homing, target and soon arc and collision detecting comes as well.
Stay tuned.

Yea i cant wait to test it

 

[Anachron]

Actually I haven't added it yet.
But I think I will register the OnRange event.
If that doesn't work that well I will iterate through all instances or I will make a custom engine that uses some basic math stuff.

 

[PurgeandFire]

You may be interested in this thread (if I hadn't posted it already) if you're looking to do projectile collision:
http://www.thehelper.net/forums/showthread.php?t=145882

Good luck with the system. =)

 

[Anachron]

Thanks I already checked hws, thehelper and wc3c.
All of the methods are somehow ugly for me.
I will check if I can make a better one.

Edit:
Aww.

Rect(GetUnitX(enteringunit), GetUnitY(enteringunit), GetUnitX(enteringunit), GetUnitY(enteringunit))

Seems to work with collision sizes. Thanks.

 

[Anachron]

Eww ):

No more feedback? Guys I need your opinions!
Tell me what you want, I will make it possible.

 

[CHA_Owner]

Eww ):

No more feedback? Guys I need your opinions!
Tell me what you want, I will make it possible.

Well maybe make z angle as in a missile comes toward you then you activate a block spell the missile flies straight upward into the sky

 

[Kingz]

I am intrigued how will you implement X/Y arc's.

I used the parabola equation for it, but i think you will probably use something different, no?

 

[Berb]

What do you mean, X/Y arcs?