Vibing
About this stream
The video appears to be a talk or presentation about a multiplayer persistence-based game architecture. It emphasizes not coupling gameplay systems with back-end details, promoting abstractions, adapters, and an authoritative server model, and warns against trusting the client for core state like inventory, crafting, resources, and progression. The game world is persistent and multiplayer, featuring a central protected city as a social/economic hub, with a larger wilderness containing resources, roads, forests, mines, farms, NPC settlements, bases, and high-value locations, not just a match-based extraction game. The vibe is technical and design-focused, reiterating core concepts across repeated segments.
Written by AI from the stream.
Transcript (AI, 10 lines)
to the protected city.
The basic macro loop is, safe city, prepare, explore, gather scavenge fight, dive, extract
or return, secure value, create a fizz gun style interaction system.
Players must eventually be able to grab physical props, move them, rotate them, precision
rotate them, freeze unfreeze them, place them, snap them, free place them, and create constraints
between compatible objects.
Master constraint types should include concepts such as weld, hinge, slider, rope, spring,
motor, axis, and other sandbox constraints.
Do not hardcode these into one giant fizz-gut building system, a conventional rust clone,
where the gen magically constructs structures.
Comments
No comments yet.
Join the discussion on OpenVibe.Community