Menü
Testing strategies and infrastructure for game entity behavior in perovskite_game_api. Use when asked to write tests for entities, including animals, minecarts, etc.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Advanced block functionality, event handlers (dig, tap, step-on, interact), extended data (simple_data, inventories, custom protobuf data), client extended data, and block mutation APIs. Use alongside define_new_block. Does not cover timers or circuits.
Defines a new block using BlockBuilder. Use this when asked to add a new block type to the game. Also provides guidance on textures.
Testing strategies and infrastructure for game block behavior in perovskite_game_api. Use when asked to write tests for block placement, dig handlers, timers, inventories, or other game mechanics.
Ask the user to demonstrate in-game actions via the dev server when you need sample gameplay input, in-game builds, or other game input you cannot determine from code or prose text alone.
How to structure a new mod or subsystem in perovskite_game_api — registration pattern, GameBuilder/GameState extensions, BlockBuilder extension traits, and cross-mod ecosystem hooks.
Adds new types of UI controls to the game protocol, and implements the server and client-side logic for them. Use this when explicitly asked to add a new UI control type.
| name | entity_testing |
| description | Testing strategies and infrastructure for game entity behavior in perovskite_game_api. Use when asked to write tests for entities, including animals, minecarts, etc. |
Entity movement logic (EntityCoroutine implementations) is tested with CoroutineTester from
perovskite_server::game_state::entities::entity_test_helpers. It drives the coroutine
synchronously step-by-step inside run_assertions_in_server (which provides the required async
runtime).
use perovskite_server::game_state::entities::entity_test_helpers::CoroutineTester;
use perovskite_server::game_state::entities::MoveQueueType;
fixture.run_assertions_in_server(|gs| {
let start_pos = Vector3::new(0.0, 0.5, 0.0);
let coro = MyCoroutine { ... };
// Constructor calls advance() once; start_pos must be in a loaded chunk
let mut tester = CoroutineTester::new(
Box::pin(coro),
MoveQueueType::SingleMove, // or Buffer8, Buffer64
start_pos,
gs,
).or_fail()?;
// Step one planned move
tester.advance(gs).or_fail()?;
// Inspect state
println!("pos={:?} buffer={}s engaged={}",
tester.current_position(), // position before current move completes
tester.move_buffer(), // total seconds currently queued
tester.is_engaged(), // false after StopCoroutineControl/ImmediateDespawn
);
// Position after all queued moves drain
let final_pos = tester.post_queue_position();
Ok(())
})?;
CoroutineTester::advance must run inside an async runtime because deferred moves call
tokio::runtime::Handle::current().block_on(...). The run_assertions_in_server closure already
satisfies this. The chunks around start_pos are warmed up automatically by each advance call.
See perovskite_game_api/src/animals/mod.rs for a full example (duck_coroutine_smoke).