Rust: Printed and Polished

The update in a minute

Tech trees use fragments, pages and books; workbenches need no fragments. Scrap research remains. Prototype: 25% success, no doubled cost. Folded Uzi: automatic, shield-compatible; unfolded: semi-automatic, more accurate.

Added: Steam Input, shears, wool insert, birds and mirrored stairs (Shift+R). Repairing a lighthouse opens Deep Sea. Staging: ~1.6 GB less memory, up to 25% less traffic (500-player server). Network LOD: limited rollout; base occlusion and Workshop texture streaming: in development.

Choose one unlock before planning the farm

Write down the item you actually want to make. Compare the full route to that item, including prerequisite unlocks and the ingredients you will need afterwards. A cheap unlock is not useful if it leaves you unable to craft it.

The Research Table uses a found item and Scrap to make its blueprint. Check whether you already know the recipe before spending anything: the item blueprint and your learned crafting knowledge are different things. A physical blueprint can also have a separate use in industrial crafting.

A chance is not a schedule

Do not budget as though every fifth use must preserve a blueprint. With independent attempts, the probability that all five consume it would be 0.8⁵ ≈ 32.8%. A short unlucky streak is compatible with that chance.

Keep enough resources to continue without a lucky outcome. Anything preserved can fund the next unlock.

Try the Uzi before committing a loadout

Use a practice environment to answer a practical question: which setup can you control reliably? Keep ammunition, attachments, target distance and sensitivity unchanged while comparing setups. Record hits and recovery between shots, not just how fast you can fire.

1. Check the binding

   Find the fire-mode control in your own settings and practise switching without looking away from the target.

2. Repeat the same exercise

   Use the same target and distance for several short attempts. Avoid comparing your best run with your worst one.

3. Account for the whole kit

   Before taking it out, check your ammunition, protection and replacement budget. A comfortable setup is more useful than a statistic you cannot reproduce.

Measure your FPS, not someone else’s headline

A test result is not a promise for your PC. Server population, nearby buildings, graphics settings and background applications can change the outcome. Check frame pacing alongside average FPS.

1. Keep the comparison fair

   Use the same server, location, resolution, graphics settings and FPS cap. Note the population and whether the scene has changed.

2. Warm up, then repeat

   Load the area first. Walk the same short route three times, keeping the duration similar. Save your results rather than relying on memory.

3. Look beyond the average

   Compare frametime spikes and low-FPS moments as well as the average. Keep a separate note of memory use and visible stutters.

4. State what you can conclude

   If you have no comparable recording from the previous build, describe current performance. Do not label a difference between two unrelated sessions as the patch’s FPS gain.

A short checklist before your next session

• Check the selected server’s rules and wipe information.
• Choose one useful item to unlock and inspect its requirements in the current game UI.
• Separate resources for unlocking from materials for crafting and replacing your kit.
• Test unfamiliar controls somewhere you can afford mistakes.
• Use the full official changelist below for changes outside your immediate plan.

Check the date before trusting a recipe table

On 10 November, the official wiki’s Workbench Level 2 recipe still listed Basic Blueprint Fragments. That table has not caught up with the release announcement. Check the cost of your next action in the current game UI; use the wiki links below for background on research and industrial crafting.