All Classes and Interfaces
Class
Description
Registry for physics body types used in the mod.
Client-to-Server packet containing the player's current VR pose.
Client-to-Server packet requesting a grab action.
Client-to-Server packet requesting a release action.
Client-side data store containing VR-related information.
Registry for custom data serializers used in network synchronization.
Registry for mod events.
An abstract base class for bodies that can be grabbed by other bodies.
Base class for packets that involve hand interactions.
The main class for the InteractiveMC mod.
Utils for generating mod-specific identifiers.
Mixin that processes keymappings right before Vivecraft would perform its own checks.
Mixin that injects into Vivecraft's keybinding setup to register hidden keymappings.
Class containing all mod keymappings.
Central networking controller for InteractiveMC.
The central registry that lists all network packets used by InteractiveMC.
Manages the creation, tracking, and interaction of player bodies in the physics world.
Enumeration of player body parts that can be controlled and interacted with in VR.
Renderer for player body part ghost rigid bodies.
Kinematic ghost rigid body without any physics which will be used to be linked with dynamic rigid body via constraint.
Renderer for player body part rigid bodies.
A dynamic rigid body representing a player's body part (head, hands, etc.).
Tracker for monitoring the player's body movements in Vivecraft VR.
Stores all data that are used on both sides and equal on both sides and related to a player.
Handles player lifecycle events such as joining, respawning, and leaving the game.
A raw container payload that transports direct Netty ByteBufs through the Minecraft networking system.
Server-to-Client packet containing the result of a grab action.
Utilities for interacting with Vivecraft without using the API, as it lacks the necessary functions.
Registry for Vivecraft related things.
Represents the VR data of a player in the Vivecraft mod.