Alistair_Mc

This was resolved in our testing in the March update: https://rust.facepunch.com/news/march-2022

• Fixed phantom footsteps continuously playing

• Fixed incorrect sfx footsteps playing

If others report this is still occurring we'll reinvestigate.

It's fixed, changelist note "Fixed several overly strict antihack configs resulting in unable to damage construction"

Facepunch Staging is online, you need to use the Rust - Staging client version which is available from your Steam library.

We have two versions of Rust, the Release version - which is the common version that everyone plays.. and Staging - which is the development version.

The Staging version has all of our latest changes, but might have bugs. The Release version is the most stable version - and at any one time should be the most bug free.

You can install the Staging Version of Rust like the regular version. If you own Rust you should see "Rust - Staging" in your games list.

The staging version isn't always compatible with the Release version, so you won't be able to join Release servers in the Staging version at times.

We're rolling back today's update now to resolve this issue, a new update should be available on Steam.

We're aware some players are experiencing crashes after today's update, we've identified the issue and will be releasing a fix in 50mins.

We're continuing to look into this issue.

Apologies for the inconvenience.

Please can you post your system details?

We've identified the issue and will be releasing a fix in 50mins.

Apologies for the inconvenience.

Looking into this currently.

We've identified the issue and will be releasing a fix in 50mins.

We're continuing to look into this issue.

Apologies for the inconvenience.

morning

The player was never unbanned, the player received a 48-hour temporary game ban which doesn't display on the Steam profile and then 9 hours later the ban was switched to a full game ban which does display on the Steam profile.

Thanks for the report, we're currently investigating this issue.

Thank you - we've now got this fixed internally now, expect to see this fix live in the near future.

This is a problem with Oxide. Oxide is a third party modding platform, they've pushed a fix for this issue - You'll need to inform your server owner to update their Oxide version to the latest.

We're aware AMD GPU users are experiencing degraded performance with the latest update, we hope to have a fix ready within the next 50 minutes.

Please can you list your system hardware? CPU and GPU.

Update - we've got a fix building currently, ETA 40minutes.

Update - We've now released a fix.

Thanks for the report, we're currently investigating this issue.

Thanks for the kind words Nordee and an additional huge thank you for your continued bug reports from Staging.

While we're not robots, we as game developers need to be open to criticism, whether the criticism is beneficial or not we need to always learn and listen from the Rust community, we need to try to balance our vision of the game with that of the Rust community. If we ignored the Rust community and never addressed concerns, it's my belief Rust would likely be in its grave by now.

Reddit at times can have a loud minority, sometimes the most upvoted opinions here are greatly different to that of other Rust communities. We're going to make mistakes from time to time and we'll learn from that and take that experience with us as we move forward.

We're going do stuff that makes zero sense, sometimes we're going push the boundaries a little and experiment which is going upset people. Be sure to tell us when you think we've messed up but also be open to us...

Thank you for the report - will fix.

If this occurs then there was no valid mission spawns, try another fishing village. This will normally only affect "small" maps.

Your criticism is valid, we've done a poor job of following up on this bug.

I promise we'll make a greater effort of looking into this over the coming days.

Noted.