Rust Dev Tracker

I try and avoid p2w the slot thing was an oversight and I think a minor one in the grand scheme of things but we are working on a solution, unfortunately we aren’t sure if we can increase clothing slots to 8 without a wipe, we also can’t make it exactly like a wolf headdress because of no bandana and then it would be useless, so maybe we have to rework the art so it works with the bandana and it’s a 1:1 wolf headdress replacement, not sure yet but the tl;dr is p2w for this item was not by design (and I think slightly overblown at that)

EDIT: Good news, Taylor was able to modify it and I was able to make it a true wolf headdress replacement as it is now compatible with with bandana. It's stats have been modified accordingly. This is what it was supposed to be all along, just a tiny oversight regarding the slot, whoops.

https://rust.facepunch.com/blog/february-update/#fullscreenexclusive

Definitely expected to find this comment in this thread.

Did not expect to find a heartwarming comment like yours in this thread.

I think you should focus on optimization instead.

I hope you enjoy them. All programmers have been putting optimization work on hold for the last 3 weeks and spent all their time on learning how to create 3D models. I think the new palms and hemp really demonstrate it was all worth it.

You rang?

All of those "27 new stable versions on the Unity site" are more broken than the one we are currently on. Yes, we've tried them all and reported every game breaking bug to Unity. The only good news is that there is a slight chance one of the next 2018.3 releases will allow us to upgrade.

Absolute unit.

This most likely means the server has not updated yet.

https://www.reddit.com/r/playrust/comments/a6zj48/hqm_upkeep_postmortem/

https://www.reddit.com/r/playrust/comments/a6zj48/hqm_upkeep_postmortem/

Since many people have been wondering about this bug and why it took us so long to address it, here's a quick post-mortem.

• The bug was relatively rare and our testers were unable to reproduce it altogether
• When it happened to a base and we checked that same base we couldn't reproduce it there anymore either
• I went over the tool cupboard code about 5 times and did not find anything wrong with it

The thing that finally gave us a lead was that Alistair noticed that sometimes when repairing an item in his base he could briefly see the base decay message pop up when he interacted with the tool cupboard immediately afterwards. When reproducing this in the editor I could also sometimes see resources that should not be there pop up in the upkeep cost overview for a brief moment, which was no the case in the standalone build. The same weekend we received a video of a clan reproducing it by repairing an item with the repair bench in their base.

Although there is no way to exploit this in a targeted way we'd like to give server owners some more time to update before we post any details.

It was a doozy. Maybe after the fix has been rolled out

I agree, and I think this should be a thing. I'll look into it early next year

Patch on Thursday will fix this issue- it currently only displays the output of the battery, so if it isn’t powering anything it’ll read 0 even for the input

Server out of date

It should be fixed on staging, (along with a lot of battery issues) so you can combine root combiners and will go live this Thursday with the xmas patch

try increasing ioentity.framebudgetms to 10 and decreasing ioentity.responsetime to 0

also lets see what it looks like under the hood!