libGDX Box2D gameplay
Connects physical contacts to game rules without changing the physics world at an unsafe moment. It separates world units from sprite pixels and makes damage or pickups safe against repeated callbacks.
libgdx-box2d-gameplay
See how it helpsWhen is it useful?
Use it when collision callbacks spawn or remove objects, or physical motion no longer matches the intended gameplay scale.
What does it help you do?
- Separates physical units and bodies from visual sprites.
- Queues world changes outside locked contact callbacks.
- Makes contact effects repeat-safe and disposes level-native resources.
Try asking this
In our platformer, destroy a breakable crate when a falling rock hits it. Queue removal outside the contact callback, spawn the reward once and restart the level. Verify sprite and body positions agree and the old level leaves no native physics objects behind.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
libGDX — box2d gameplay
Use when integrating libGDX Box2D bodies, contacts, joints or gameplay collisions.
Version and project gate
Inspect Gradle wrapper and modules, libGDX/backend versions, Java toolchain, ApplicationListener/Game/Screen structure, AssetManager ownership, viewport policy, native libraries and supported desktop/mobile/web targets. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Confirm the wrapper/native version, units and fixed-step owner. Keep visual sprites separate from bodies and queue world mutations outside locked contact callbacks. Turn contacts into idempotent gameplay events. Dispose World and associated native data with the level.
Deliver
A body/contact ownership map and a reproducible obstacle or combat scenario. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
Do not destroy a body inside a locked Box2D callback or treat pixel coordinates as sensible physical units.
Acceptance scenario
Trigger simultaneous contacts, despawn an object from a contact and reset the level without stale body references. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Keiko. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Task-specific official references
Included files 1
SKILL.md