Olympus Technologies open testing

[Lyinginbedmon]

So by now I imagine you're all getting perhaps a little sick of seeing me drone (hah) on about my coding and designing for my drones.

Since my computer is currently unfixable (There is a second computer that needs to be fixed before mine can, which is out of my hands) and I can't afford a spare to build my drones on, all I can do is design and code, I can do no testing.

So I thought I'd give you all some things, little mechanisms from my drones, for you to put together into your own contraptions. I'll code together the buddy system and the stealth system in a little bit.

The benefit being that you get some tangible benefit from my ramblings and I get effectively some testing done for them.

[Lyinginbedmon]

Weaponry & Defense expressions

Caduceus teleportation protocol Mk-I
Effect: Whenever an RPG round is within 75 units (Determined every half second), the expression feeds a random location between 150 and 200 units from the attached object to the hoverdrive and launches it, effectively ensuring that the RPG round will miss.

Application: Place the expression on a prop, wire the hoverdrive SetJumpTarget and Jump to the Jump output and the vector input to the Vector output, and attach a toggle button (On = 1) to the Defend input. Ensure that the hoverdrive is connected to the overall contraption or it will simply randomly teleport whenever an RPG comes near the hoverdrive, without actually moving the contraption.

@name Caduceus teleportation defense	
@inputs Defend
@outputs Vector:vector Jump Dist Clk
@persist Base:entity Clock RPG:entity Loc:vector
 
if(first()){
    Base = entity():isWeldedTo()
    Clock = findUpdateRate() + 100
 
    Loc = Base:pos()
    Vector = Base:pos()}
 
#Activation & RPG search
if(Defend){ 
 timer("sear_clk",Clock)
 if(clk("sear_clk") & !Clk){
 findByClass("rpg_missile")
        RPG = findClosest(Base:pos())}}
 
#Checking the distance to nearest RPG
if(RPG & !Clk){
 timer("rpg_check",10)
    Dist = Loc:distance(RPG:pos())
 if(Dist < 400 & clk("rpg_check")){ 
        Loc = Base:pos()
 
        Rand1 = random(-1,1)
        Rand2 = random(-1,1)
        Rand3 = random(-1,1)
 
        X = random(150,200)
        Y = random(150,200)
        Z = random(150,200)
 
 if(Rand1 < 0){X = X * -1}
 if(Rand2 < 0){Y = Y * -1}
 if(Rand3 < 0){Z = Z * -1}
 
        Vector = vec(X,Y,Z) + Loc
        Jump = !Jump
 Clk = 1}}
 
#Ensure the hoverdrive has rematerialised before rechecking
if(Clk){
 timer("tele",100)
 if(clk("tele")){Clk = 0}}

------------------------------------

Cycnus dumb missile Mk-I
Effect: Need a quick missile? Plant a Cycnus dumb missile chip wherever you like and tell it to fire. If it hits anything, keeps going for 5 seconds, or you send the signal to detonate anyways, it explodes out into a 200 unit radius dealing moderate damage.

Application: Place the launch chip and attach buttons or numpad inputs to both inputs, they don't need to be toggled but the On values must be positive. Then, place the missile chip(s) anywhere you want, with the chip decal facing in the direction you want the missile to fire. Do NOT weld them to anything. The inputs should be self-explanatory as to what they do.

	
	
@name	Cycnus dumb missile
@inputs 
@outputs 
@persist	Fire Premat Push:vector Me:entity Clock
 
if(first()){
	Push = -entity():up()*10
	Me = entity()
	signalSetGroup("Cycnus launch",0)}
 
runOnSignal("Launch",0)
runOnSignal("Detonate",0)
 
if(signalClk("Launch")){Fire = 1}
if(signalClk("Detonate")){Premat = 1}
 
if(Fire){
 interval(10)
 applyForce(Push)
	Clock +=1
 
 if(Clock = 500|$Me:vel() < 0){Premat = 1}}
 
if(Premat){selfDestruct()}
 
  
@name	Cycnus remote
@inputs	Launch Detonate
@outputs
 
if(first()){signalSetGroup("Cycnus launch")}
 
if(Launch){signalSend("Launch")}
if(Detonate){signalSend("Detonate")}
 

Notes: This is my very first attempt at using applyForce(), so if anything goes wrong it's either that or the lack of the detonate(N,N,N,N) function in your copy of Wiremod.

------------------------------------

Lethe stealth protocol Mk-I
Effect: Turns an entire contraption completely 100% transparent and back again, preserving initial transparencies, at the push of a button.

Application: Place the first expression chip onto your contraption and the second anywhere else (Do NOT put it on the contraption, or you'll have a hard time finding it). Wire the Active input of the second chip to a toggled button (On = 1, Off = 0 for the button).

	
	
@name Lethe stealth cloak
@inputs 
@outputs 
@persist Base:array Body:array Entry
 
if(first()){signalSetGroup("Lethe")}
 
runOnSignal("Engage",0)
runOnSignal("Disable",0)
 
if(signalClk("Lethe","Engage",0)){Cloak = 1}
if(signalClk("Lethe","Disable",0)){Decloak = 1}
 
if(Cloak == 1){ 
	Body = entity():getConstraints()
 
 timer("working...",10)
		Base:setNumber(Entry, Body:entity(Entry):getAlpha())
		Body:entity(Entry):setAlpha(0)
 
 if(Entry == Body:count()){ 
 stoptimer("working...")
		Entry = 0
		Cloak = 0}
 else{Entry += 1}}
 
if(Decloak == 1){
 timer("decloak",10)
	Body:entity(Entry):setAlpha(Base:number(Entry))
 
 if(Entry == Body:count()){ 
		Entry = 0
 stoptimer("decloak")
		Decloak = 0}
 else{Entry += 1}}
 
  
@name Lethe cloak activator
@inputs Active
@outputs
 
if(first()){signalSetGroup("Lethe")} 
 
if(Active){signalSend("Engage",0)} 
else{signalSend("Disable",0)}
 

Notes: This basically remotely sets the contraption with the first expression chip to have Alpha 0 on all of it's components, so you could still walk into it, shoot it, etc. you just won't be able to see a single part of it.
Because it's signal based, you can even put it on a bunch of different contraptions and operate the whole cloaking system with the one button. Invisible contraption army?
This adaptation is also my first attempt at using the Signal functions, so if it doesn't work that's probably why.

------------------------------------

Lethe stealth grenade
Effect: Throwing down this expression grenade will cause all of your items (props, contraptions, and even NPCs) within 400 units to gradually disappear from view into invisibility. Activating the signal with the second expression will reverse the process and destroy all of your Lethe grenades.

Application: Place the first expression wherever you want, and place the second expression anywhere and wire a button (toggle or otherwise, on = 1) to the Deactivate input. You do not need to have the second expression spawned to use the first, only to deactivate it.

	
	
@name	Lethe stealth grenade		
@inputs 
@outputs 
@persist	Base:array 
 
if(first()|dupe()){ 
	signalSetGroup("Lethe") 
 
 findInSphere(entity():pos(),400) 
 findSortByDistance(entity():pos()) 
 
	Qty = findInSphere(entity():pos(),400) 
	Base = array() 
 
 if(Entry != Qty){ 
 interval(10) 
 if(findResult(Entry):owner() != entity():owner()){Entry += 1} 
 else{ 
			Base:setNumber(Entry,findResult(Entry):getAlpha())
 findResult(Entry):setAlpha(0)
			Entry += 1}}
 else{Entry = 0} 
 
runOnSignal("Grenades off",1)} 
if(signalClk("Lethe","Grenades off",1){ 
 if(Entry != Qty){ 
 interval(10) 
 if(findResult(Entry):owner() != entity():owner()){Entry += 1} 
 else{ 
 findResult(Entry):setAlpha(Base:number(Entry))
			Entry += 1}}
 else{selfDestruct()}
 
  
@name	Lethe grenade deactivator
@inputs	Deactivate
@outputs 
 
if(first()){signalSetGroup("Lethe")} 
 
if(Active & ~Active){
	signalSend("Grenades off",1)
	selfDestruct()}
 

Notes:You can change the 1s in the signal settings to 0s to prevent others from reverting your grenades, but it's largely there for admin purposes at the moment.
The cloaking field does not affect any objects or NPCs that move into the area during or after activation, but it will revert them on cue even if they have moved out of the region afterwards. In theory if you stand close enough you can turn yourself invisible.

[Lyinginbedmon]

Motion Control expressions

Vector Triad calculator Mk-I
Effect: This code takes a trio of vector thrusters and has them hold an altitude of 30 wherever they are.

Application: Take the expression and place it as close to the middle of the triad as you can, then wirelink them into the three inputs.

@name	Vector Triad calculator		
@inputs	Thrust1:wirelink Thrust2:wirelink Thrust3:wirelink		
@outputs 
@persist	Vec1mod Vec2mod Vec3mod
 
if(first()){ 
 timer("vecfinder",10) 
 if(Thrust1 & Thrust2 & Thrust3){ 
			Vec2mod = Thrust1:entity():pos() - Thrust2:entity():pos()
			Vec3mod = Thrust1:entity():pos() - Thrust3:entity():pos()
			Vec1mod = entity():pos() - Thrust1:entity():pos()
 else{stoptimer("vecfinder")}} 
 
interval(50) 
	Alt = ranger(1000) 
	VecBase = entity():pos() 
 
	THoverZ = 30 - Alt:distance() 
 if(Alt:distance() != 30){ 
 interval(15) 
		HovAlt = Alt:distance + (THoverZ/8)} 
 
	Vec1 = -(VecBase + Vec1mod):setZ(HovAlt) 
	Vec2 = -(Vec1 + Vec2mod):setZ(HovAlt) 
	Vec3 = -(Vec1 + Vec3mod):setZ(HovAlt) 
 
	Thrust1:setVector("Vector",Vec1) 
	Thrust2:setVector("Vector",Vec2) 
	Thrust3:setVector("Vector",Vec3)

Notes: This code does not support thruster-based turning itself, but I'll release one with turning at some point.

------------------------------------

Vector Triad calculator Mk-II
Effect: Same as the Mk-I, but now you can attach a wired laser receiver and have the location basis of the vector thrusters be wherever you last pointed, so you can move it around the map. Perfect for, say, a remote baggage handler or somesuch.

Application: As with the Mk-I, except you can also wirelink a wired laser receiver to the Laser input of the expression chip.

@name	Vector Triad calculator Mk-II
@inputs	Laser:wirelink Thrust1:wirelink Thrust2:wirelink Thrust3:wirelink
@outputs
@persist	Vec1mod Vec2mod Vec3mod
 
if(first()){
 timer("vecfinder",10)
 if(Thrust1 & Thrust2 & Thrust3){ 
			Vec2mod = Thrust1:entity():pos() - Thrust2:entity():pos()
			Vec3mod = Thrust1:entity():pos() - Thrust3:entity():pos()
			Vec1mod = entity():pos() - Thrust1:entity():pos()
 else{stoptimer("vecfinder")}}
 
if(Thrust1 & Thrust2 & Thrust3){
 interval(10)
		Alt = ranger(1000)
 if(Laser:number("Active")){
			VecBase = vec(Laser:number("X"),Laser:number("Y"),0)
 else{VecBase = entity():pos()}
 
		THoverZ = 30 - Alt:distance()
 if(Alt:distance() != 30){
 interval(10)
			HovAlt = Alt:distance + (THoverZ/8)}
 
		Vec1 = -(VecBase + Vec1mod):setZ(HovAlt)
		Vec2 = -(Vec1 + Vec2mod):setZ(HovAlt)
		Vec3 = -(Vec1 + Vec3mod):setZ(HovAlt)
 
		Thrust1:setVector("Vector",Vec1) 
		Thrust2:setVector("Vector",Vec2) 
		Thrust3:setVector("Vector",Vec3)

Notes: Not much changed, but I'm not entirely certain of the vector co-ordinates acquisition from the laser receiver, it may not work because they're world co-ordinates being used in a vector, but the system should do something even if that's faulty.
The laser receiver is entirely optional, if you don't wire anything into the Laser input it'll work exactly the same as the Mk-I.

------------------------------------

Vector Triad calculator Mk-III
Effect: Exactly the same as the Mk-II, but now featuring a buddy system! The vector thrusters try to stay within 100-150 units of up to three buddies and reassigns buddies when it detects a fourth.

Application: Exactly like the Mk-II (Including the optional nature of the laser) except you need to attach a Locator to the contraption. No additional wiring is required beyond that of the Mk-II.

@name	Vector Triad calculator Mk-III			
@inputs Laser:wirelink Thrust1:wirelink Thrust2:wirelink Thrust3:wirelink			
@outputs 
@persist Num N M O Thrust Chips Vec1mod:vector Vec2mod:vector Vec3mod:vector Buddy1:entity Buddy2:entity Buddy3:entity VecPre:vector			
 
if(first()){ 
 timer("vecfinder",10) 
 if(Thrust1 & Thrust2 & Thrust3){ 
			Vec2mod = Thrust1:entity():pos() - Thrust2:entity():pos() 
			Vec3mod = Thrust1:entity():pos() - Thrust3:entity():pos() 
    Vec1mod = entity():pos() - Thrust1:entity():pos()}
 else{stoptimer("vecfinder")}} 
 
if(Thrust1 & Thrust2 & Thrust3){ 
 interval(10) 
		Alt = ranger(1000) 
 if(Laser:number("Active")){ 
    VecBase = vec(Laser:number("X"),Laser:number("Y"),0)}
 else{VecBase = entity():pos()} 
 
		THoverZ = 30 - Alt:distance() 
 if(Alt:distance() != 30){ 
 interval(10) 
			HovAlt = Alt:distance() + (THoverZ/8)} 
 
		Vec1 = -(VecBase + Vec1mod):setZ(HovAlt) 
		Vec2 = -(Vec1 + Vec2mod):setZ(HovAlt) 
		Vec3 = -(Vec1 + Vec3mod):setZ(HovAlt) 
 
		Thrust1:setVector("Vector",Vec1) 
		Thrust2:setVector("Vector",Vec2) 
		Thrust3:setVector("Vector",Vec3)} 
 
 interval(5000) 
 findInSphere(entity():pos(),200) 
 findClipToClass("gmod_wire_locator") 
 findSortByDistance(entity():pos()) 
 
 #DRONE DETECTION		
		TarProps = findResult(Num + 1):getConstraints() 
 
		N = TarProps:count() 
		O = floor(TarProps:count()/2) 
		P = O + 1		
 
 interval(10) 
 if(M != O|N != P){ 
 if(TarProps:entity(M):type() == Thrust1:entity():type()){ 
 if(Thrust == 3){Thrust = 3}
 else{Thrust += 1}}
 elseif(TarProps:entity(M):type() == entity():type()){ 
 if(Chips == 1){Chips = 1}
 else{Chips += 1}}
 else{M += 1}
 
 if(TarProps:entity(N):type() == Thrust1:entity():type()){ 
 if(Thrust == 3){Thrust = 3}
 else{Thrust += 1}}
 elseif(TarProps:entity(N):type() == entity():type()){ 
 if(Chips == 1){Chips = 1}
 else{Chips += 1}}
 else{N -= 1} 
 
 if(TarProps:entity(P):type() == Thrust1:entity():type()){ 
 if(Thrust == 3){Thrust = 3}
 else{Thrust += 1}}
 elseif(TarProps:entity(P):type() == entity():type()){ 
 if(Chips == 1){Chips = 1}
 else{Chips += 1}}
 else{P += 1} 
 
 if(TarProps:entity(O):type() == Thrust1:entity():type()){ 
 if(Thrust == 3){Thrust = 3}
 else{Thrust += 1}}
 elseif(TarProps:entity(O):type() == entity():type()){ 
 if(Chips == 1){Chips = 1}
 else{Chips += 1}}
 else{O = O - 1}}
 else{Ident = Chips + Thrust} 
 
 #BUDDY GENERATION			
 if(Ident == 4){ 
 if(!Buddy1){Buddy1 = findResult(Num)} 
 elseif(!Buddy2){Buddy2 = findResult(Num)} 
 elseif(!Buddy3){ 
			Buddy3 = findResult(Num) 
    Num += 1}}
 else{Num += 1} 
 
 #BUDDY DISTANCE MONITOR			
 if(Buddy1){ 
 timer("buddy1",100) 
		VecPre = VecBase		
		Bud1Dist = entity():pos():distance(Buddy1:pos()) 
 
 if(Bud1Dist > 150){VecBase = Buddy1:pos()} 
 elseif(Bud1Dist < 100){VecBase = -Buddy1:pos()} 
 else{VecBase = VecPre}} 
 
 if(Buddy2){ 
 timer("buddy2",100) 
		VecPre = VecBase		
		Bud2Dist = entity():pos():distance(Buddy2:pos()) 
 
 if(Bud2Dist > 150){VecBase = Buddy2:pos()} 
 elseif(Bud2Dist < 100){VecBase = -Buddy2:pos()} 
 else{VecBase = VecPre}} 
 
 if(Buddy3){ 
 timer("buddy3",100) 
		VecPre = VecBase		
		Bud3Dist = entity():pos():distance(Buddy3:pos()) 
 
 if(Bud3Dist > 150){VecBase = Buddy3:pos()} 
 elseif(Bud3Dist < 100){VecBase = -Buddy3:pos()} 
 else{VecBase = VecPre}}

Notes: The chip tracks three buddies, and if it finds another it resets all buddies and selects the three nearest to be buddies. That's important to know if you want to have like a large "herd" of buddy contraptions.

[Lyinginbedmon]

Miscellaneous expressions

Archer entity tracker Mk-I
Effect: Use this neat little chip to track the whereabouts and movements of the entity closest to it at activation, around corners and over far-spanning maps with no problem.

Application: Spawn the chip and wire two buttons (On = 1) to the Record and Output inputs. Turn Record on (And Output off) to start tracking the input entity (And entity marker helps but of course there are other ways).

@name	Archer entity tracker Mk-I		
@inputs	Record Output Target:entity 
@outputs	Vector:vector
@persist	Target:entity Path:array Index Body:array 
 
if(Record & !Output & Target){ 
 interval(100) 
	Path:setVector(Index,Target:pos())
	Index++}}
 
if(!Record & Output){ 
	Index = 0		
 
 timer("vector_output",100) 
 if(Index != Path:count()){ 
			Output = Path:vector(Index)
			Index++}
 else{stoptimer("vector_output")}

Notes: You may wonder how tracking the entity's position every hundred milliseconds is better than simply keeping it's position as an output. Well, for one, you can't really record a constant output, just use it for target setting or such. For another, if you send a typical seeker bot after a target that goes into a building, it'll probably keep running into walls for eternity. If you fed the output vector into the vector base of the vector triad calculator, however, it would follow the path made by the entity, which in most instances means it would go down corridors, around corners, etc. without issue.
With a little ingenuity, you could recode the output to go to the end of the array and then reverse, producing a recurrent loop that could be used for telling simple bots to follow a complex looping path.

------------------------------------

Hecate entity tracker Mk-I
Effect: Outputs the location of the prey entity (Fed into the expression via ranger or another expression for finding the prey entity), the distance to it, and the number of NPCs and players within 400 units of it. This handy little tracking device can also wirelink to a cam controller to give a tracking view of the prey.

Application: Spawn the chip and feed it an entity through the Prey input. Wire screens to the Dist and Herd outputs, and the PreyLoc to a text screen. At your option, wirelink a cam controller to the Cam output.

@name	Hecate entity tracker Mk-I
@inputs	Prey:entity Cam:wirelink
@outputs	PreyLoc Dist Herd
@persist	Prey:entity GPS:vector Herd Dist PreyLoc:string
 
interval(500) 
GPS = entity():pos()} 
 
PreyLoc = Prey:pos():toString() 
Dist = GPS:distance(Prey:pos()) 
 
#NPCs	
findByClass("npc") 
NPC = findClipFromSphere(Prey:pos(),400) 
 
#NPCs	
findByClass("player") 
Play = findClipFromSphere(Prey:pos(),400) 
 
Herd = NPC + Play	
 
Cam:setNumber("X",Prey:pos():x()) 
Cam:setNumber("Y",Prey:pos():y()) 
Cam:setNumber("Z",Prey:pos():z() + 100) 
Cam:setNumber("Yaw",0) 
Cam:setNumber("Roll",0) 
Cam:setNumber("Pitch",-45)

Notes: A drone with this script is effectively equipped for hunting, so if you happen to survive an encounter, consider why they would let you live before fleeing back home.

[Lyinginbedmon]

Added the Lethe stealth grenade. It's a bit unusual for a grenade to do nothing harmful, but in this case it's really more like the Gmod equivalent of a smoke grenade. I think it has a lot of potential usages, such as in PVP or even RP.

Really looking for some responses on how well these codes work folks.

[Azrael]

WireLib.AdjustSpecialInputs(self.Entity, {"Mul", "X", "Y", "Z", "Vector"}, { "NORMAL", "NORMAL", "NORMAL", "NORMAL", "VECTOR"})

The Vector Thruster's Vector input is just called Vector.

Anyway, great job. Especially with the vector triad calculators, that's a pretty neat method. I think you have a typo (due to renamed inputs maybe?) in your triad code:

if(V1 & V2 & V3){

Those three variables aren't defined anywhere else.

[Lyinginbedmon]

Anyway, great job. Especially with the vector triad calculators, that's a pretty neat method. I think you have a typo (due to renamed inputs maybe?) in your triad code:

if(V1 & V2 & V3){

Those three variables aren't defined anywhere else.

Yeah, initially I named them V[X] for simplicity, but later changed it to Thrust[X] for user comprehension.

[eduardo]

your awesome lying in bed

[Lyinginbedmon]

I've added the Caduceus teleportation protocol, which teleports the contraption a random distance (Between 150 and 200 units) and direction whenever it detects an RPG round within 75 units.

Once it's expanded to include Cycnus missiles and explosive barrels travelling at velocity, it's intended to be the defensive protocol for the Hermes drone (The only drone currently designed with a hoverdrive core).

[BlackholeWM]

Your stuff is always so awesome. I envy you.