I've always wondered why a server would intentionally disable something like this? What is the possible upside?
In this case, the server has issues with players being kicked by flyhack while using a modded teleport command. The quick fix for them was to completely disable server-side flyhack antihack and fix the underlying at a later date.
This server has disabled flyhack antihack.
Not possible on servers running default antihack settings.
We plan to address this issue in the near future.
Could you please put the person to last wound you second in that list?
Sometimes the cheater downs you and has his non-cheating friend finish you.
Yes
Cross-post from the Bug Reporting thread:
[BUG] After today's Halloween update you seem to have updated the UI for F7 reporting. While it seems to be an improvement for making bug suggestions or offering feedback, the "Report A Player" interface leaves a lot to be desired.
After wanting to submit a report for a potential cheater, I encountered the following:
Gone is the dropdown list of players in-game with the most recent offender at the top of the list. This has been replaced with a very pretty UI of all players in alphabetical order.
The most recent offender is not listed first, or at the top, so you have to hunt to find his name. This can be difficult if you have forgotten his name and have to browse through every name. It might not jump out at you straight away and can lead to confusion.
Looking through the names that were there I noticed a number of users from a server I was on previously -- not on my current server -- and who were not suspected cheaters in any sense. This contributes even more to the overall confusion.
After struggling to find the player who killed me using this new interface, I alt-tabbed out of Rust, launched Firefox, loaded battlemetrics, and looked through the list of players for the name I would recognize -- and I found him!
After tabbing back into Rust with the Report screen still up I found he wasn't even on the list at all, so I couldn't report him.
This new interface makes reporting suspected cheaters exponentially confusing and more difficult. I'm happy that hitting F7 no longer launches a separate web browser which hogs RAM, but not at the expense of making reporting difficult, if not impossible. Please take another look at this because in its current form, the F7 Reporting Interface is completely broken.
You should be able to click on "report player" on the death screen to report the player that killed you.
Failing that the last person that killed you should always be first in the list.
Would this require a server restart?
Server update which requires a server restart yes.
We've released a patch to resolve this issue.
[BUG] scientists can walk through closed doors on oilrig.
This is the current intended behaviour - We'll improve upon this in future updates.
[deleted]
We've now released a fix for this issue.
[BUG] Tools are not showing the relevant stats (img)
We've now released a fix for this issue.
[BUG] Bradley stuck at launch site. (on server im playing on it's stuck near the recycler)
Update - We've now released a fix for this issue.
[BUG] Now that horses have inventory slots you can use them to pass loot through walls you don't own. You just need to stick the head of the horse through a wall a little bit. (Similar to old BBQ exploit)
[BUG] You can push a player through an open door in a triangle airlock if you jump on their head.
Thanks, we'll take a look at this.
We've now released a fix for this issue.
[BUG] Map now doesn't work at all when spectating as admin. It was spotty in the past as it didn't update or allow you to move it around when spectating, now it won't come up at all.
We'll have this fixed in tomorrows hotfixes.
Afraid not for this update but they'll return next month!
Back at ya!
[BUG] Bradley stuck at launch site. (on server im playing on it's stuck near the recycler)
Thanks - we'll have this fixed in tomorrows update.
[BUG] Bradley is not moving at launch site
Thanks - we'll have this fixed in tomorrows update.
Update - We've now released a fix for this issue.
Opening map directly after respawning causes you to be disconnected from the server
Currently unable to replicate this issue, is it occurring on all servers and do you get an error message?
