Library: Awesome Scripts: Linked-Tier Hierarchics. Fast Cone Spread, Physics Library.

Im releasing all of my Pwnsome Scripts for the public. Lets see what people can make out of the sweat and countless hours effort I have spilled into these little masterpiece gems.

Hope you enjoy it.


https://wiki.secondlife.com/wiki/Hierarchics

Might wanna change some of the Developer# keys as it includes a smart fail-safe anti-theft system in case a script were to be taken out of a piece, it even checks surrounding prims for non-creator scripts that might be trying to inject messages into the linkset or observe internal communications.

A smart fast way to creating cone spread in a weapon, or perhaps even in some unique and creative ways!

https://wiki.secondlife.com/wiki/FastConeSpread

Has wicked trajectory functions and a target interception function.

https://wiki.secondlife.com/wiki/PhysicsLib

Interesting! I'm gonna have to play with these in a bit :o)

Based on my interpretation of A*, I built a pathfinder before mono was even known about, trying to juggle for high performance I built it all based on purely integer computation.

https://wiki.secondlife.com/wiki/Basic_A-Star_Pathfinder

Thank you for the contributions, may I suggest a bit more explanation however, of the intent and uses to those like myself, who don't readily see it's applications?

I assume as you are putting it in the wiki, that you would like to see your code understood and used by others, thanks again

Very cool, thank you for posting this!

One quick note : Your physics functions have variables defined that are never used: D, D2, and MaxD. I have not yet had time to really poke at this stuff, so I assume that's just an artifact of legacy code?

hehe I played with several variations of this, so I definitely want to see how you approached it.

I...totally didn't notice those.

But then again I had to remove approximately 200 - 300 lines of comments of an entire essay trying to make the piece of code work.

So yes, those are artifacts of legacy code of older variations. MaxD is a useful debug I used to compute the maximum distance, to check my script was working correctly on the error checking part due to the added complexity when I wanted to allow different heights instead of the presumption Z = 0.

Hm, im curious about what others have tried? I tried to just do what my gut feelings said was the best idea, I have been thinking about the concept for a long time and previously used many hardcoded instances which even introduced joint limits and neat features, but they lacked the pure flexibility that I REALLY needed for my purposes of a huge realtime strategy game. The final result of this is what I think is a flawless concept of a self-aware system.

heh I actually meant the security features (though I have played with scripted hierarchies, but nothing complex, mostly message passing, because it was useful to memory scripts I was playing with at the time.)

most of my security features have been based on prim permissions, owner/creator comparisons, and hidden variables (some of which can be VERY stealthily buried).

ETA:
my whole concept on hierarchical structure relied on prim names and prefixes to them root could be any name (because it has a link target) but anthing past that A,1,a, and special character prefixes if i went lower.... I didn't get much into the physical side though) all those scripts were lost in my HD or I'd be happy to share =/ I had intended to open source it for memory objects... lot of work to rebuild all that and it's not on the schedule right now

Your A* will always find a straight line no matter what. It doesn't appear to be checking for "invalid" moves (such as not being "all object entry", or "scripts ok." It seems to assume that where ever you put it, it will have full movement privedges..in which case just compute a straight line..much easier

Im not sure I understand you Aztra, but it works fine for me on avoiding obstacles? It is not meant to use land parcels as the navigation spatial environment but a flat 2D grid of prims spaced at 1 metre per node, where the script currently allows a maximum size of 20x32.

I built a tiled 10x10 grid to test it out with each 1x1x0.01 prim containing the Tile script.
Set "vector Ref" in the unit to the lower corner of the grid.
Made a new prim named 'Target' on one end of the grid.
Positioned the unit as well on the opposite side of the grid.
Touched the tiled grid prims to create some obstacles.
And finally clicked the unit to command it to move towards the target.

Ah...ok. I see it now. You create "obstacle" objects which when clicked use regionsay to tell your moving object to add them to the obstacle list. Then you run A* based on that.

Soory..I've just always used A* for my simscan sensors, and missiles to find their way through a sim (based on object entry and scripts "ok" to their target.

different focus =)