Slide System Concept

emjlr3

Change can be a good thing
Reaction score
395
*UPDATED* check the first thread for new script and implementation examples

to summarize

  • updated naming convention (thoughts?)
  • slide struct now treated as a unique object identifier
  • GUI wrapper functions now call the native struct methods
  • switched to an array stack loop (faster!)
  • added the ability to collide with the same unit multiple times within one slide instance
  • system requirements are completely optional
  • a few minor performance tweaks and various other updates
 

Sevion

The DIY Ninja
Reaction score
424
You should make them all struct arrays and use Alloc ;)

Performance increase because of less overhead.

Still working out OnDestory, but it should be fine.
 

emjlr3

Change can be a good thing
Reaction score
395
Ahh... Cool.
Adding method operators would be good.
JASS:
local Slide s = Slide[unit]

that is effectively what I am doing, albeit with more overhead associated with the SlideSystem (using a unit attachment system would be nice, but then there is another system req. some people may not need/use - that and which to use???).

You should make them all struct arrays and use Alloc

Performance increase because of less overhead.

Still working out OnDestory, but it should be fine.

can't speak for the practicality of this, as I've no idea how your system works.
 

Sevion

The DIY Ninja
Reaction score
424
Alloc is a custom allocation method. It's used with array structs. Much more efficient because of the fact that regular structs have a ton of overhead. Array structs have almost none.

It uses built in recycling and some really simple but efficient allocation/deallocation. It's basically a linked list method of allocation.

Very efficient very easy to use.

In fact, all you have to do is make your struct an array struct, [ljass]implement Alloc[/ljass] at the top of the script (under OnDestroy method if used) and you're done.

Use [ljass]thistype.create(parameters)[/ljass] to create your struct and [ljass]thistype.allocate()[/ljass] to allocate. Same as always. Instead of destroying with [ljass]this.destroy()[/ljass] you use [ljass]this.deallocate()[/ljass] directly. You can make a [ljass].destroy()[/ljass] method for your sake, but all-in-all it's used exactly as you would use a regular struct with more efficiency behind it ^_^
 

emjlr3

Change can be a good thing
Reaction score
395
more bloat IMO

I'd at least rather wait until you have the kinks worked out

does anyone else have any comments for this

I may submit it as a resource tonight
 

Sevion

The DIY Ninja
Reaction score
424
Truthfully, there are very few kinks at the moment, I think.

The only thing that needs working out is OnDestroy, which works atm (though encapsulation for it and trigger evals etc need to be done).

It's not really bloat if you think about it.

The entire library gets "removed" in the end and only the module implementation on the struct stays (which eliminates bloat created from JASSHelper).

So from a technical standpoint, it actually removes bloat.

I really do think you should use Alloc. I believe it should become a standard for non-extending structs.
 

emjlr3

Change can be a good thing
Reaction score
395
*UPDATED*

includes:

  • tracking of total slide distance and time
  • custom user collision filter
  • option to use pre-made libraries for destructible and cliff detection
  • changed the access levels for struct methods and variables
  • destroy method completes stack updating
  • ability to use interfaces for onHit, onPeriodic and onEnd, respectively
  • minor script re-arrangement and optimization
  • three new methods, unitsetslideeffect, unitslidedistance and unitslidetimed

comments welcome
 

kingkingyyk3

Visitor (Welcome to the Jungle, Baby!)
Reaction score
216
that is effectively what I am doing, albeit with more overhead associated with the SlideSystem (using a unit attachment system would be nice, but then there is another system req. some people may not need/use - that and which to use???).
Use hashtable? :)
 

emjlr3

Change can be a good thing
Reaction score
395
they were too slow, see post #20

I am just using a struct array now for efficiency's sake
 

emjlr3

Change can be a good thing
Reaction score
395
think i worked out all the kinks

next is a test map to demonstrate functionality - which should be finished in the next few days
 

Sevion

The DIY Ninja
Reaction score
424
I still think you should use Alloc. If only to remove some overhead. Systems like these should try to have as little extra as possible without removing functionality.

Edit: I saw this: "I am just using a struct array now for efficiency's sake"

I didn't see any [ljass]struct extends array[/ljass] in the script >_>
 

emjlr3

Change can be a good thing
Reaction score
395
hrmm?

i meant storage on units
 

emjlr3

Change can be a good thing
Reaction score
395
whats the benefit to that?
 

emjlr3

Change can be a good thing
Reaction score
395
when using Alloc?
 

emjlr3

Change can be a good thing
Reaction score
395
which still has issues...?
 
General chit-chat
Help Users
  • No one is chatting at the moment.

      The Helper Discord

      Members online

      No members online now.

      Affiliates

      Hive Workshop NUON Dome World Editor Tutorials

      Network Sponsors

      Apex Steel Pipe - Buys and sells Steel Pipe.
      Top