/id for props

[TooRaw 36]

Description: It is pretty much in the title. Staff is strongly encouraged to do /id on players to grab their steam id. It would be a very similar action but the only difference is being able to get the steam id of the prop owner. This will make life so much easier for staff (and is actually quite convenient). 

 

Reasoning: We all know the server can get chaotic, that's why we are here. Prop block is probably one of the highest reported rules (under rdm) that occur on the server. Being able to /id props will be very efficient. It could prevent the event of accidentally tping the wrong person (given that most names are complicated and/or common). These situations will occur when no one is reporting them. I find myself (as well as other mods) constantly taking these situations into our own hands, as it is basically game-breaking. In terms of coding it, it shouldn't be too hard at all. Being a coder myself, I could try and write the code, but I have never touched gmod and most likely don't know the language or the code files that are written in general. The variable of the prop owner is already existent. Not only is it in the admin logs, but it is also available to any user who has their crosshairs over the prop. This feature will not only save time, but prevent staff errors, helping keep the server great.

[ElCompadre 211]

+1

That's a good idea, it can help us banning people faster.

[Smitty 211]

+1. This is a good idea being that sometimes I get visual bugs and it doesnt say who’s prop I’m looking at

[BeMinxX 142]

+1 very beneficial 

[Shin_Tsukimi 2,246]

+1, if possible this would be incredibly useful for dealing with prop-related sits, as sometimes you can't see who owns what prop.

[BigA 132]

+1...don't see how this wouldn't be helpful and this would make it easier to deal with prop-related sits as shin mentioned!

[DiegoZavier 612]

Your suggestion has been Accepted

Please note that accepted suggestions will not necessarily be implemented into the server, but rather forked over to the development team for a second opinion, at which point they are free to choose between implementation or not.