Make the shared rod shape every turn
In this fictional design, Mira and Sol explore a quiet inlet with one fishing rod between them. They have four turns before the tide closes and a shared basket that holds three fish. A cast uses one turn and adds one fish. Passing the rod at the central dock is free, but a player cannot hand it over from a distant bank. The group can catch two fish and still keep two turns for travel or a final choice.

This small constraint creates a clear cooperative question: who should cast before the rod changes hands? If the player on the far bank casts first, the group gets a catch but must still reach the dock to pass the tool. If the dockside player casts first, the other player can take the rod sooner. Keep travel and casting costs separate in the first prototype so the value of the handoff is easy to see.
Make ownership and location explicit
Store the rod owner, both player positions, remaining turns, basket count and tide phase in one outing state. A cast is legal only for the current owner, consumes one turn and increments the catch count up to the basket limit. A handoff requires both players at the dock, transfers ownership, and consumes no fishing turn. End the outing when turns reach zero or the group chooses to leave.

A deterministic trace can start with Mira holding the rod at the dock: Mira casts, the rod passes to Sol, and Sol casts. The outing uses two of four turns and catches two fish. Test the same sequence with Sol starting. Then move Mira to the far bank and try to pass: reject the handoff and keep ownership unchanged. Explicit feedback such as “Return to the dock to pass the rod” makes the rule legible.
Test the tide window before adding more fish
Run the state transitions with a small executable rule test before tuning species, bait or animation. Check that the rod always has one owner, each cast costs exactly one turn, the basket never exceeds three fish, and an invalid handoff does not alter owner or turn count. Also test the boundary at zero turns so a late cast cannot create a fifth action.
This is a local rules simulation for a fictional concept. It does not test simultaneous input, network latency, movement feel, collision, fishing timing or whether two people enjoy the loop. In a playable co-op prototype, test both players at the same dock, one player leaving mid-handoff, and a save or reconnect while the rod is held. Keep those results separate from this deterministic check.

Prototype the handoff before the whole coastline
Ask for one inlet, two player tokens, one rod, one dock, a four-turn counter and a three-fish basket. Show who owns the rod and whether both players are close enough to pass it. Make cast, move, pass and end-outing separate actions. Once the local state trace matches the expected turns, add fish variety or a second location.
Godot signals can help one gameplay node notify another when a handoff occurs; the official documentation explains connecting signals between objects. SEELE AI Game Maker offers a prompt-based starting point for a playable game concept. Use either as a creation aid, then verify co-op behavior in your own build. Neither source proves that this fictional example has been implemented.
Create an original cooperative fishing prototype with two players, one shared rod, one central dock, four outing turns and a basket capacity of three. A cast by the current rod owner costs one turn and adds one fish. Passing at the dock transfers ownership without spending a turn. Reject passing away from the dock. Show rod owner, turns and basket count. Do not claim online or playtest validation.
Start a fictional co-op prototype in SEELE · Godot signals documentation
Frequently asked questions
Why should passing the rod be free?
The handoff is the cooperation mechanic, while turns measure fishing opportunities. Making both actions cost a turn can make passing feel like a penalty before players understand its value. Start with free handoff at the dock, then test a paid pass only if the outing has enough turns and the trade-off is clearly shown. Keep that balance change as a separate iteration.
How do I prevent both players from using the same rod at once?
Keep a single owner field in the outing state. A cast checks that the acting player matches the owner, then spends one turn and records the catch. A pass changes the owner only after the dock condition succeeds. If the game later supports simultaneous network input, make the state change atomic and test conflicts in the playable build.
What should happen when the tide closes?
End the outing at the defined turn boundary and present the shared basket, not separate individual totals. In the four-turn concept, no fifth cast is accepted. If travel uses turns in a later version, show that cost before a player commits so the final route to the dock is a visible choice.


