Start here
Check whether the new Viewpoint update is on Workshop
As checked November 2, the original Workshop changelog still ends at alpha-0.1.6.1 on October 15. Today's new-feature video explicitly describes Discord testing. A preview or nightly collection is not proof Steam delivered the new core to you. Check the original item's change note and the version actually loaded in your game before changing companions.
On this page
Separate a preview, a mod release and the game build
Owen Oasis's November 2 preview shows inventory UI, sound, snow, building and other changes. Its description spells the version 0.1.17; current Workshop comments call the anticipated build 0.1.7. We have not authenticated or installed that test build, and do not resolve the naming difference by inventing a public release.
Use the original item 3809306528 and its Change Notes as the public-channel checkpoint. Recheck it when you act: this is a dated observation, not a promise the Workshop cannot update later today. A companion updated for a new core can appear before that core's public release.
The base game's Build 42 number, ZombieBuddy version, Viewpoint core and each companion are separate versions. A recent SteamDB base-game entry does not establish which renderer was installed.
Check what you have before trying an update
- Close the game and preserve the complete save. Note the game build, launch mode, loader/core versions and optional companions.
- Open the original Workshop item's latest Change Notes. Compare the release identifier with the tutorial or preview you followed.
- If you want the public channel, let Steam finish the intended download with the game closed. Do not substitute a similarly named upload or a comment's executable archive.
- Launch a separate test world. Check ZombieBuddy's loaded indicator and the installed Viewpoint version shown by its setup or runtime information; inspect relevant log lines if the display is unclear.
- Confirm O changes perspective, then test one required action before restoring optional companions. Download completion alone does not prove the new Java code loaded.
If you keep the current public core, you do not need to join a private test or unsubscribe a working installation to make the preview's date match your menu. For a missing original item, use the availability checks.
Do not remove half your mod list based on a preview
Compare each companion's actual supported core and feature. The current QOL description accepts 0.1.6.1 or 0.1.7, but distinguishes its experimental world actions and Additional Features by core version. That is not certification of every other Java add-on, and a collection title is not a tested compatibility matrix.
Keep a small known-working test setup, add one intended feature and review a changed JAR's approval independently. For an unsupported-version message or absent bridge, use post-update loading checks. Record the real message rather than deleting every approval.
Creator titles advertise different FPS multipliers. We have no controlled benchmark and cannot promise a universal increase, especially in Louisville or a heavily modded hosted world. Compare the same route, resolution, preset and mod set with the FPS troubleshooting flow.
Sources & version
Based on author documentation and community instructions, not our own gameplay test. Later updates may change defaults.