Olympus Technologies open testing

[Bobsymalone]

There's a bit of a problem in your lethe cloaking thing, where you've tried to access array entries with Base(Entry) and whatnot. You have to use Base:number(Entry) or Base:setNumber(Entry,Value). Unless that's a new thing I haven't heard of.

I might have a go building some rough versions of these bots at some point, I'll let you know of any typos or bugs.

[eduardo]

i love lying in bed hes amazing

[Lyinginbedmon]

There's a bit of a problem in your lethe cloaking thing, where you've tried to access array entries with Base(Entry) and whatnot. You have to use Base:number(Entry) or Base:setNumber(Entry,Value). Unless that's a new thing I haven't heard of.

Huh, that would be the only array method I've ever encountered that isn't Array(Index) then.

Should be fixed now.

[Bobsymalone]

Huh, that would be the only array method I've ever encountered that isn't Array(Index) then.

In Lua you use square brackets and whatnot, but there's no real native support for arrays and tables in E2. Both extensions are kinda hacky.

http://wiki.garrysmod.com/wiki/?titl...ression2#Array

[Lyinginbedmon]

The Archer entity tracker Mk-I is now in the Miscellaneous expressions post.

[Lyinginbedmon]

I've just added the Hecate entity tracker to the Miscellaneous expressions post.

Whilst the Archer entity tracker is designed to allow a drone to accurately retrace the path of a target entity, the Hecate entity tracker is designed for using the entity more as a scout, and keeping apace of it's position and distance realtime. So if the Archer entity tracker is a herding animal, the Hecate entity tracker is a stalking predator.

[Nikolas]

Your stuff is always so awesome. I envy you.

WORD! You hit that spot on

[Lyinginbedmon]

WORD! You hit that spot on

Well I can't take all the credit. If the concept didn't amaze so many people I'd never have the motivation to keep going.

I might have a go building some rough versions of these bots at some point, I'll let you know of any typos or bugs.

And advance on this Bobsy?

And in conceptual news: I'm considering a kind of "familiarity" system, so the drones recognise locators on other drones and increase a number associated with them in a table as they stay around longer. The end result being that in cases such as the Buddy system they gravitate towards drones with higher familiarity values.

Extending that, groups of drones formed either via familiarity or the buddy system average out their general (Director) action so they synchronise on something they al prefer.

And now why I'll likely never code that: Imagine a large group of drones, and then ticking one or two off until they decide to switch to Attack.

Yup. That's why. I've finally conceptualised a protocol even I don't want to give them.

[Lyinginbedmon]

I've just added the dumb version (Flies in a line then explodes) of the Cycnus missile prototype expression.

It almost certainly has issues, because I've never used applyForce before, but the signals and detonation should work so at the very least they're small landmines. If you happen to be on a server with Gcombat enabled, they can also serve as expression C4.

[Lyinginbedmon]

Okay, signals are presently busted, but after some testing with a slightly modified version (Using radios instead of signals) I discovered a few faults with the Lethe system.

At first, it didn't activate period, partially because the signals are broken and partially because of the way the code was made to activate interfering with itself.
Next, if stopped mid-transition, the arrays got messed up and wound up with part of a contraption that turned invisible and back and part that just stayed invisible. This is because activating decloak whilst cloak was still running messed with the arrays and set some entries to 0, so the Alpha would be 0 for some props. It didn't help that activating the cloak again overwrote the previous array.

I've fixed these issues now, so it should work perfectly once signals are operational again. As usual it seems subroutine pinging was the solution.

One curious little flaw in the Lethe chips right now is that the cloaking chips don't cloak themselves, so you end up with an invisible contraption and small seemingly-levitating expression chip. This wouldn't be hard to fix (entity():setAlpha(0) and entity():setAlpha(255)) but as of right now I haven't done so to the first page's code.