04-30-2014, 03:19 PM
(This post was last modified: 09-01-2022, 01:03 AM by Fearless Community.
Edit Reason: Checked Encoding
)
(04-30-2014, 08:04 AM)Temar Wrote: What exactly would a staff member figure out by checking him selfVariables not applicable to an automated system? As mentioned previously: Mingebag Underground. Users which openly support double accounters, banned users, and otherwise coming into the server to create havoc. The solution is to have admins study the players the double accounters frequent the most, and if these users are handing them large sums of money, weapons, ammo, cars, and otherwise without any real reason... You have just discovered a Mingebag Underground: By shutting it down you solve the problem of double accounters getting banned, and coming back and have a source of money and weapons.
(04-30-2014, 08:04 AM)Temar Wrote: Player logs on and staff get alertedThe conclusion is not to look for Double Accounters, but instead look for players involved in much more serious rule breaking. Players that openly give hackers, double accounters, and otherwise the means to break rules and create havoc.
They check the ban etc and pretty much always come to conclusion of double account
How exactly are they going to not see this
(04-30-2014, 08:04 AM)Temar Wrote: They are obviously linked as using same gmodBut you do have the tools to adminstrate the logs, cloak and follow the player on server, and then study the user's activities with good ol' fashion pen and paper. Think of it like a Cop RP. You are investigating a murder, and in order to book someone, you need more evidence.
We can't exactly goto there house to investigate
(04-30-2014, 08:04 AM)Temar Wrote: The only thing a player would have to support him is playtime while no banBut that player isn't the one you should be after. If players know of a double-accouters existence, and are not reporting it, and handing them weapons and money... Who is the more serious offender that should be dealt with?
![[Image: EglEnZU.gif]](https://i.imgur.com/EglEnZU.gif)