What's new in Club v0.1.3

🖱️ Item Scrolling — beta

Move items with the mouse instead of clicking them one slot at a time.

• Scroll a slot to move one item · Shift the whole stack · Ctrl every stack of that type · Ctrl+Shift the whole inventory · Shift+drag across slots to move each one you cross.
• Every control is rebindable — choose the modifier and the button for each action on its own screen. No two actions can share one: assign it to a second and it leaves the first, and the row tells you.
• When a control would override something vanilla already does with it — Shift+click is the game's own quick-move — the row says so, instead of quietly swallowing the click.
• It ships as beta while it settles: it doesn't reach the creative inventory yet, and the card admits that rather than pretending to work.

🎛️ Settings that belong to their card

Right-click a module and its settings unfold right under that card, sliding the cards below it down to make room — the sheet never covers the grid. It's the width of its card, its controls squeeze to fit, and a name too long to fit is shortened, not spilled. A module with nothing to configure no longer opens an empty panel — it flashes a small crossed-out gear and leaves the card where it was.

👁️ Club stops drawing what you cannot see

• Particles behind the camera are no longer built. Minecraft culls particles not at all — it tessellates every live one every frame, the ones behind your head included. Nothing on screen changes.
• Block entities off-screen inside a section the frustum kept stop rendering — while anything that asked for special treatment (a beacon's beam, an end gateway, a moving piston) is left untouched.
• Measured on a fixed-seed scene, interleaved in one session: −5.3% frame time on a normal machine, −8.1% on a CPU-bound one. Where the GPU is your bottleneck, our own benchmark refuses to claim a win — and says so.

🔋 Background throttle

Cap the frame rate while the window sits behind something else. It gives zero in-game FPS — a battery, fan-noise and second-monitor feature, and calling it an FPS boost would be a lie. It can never raise a limit you set yourself.

📊 A cheaper, tidier HUD

The HUD's icons used to leave one GL call per sprite — a third of its whole cost. They batch now; not a pixel looks different, and every build proves that by geometry, not by eye. In the editor, elements refuse to overlap: drag one onto another and it slides along the edge instead of stacking, so nothing can hide under a neighbour or under the toolbar. The target chip's reach is fixed one step past vanilla's — a dial for it would name an opponent before you could touch them, and that's a soft cheat we won't ship.

What we didn't ship: an entity culler. It was built, measured at −22% frame time, and deleted — vanilla's visible-section list only holds sections that contain blocks, so a phantom in open sky belongs to none of them and would blink out while you watched it. If you want that, run Sodium (it owns the occlusion graph) with EntityCulling on top; we don't duplicate them.

Client-side only · works on vanilla servers · needs Fabric API · MIT.