Player Fish

Runs when the player fish interaction occurs for an eligible participant/entity in the plot.

Selection

Event → Choose Operation → Player → Interactions & Blocks → Player Fish. Configure with Dev access and compile.

Target context

Default Event Target has declared type player. Only values actually supplied by this event are available.

Available data

Use Game Values and Target Objects appropriate to this event. Unavailable event data reports an error rather than silently producing a usable default.

Example handler

Event: Player Fish
  Call Method → Event Target → Send Message
    Message: Player Fish observed

Declare any Public destination first. Test by performing the described interaction in Play; some events require the matching entity/item/game context. Use the example as an observation handler, then replace it with your intended behavior.

Timing and restrictions

Event mutations/cancellation must run while the original synchronous event is active. A Wait or suspension ends that opportunity. Captured event values can remain readable afterward. Check that participants still belong to Play before applying later actions. Repeated movement/interaction triggers can create many tasks if each starts detached work.

Events and targets · Control flow · Async calls

Reference identifier: player_fish.