Logbook is a menu in Scrap Mechanic.
Overview[edit | edit source]
Usage[edit | edit source]
Once obtained, the Logbook can be opened by pressing L. Press Escape or L to close it. Clicking the "Beacons" button will list all of the Beacons in the world, where their waypoints can be toggled on or off. It also shows the distance to each Beacon in meters, where 1 meter is 4 blocks.
Obtaining[edit | edit source]
The Logbook is obtained from the terminal to the left of the cockpit in the Crashed Maintenance Ship after power has been restored.
Entries[edit | edit source]
Each entry in the Logbook is represented by an image. A waypoint can be toggled on the structure associated with an entry. Only one entry-associated waypoint can be active at a time.
Crashed Ship[edit | edit source]
Better keep the ship coordinates handy. Maybe I can get back here later when I can make her spaceworthy again.
Mechanic Station[edit | edit source]
Structure: The Mechanic Station that is nearest to the crash site, found to the northeast of the ship.
VESSEL STATUS - DISABLED. MISSION STATUS - ABORTED. CONTACTING WONK ENTERPRISES... CONNECTION FAILED. RETRYING... HULL INTEGRITY: 40% LIFE SUPPORT SYSTEM CAPACITY: 55% COMMUNICATION SYSTEMS INTEGRITY: 33% THRUSTER INTEGRITY: 12% FREE LUNCH DRIVE STABILITY: 5% POSSIBLE CAUSE: Kinetic impact/bombardment. Further results: inconclusive. CONCLUSION: VESSEL UNFIT FOR OPERATION. PLEASE CONTACT YOUR NEAREST Mechanic Station FOR ASSISTANCE
Upcoming[edit | edit source]
The Logbook will be used to track quests.
Trivia[edit | edit source]
- Before the Logbook was added, the in-game time was displayed in the top left corner of the HUD.
- The HUD element for the Logbook and its associated keybind were present before the Logbook itself was added.
- The Logbook uses the same animations as the Handbook.
History[edit | edit source]
Beta[edit | edit source]
Gallery[edit | edit source]
Issues[edit | edit source]
Guest players will be unable to obtain the Logbook after the host player interacts with the terminal. To avoid this, let all the connected guest players interact with the terminal first. This happens only once per session, so in the event that it does occur, the host should exit the world and start it again.