Choose a minimal Viewpoint mod list for Build 42

Establish the smallest working camera setup

Use the original ZombieBuddy item and Viewpoint item, including the loader setup for your platform. Subscribing and enabling are separate steps. Check the installed release's required-items panel before relying on someone else's older collection.

1. Back up the world and note the existing game build, mod list and launch method.
2. Use a separate test world. Complete the platform-specific installation and review the intended Java files.
3. Confirm the loader indicator, then that O changes perspective.
4. Keep this working list as your comparison before adding companions.

If the camera fails at this stage, fix that prerequisite first. A new shader, object pack or inventory overlay cannot prove the underlying Java agent started.

Choose companions by the task you want

For example, camera plus object models is a narrower goal than camera plus new controls and regional weather. This is a way to choose features, not a claim that we benchmarked either combination.

Validate each addition before keeping it

1. Record the original Workshop item, required items and version. Enable the chosen companion after its prerequisites.
2. Restart and review any new or changed Java approval. Confirm its actual loading state.
3. Repeat the companion's intended action in the same test world, not merely the base camera switch.
4. For input mods, rehearse both the new action and the vanilla action it displaces. K, V and E have different meanings across companions.
5. If the test fails, preserve the log and compare with the last working test stack before changing another variable.

A loaded JAR does not establish correct object rendering, server agreement or stable frame rate. Keep the exact failed action with your notes rather than calling the whole collection broken.

A client mod list is not a complete server setup

Keep Workshop IDs and Mod IDs in their respective lists. Each player's Java loader and approvals still matter. Simple Mod Check is an optional consistency tool; it is not a dependency that makes every rendering stack compatible.

Before adding weather Gameplay or changing a shared world's rules, agree on the intended behavior and follow the client/server checklist. Keep an unchanged world backup. Stop at an unmet dependency or unsupported platform rather than filling the gap with an unverified repack.