Moderation features that Cove seem to be capable of, but dont utilize.

[Fleur-Bot]

Hi there!

When it comes to server moderation the biggest issue i run into is the lack of features to gather steam profiles or steam ID's.
Especially so when a culprit has already left.

It is incredibly common in this game for some player to log into your server, ruin all the art with bunch of chalk and leave.
Now if this player was on i could simply ban them and it would automatically find their steam id for me.
But when they're already logged off, well i have chalk logs, previous people who joined, and chat logs of them joining all with timetamps.
But no actual steam ID's which is what Cove requires to do a ban. I can pick out who was the culprit pretty easy.

but then am able to do nothing against them. Searching up their names on steam is a hassle and often has no results Names are common, obfuscated or just arent found in the search feature. But Cove has no way of recovering someones steam ID when they've already left.

Can we not generate some kind of Playerlist.txt file? That works similarly to the !prev command but it just logs everyone who joins, adds their username as it shows in our console, and adds the steamID behind it?

And additionally a way to get the steamID immediately of an online player, like if i typed '!steam Fleur' or '!steam X9Z' (auto-generated code) it would give my SteamID as a console result immediately without the need of banning them?

I'd really love some extra moderation features as currently griefers are running rampant with almost no way to enact consequence.

[DrMeepso]

I've added !steam to the most recent version dl. for previous players / players who have quit try the !prev command, it SHOULD list players that have left and their ID's that you can then use to ban them even after they have left (I've heard it okay at its job). I have a few ideas for new moderation things but im swamped by school right now so it might be a while before I can implement them.

[binury]

On a side note, Steam does implement this functionality if you look at game info > recently seen players. If you are using Socks, I have patched this feature into Webfishing client for consistency.

[Fleur-Bot]

I've added !steam to the most recent version dl. for previous players / players who have quit try the !prev command, it SHOULD list players that have left and their ID's that you can then use to ban them even after they have left (I've heard it okay at its job). I have a few ideas for new moderation things but im swamped by school right now so it might be a while before I can implement them.

The !steam implementation will definitely be helpful i will give it a try.

I have tried the !prev command before, however the 3 character alphanumeric code has never worked on banning someone thats already gone for me. People have also left usually too long ago for them to even show up in !prev, i mostly learn about people i should ban through my community opening tickets but they often forget to get a steam profile which is why that playerlist would be helpful, so even if i want to ban someone days later, i can always find them back.

On a side note, Steam does implement this functionality if you look at game info > recently seen players. If you are using Socks, I have patched this feature into Webfishing client for consistency.

I haven't had this feature work for me, i also do have Socks. But the recent tab has never showed me any players i played with so im not sure what's up with that, though even if it did, I'm mostly looking for features to help ban people after the fact when they're already gone, and that's often a player i didn't even play with myself, but rather got reported by a community member, so they wouldn't be in the list regardless.

Thanks for the help though

[Fleur-Bot]

I have tried out the new !steam feature, but similarly to other moderation capabilities. This also only works while the player is still online, so it helps little in punishing griefers that have already left.

I have also attempted once more to ban someone using the codes given in !prev, but this indeed does not work for me.

[binury]

for the meantime, i have found this API useful for finding an ID

[Fleur-Bot]

for the meantime, i have found this API useful for finding an ID

Yes indeed. though, even then i would still have to find the actual correct steam profile hence my preference for cove saving all previous players somewhere

as i mentioned here

Searching up their names on steam is a hassle and often has no results. Names are common, obfuscated or just aren't found in the search feature. But Cove has no way of recovering someone's steam ID when they've already left.

meaning this will remain an issue even with that tool. As long as theres no way to find a history of players that were on your server, it will remain difficult to moderate it, because its incredibly uncommon you just happen to find the right player on steam to trace their steamID, and alot of griefers use obfuscated or spoofed names, or names with special font characters that you cant exactly type in a search bar. Making it impossible to find them without a full player history.

[binury]

Can we not generate some kind of Playerlist.txt file

Since usernames on Steam are not unique it is not possible to keep a useful map of name -> steamID as you have described. (There would be no way to distinguish identity between two or more players who share the same name)

As a workaround when retroactively banning you can consult the log of the incident and reference the join message which includes the player's ID.

On a related note, a player DB for logs/stats/plugins is a planned feature and could be utilized to track down players since entries would include distinguishing info.