Ideas for mouse binding

Advanced Camera & Mouse Input System (Suggestion)

Overview

Currently, MCreator provides limited access to camera control and mouse input handling in Minecraft.

This makes it difficult to implement:

• advanced camera systems
• FPS-like controls
• cinematic sequences
• precise direction-based mechanics

This suggestion proposes a set of new procedure blocks to expose and simplify these features.

Camera Control System

Proposed blocks:

• Set camera position (x, y, z) in space
• Set camera rotation (pitch, yaw)
• Attach camera to entity
• Smooth camera movement (interpolation / velocity-based)
• Reset camera to player

Use cases:

• Cinematics
• Custom perspectives
• Drone / spectator systems

Mouse Input System

Proposed blocks:

• Get mouse delta X
• Get mouse delta Y
• Detect movement direction (up/down/left/right)
• Invert mouse axis (horizontal / vertical)
• Adjustable sensitivity

Why this matters:

Mouse delta is already computed internally but not exposed.
Making it accessible would allow much more precise control systems.

Direction & Movement Utilities

Proposed blocks:

• Get angle between two directions
• Apply velocity relative to look direction

Benefits:

These operations are commonly needed but currently require complex workarounds.

Camera Effects / Vision Types

Proposed features:

• Custom camera effects (distortion, overlays, etc.)
• Ability to switch camera rendering style

Inspired by existing behaviors in Minecraft (e.g., entity-based visuals).

Safety & Reset

Proposed blocks:

• Reset camera to default
• Reattach camera to player
• (Optional) Undo last camera modification

Importance:

Prevents players from getting stuck in broken camera states.

Technical Notes

• Most of these systems already exist client-side in Minecraft:
  • Camera transformations (spectator mode, entity views)
  • Mouse input deltas
  • Directional vector math

This means the feature would mainly involve exposing existing functionality, not creating entirely new systems.

• Mouse input should remain client-side only to avoid desync issues
• Camera control could hook into existing render/view logic
• Vector math blocks would be lightweight wrappers

Performance Impact

• Mouse delta access: negligible (already computed each frame)
• Camera updates: already part of render tick
• Math operations: minimal cost

 Overall impact should be very low.

Why This Would Be Valuable

Adding these features would:

• Greatly expand what can be created in MCreator
• Reduce the need for custom code or external APIs
• Enable entirely new types of mods:
  • FPS systems
  • Cinematic tools
  • Advanced abilities
  • Custom control schemes

Summary

This suggestion focuses on exposing and structuring existing client-side systems to make them usable through procedure blocks.

High impact, relatively low implementation complexity, and strong benefits for advanced creators.