The Build A Boat For Treasure Property tool edits values supported by the selected object. A normal block and a mechanical part may expose different fields. Work on a copy, change one value, and verify the result in the current server before applying it across a saved vehicle.
Verify the live unlock
Check the Shop for the current tool name, description, availability, and Gold price. Historical community pages have listed a price, but the number shown in the running experience is the purchase authority. Make sure the next build actually requires a property change before spending progression currency.
Equip the tool and place one disposable test block away from the build. Save the working vehicle. This test area becomes the reference for every unfamiliar field.
If the panel shown in a video differs from yours, follow the current field labels rather than an older menu position.
Select a compatible object
Choose the object and confirm its highlight. Read the entire property panel before changing anything. Some fields appear only for particular mechanical or interactive parts, so a missing option may mean the selected object is incompatible rather than the tool is broken.
On crowded builds, isolate or recolor the target. Avoid starting with a multi-selection. A batch property change can alter hidden blocks and make the failure difficult to trace.
Keep a note of the original value or preserve the saved checkpoint before editing.
Test appearance fields
Community documentation has described fields such as transparency and shadow behavior for supported parts. Change appearance on the test block, rotate the camera, and view it in different lighting. Confirm whether the part remains selectable and visible enough for future maintenance.
An invisible component can be useful in a designed mechanism but frustrating to debug. Mark its location with a temporary visible guide until the build is finished.
Appearance does not prove physical behavior. Test collision and stage interaction separately.
Test collision and anchoring
If the current panel provides collision or anchoring controls, change only one of them on the copied part. Walk or move another object against it, then launch or activate a minimal test. Record what changes and what does not.
Community reports warn that disabling ordinary collision does not necessarily remove every form of stage damage or special interaction. Do not use a visual pass-through test as proof of invulnerability.
Anchoring can prevent expected motion or cause a mechanism to remain fixed. Check the launch state and connection to nearby parts before using it in a vehicle.
Edit mechanical values
Compatible hinges, pistons, motors, wheels, and other special parts may expose object-specific values such as direction, speed, force, range, or delay in the current version. Build one fixed mount and one moving element. Adjust a single field by a small amount and activate at a safe distance.
Watch the full motion path. More speed or force can damage the mount, destabilize the vehicle, or make a control harder to stop. Correct direction and range before adding power.
Do not copy a numeric value across different part types without a live comparison.
Apply a property to a real module
After the sandbox result is repeatable, duplicate or select one noncritical module in the build. Save under a new name. Apply the confirmed value and test the module alone before launching the complete vehicle.
Inspect nearby objects for accidental selection. Verify the mechanism at inactive and active states. If the property affects collision, test player movement and part movement separately.
Only then repeat the edit across mirrored or duplicated modules.
Use properties in route builds
Keep structural survival independent from experimental appearance where possible. The seat cage and spine should remain understandable even when panels are transparent or nonstandard. Do not hide every connection until the boat has completed several routes.
For stage clearance, a non-colliding or transparent surface still needs testing against current hazards. For waterfall survival, confirm the avatar, seat, and structural core remain connected under load.
Use the Obstacles guide to identify the failure before changing a property.
Recover from an unexpected result
Restore the original value if it is known, use undo if the current interface supports it, or reload the saved checkpoint. If the object cannot be selected after an appearance change, approach from a clearer angle or expose it by temporarily removing surrounding parts.
If a mechanism freezes, check anchoring, collision with armor, direction, and motion range one at a time. If a whole build changed, return to the pre-batch save and reproduce the edit on one part.
Avoid stacking new property changes on top of a result you do not understand.
Document version-sensitive values
Record the review date, object name, original value, changed value, observed result, platform, and whether the behavior persisted after launch. This turns a vague tutorial into a reproducible test.
Recheck after updates. Current fields can be renamed, added, removed, or rebalanced. A value that worked for one part or client version is not a permanent rule for every build.
Evidence status: the Property tool and its live panel are Official when shown in the experience. Common use cases and historically documented field families are Community corroborated. Current unlock price, exact field list, value limits, collision exceptions, and mechanical results are Needs in-game testing.