Interact with Entities using an Expression Gate (Like pressing E)

[Matthias]

Hi,

I searched a lot, hopefully enough, to say, that i havent found it.

I think it would be nice, to be able to interact with entities with an Expression Gate.
Especially, i wanted to design a Expression Gate, to switch the train-switches on gm_wireconstruct, without being forced to leave the Train.
But sadly i could not find a function like this.
Are there special reasons not to include it?

Greetings
Matthias

[Rybec]

You could always have a wired User that's been nocollided with everything, including the world via the Adv. Ballsocket method, then applyforce that to wherever you need it.

Or just have it follow the train and aim where you look, wire it to Mouse1 on the pod controller.

If you've never applyforce'd anything before, there's tutorials about and we can help you when you get stuck.

[Matthias]

But it would be nice anyway, to have something like entity():use()

(Maybe restricted in the range, from which you can use something)

[Matthias]

well... sry for doubleposting, but i want this thread moved to expression-gates-addons or added to public branch? *hope*

e2function void entity:use()
	if  not this then 
		return nil 
	end
	if  not this:IsValid() then 
		return nil 
	end
--	if (this.IsWorld()) then 
--		return nil
--	end	
--	if not validEntity(this) then 
--		return nil
--	end
	if this.Use and this.GetPlayer then
		this:Use(this:GetPlayer())
	end
end

feels like the first sensefull thing I did in life.

i think you can add this as entity.lua in your "\garrysmod\addons\wire\lua\entities\gmod_wire_exp ression2\core\custom"-folder or add this to entity.lua...

Greetings
Matthias

[Colonel Thirty Two]

1. Has no prop protection.
2. You check for this being valid twice.
3. You are passing the owner of the entity to Use and not the owner of the E2 executing it.

[Donkie]

1. Has no prop protection.
2. You check for this being valid twice.
3. You are passing the owner of the entity to Use and not the owner of the E2 executing it.

3 times, actually.

[Colonel Thirty Two]

Well, not 3 times. An entity can be something other than nil and still be invalid. But validEntity(E) does the same thing as E ~= nil and E:IsValid()

[Matthias]

i just wanted to provide the same security and "features" as the User-Ent does:

if (!trace.Entity) then return false end
if (!trace.Entity:IsValid() ) then return false end
if (trace.Entity:IsWorld()) then return false end
if trace.Entity.Use and trace.Entity.GetPlayer then
	trace.Entity:Use(trace.Entity:GetPlayer())

EDIT: Well... the IsWorld() is senseless in that case.
EDIT2: and the second valid-check - well you are right

[Colonel Thirty Two]

Well, the user is limited in that it is a beam; the one you made is unlimited.

[Matthias]

Then I'm open to suggestions, how to limit it.