Platformer follow camera
platformer-follow-camera · an adoption of Camera framing, version 1
Use in your game
Opens the authoring tool with these answers and settings already filled in. You still add your game's own rules and tuning.
What is in the ZIP
The ZIP holds the adoption and its acceptance tests. In the authoring tool, choose Add contract and pick this ZIP. If you keep your design as files, put them in contracts/.
The contract behind it
Covers the views used during play and what each one keeps visible. It records fixed, follow, and free-camera modes, manual panning, view size, travel limits, safe areas, clearance, camera activities, and failure handling. Camera feel, physical input mappings, unit commands, HUD layout, and 3D occlusion stay elsewhere.
Questions
The supplied answer is marked on each question. Pick other answers to see what changes. Nothing is saved here: the ZIP and the authoring tool use the supplied answers.
In normal play, must these cameras keep anything from your game on screen?
Why this is asked
A follow target or camera travel limit does not prove that game content remains visible. This choice states whether these cameras make that promise.
Numbersno numbers
This contract has no numbers to set.
Rulesno rules
A rule is a check between the numbers. Validation reports a rule that fails.
This contract has no rules between its numbers.
Lists3 lists
Each list holds the rows this adoption supplies. A list can be empty.
Cameras
cameras
| Id | Active when | View declared in | Follow mode | Follow target declared in | Manual pan | Pan actions declared in | Recenter action declared in | Travel limit | Travel limit declared in | View size | View size rule declared in | Failure response | Failure handling declared in |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
platformer-follow-camera | movement.platformer-play-active | presentation.platformer-play-view | slack-follow | movement.player-character-follow-target-and-slack-region | — | — | — | one-world-region | world.platformer-camera-region | fixed-size | — | failure-unreachable | world.player-character-always-fits-platformer-camera-region |
Coverage promises
coverage-promises
| Id | Camera id | Subject | Applies when | Coverage | Reference point | Visibility area | Safe area declared in | Margin declared in |
|---|---|---|---|---|---|---|---|---|
player-character-point | platformer-follow-camera | movement.player-character | movement.player-character-in-play | reference-point | movement.player-character-reference-point | rendered-view | — | presentation.player-character-view-margin |
Camera activities
camera-activities
| Id | Camera id | Activity kind | Applies when | Extent declared in | Actions declared in | Promises | Promise effect |
|---|---|---|---|---|---|---|---|
movement-look-ahead | platformer-follow-camera | look-ahead | movement.player-character-grounded-run-or-airborne-arc | presentation.movement-look-ahead-extent | — | — | keeps-promise |
Test inputsscope and seeds
Some tests need a scope or seeds from the adoption before they can run.
This adoption supplies none; every test uses its defaults.
Acceptance tests29 tests apply
The contract comes with 51 tests. A test that runs once per row is counted once for each row. Tests that do not apply to these answers are still listed, with the reason.
framing-vocabulary-is-observable
the framing vocabulary is observed at the displayed result
Applies to platformer-follow-camera.
This test fixes two observable meanings. A displayed play moment is the final play image after every listed camera change, scaling, and HUD composition. Any overlap makes two screen areas one play region.
Test steps and diagnostics
- Given
a trace of camera settlement and displayed output for
platformer-follow-camera- When
- displayed play moments and play regions are classified
- Then
- each displayed play moment is the final play image after follow motion, manual pan, aim or peek offset, player-held zoom, shake, temporary zoom, scripted movement, viewport scaling, and HUD composition
- two play regions are treated as one region whenever their screen areas overlap at all
- Diagnostics
platformer-follow-camera-displayed-frame-logplatformer-follow-camera-active-camera-traceplatformer-follow-camera-candidate-trace
declared-content-framing-outcomes-are-observable
valid frames and framing failures are observable
Applies to platformer-follow-camera.
For declared content, a valid frame satisfies every applicable unsuspended coverage row at its settled margin. A framing failure exists only after every allowed position and size has failed.
Test steps and diagnostics
- Given
a trace of composed views and failure settlement for
platformer-follow-camera- When
- valid frames and framing failures are classified
- Then
- a frame is valid exactly when every applicable unsuspended coverage row fits at its settled margin
- a framing failure is recorded only when no position and view size allowed by the camera can produce a valid frame
- Diagnostics
platformer-follow-camera-failure-record
camera-supplies-region-while-active · platformer-follow-camera
platformer-follow-camera supplies its region exactly while active
Applies to the platformer-follow-camera row.
Camera platformer-follow-camera supplies exactly the play region cited at presentation.platformer-play-view, and only while the rule cited at movement.platformer-play-active holds. The test names both addresses and restates nothing from them.
Test steps and diagnostics
- Given
camera row
platformer-follow-cameraand the rules cited atmovement.platformer-play-activeandpresentation.platformer-play-view- When
- the active-camera trace crosses both edges of the rule cited at
movement.platformer-play-active
- the active-camera trace crosses both edges of the rule cited at
- Then
platformer-follow-camerasupplies exactly the play region cited atpresentation.platformer-play-viewwhilemovement.platformer-play-activeholdsplatformer-follow-camerasupplies no play region whilemovement.platformer-play-activedoes not hold
- Diagnostics
platformer-follow-camera-active-camera-traceplatformer-follow-camera-displayed-frame-log
active-regions-are-exclusive
active cameras occupy exclusive play regions
Applies to platformer-follow-camera.
At most one camera is active in one play region. Overlap is the whole test; how two areas are composited is outside this contract. No pair settles independently unless its play regions are distinct, and each distinct camera's settlement and promise results remain independent. Where the adoption can activate no pair, there is no pair behavior to assert.
Test steps and diagnostics
- Given
every pair of cameras that
platformer-follow-cameracan activate at the same displayed play moment; an adoption with no such pair asserts only the no-pair result- When
- their play regions are compared after display scaling
- Then
- no pair is active where the two screen areas overlap at all; a violating pair is a defect this test fails by construction
- no pair settles independently unless its play regions are distinct; where they are distinct, each camera's base position, settled view size, suspensions, and promise results are recorded per camera and no value of one is a function of the other's
- an adoption that can activate no pair has no simultaneous-region settlement to assert
- Diagnostics
platformer-follow-camera-active-camera-traceplatformer-follow-camera-play-region-mapplatformer-follow-camera-candidate-traceplatformer-follow-camera-settled-margin-recordplatformer-follow-camera-suspension-log
promise-applies-exactly-when-cited · player-character-point
player-character-point applies exactly when its cited rule holds
Applies to the player-character-point row.
Promise player-character-point on platformer-follow-camera applies exactly while the rule cited at movement.player-character-in-play holds. Outside that interval it is not tested and cannot create a framing failure. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
coverage-promises row
player-character-pointforplatformer-follow-camera- When
- the trace crosses both edges of the rule cited at
movement.player-character-in-play
- the trace crosses both edges of the rule cited at
- Then
player-character-pointenters the applicable promise set exactly whilemovement.player-character-in-playholds- outside that interval
player-character-pointis not tested and cannot create a framing failure
- Diagnostics
platformer-follow-camera-visibility-area-traceplatformer-follow-camera-failure-record
whole-extent-stays-visible
the whole extent of Row.id remains inside its visibility area
Does not apply to platformer-follow-camera: no row in coverage-promises matches coverage whole extent.
reference-point-stays-visible · player-character-point
the declared point for player-character-point remains inside its visibility area
Applies to the player-character-point row.
The reference point named at movement.player-character-reference-point for player-character-point, the subject named at movement.player-character, remains inside this row's own visibility area at its settled margin on every displayed play moment where the promise is applicable and unsuspended, except on a displayed play moment that has entered failure settlement, where this row is recorded as failed rather than kept. This row promises nothing about the rest of the subject. The suspension log shows whether each moment tested this row or left it untested. The test names the addresses and restates nothing from them.
Test steps and diagnostics
- Holds
on every displayed play moment when
player-character-pointis applicable and unsuspended, the point named atmovement.player-character-reference-pointfor the subject named atmovement.player-characterremains inside this row's visibility area at its settled margin, except on a displayed play moment that has entered failure settlement, where this row is recorded as failed rather than kept; no other part of the subject is required to fit by this row; the suspension log shows whether each moment tested this row or left it untested- Seeds
["camera-route-a","camera-route-b"]- Scope
all supported play routes and camera transitions covered by the row's cited conditions- Diagnostics
platformer-follow-camera-displayed-frame-logplatformer-follow-camera-visibility-area-traceplatformer-follow-camera-suspension-logplayer-character-point-reference-point
rendered-view-defines-visibility-area · player-character-point
player-character-point uses the rendered play region
Applies to the player-character-point row.
Promise player-character-point uses the final rendered play region supplied by platformer-follow-camera as its visibility area. HUD overlap alone is ignored for this row.
Test steps and diagnostics
- Given
applicable unsuspended promise
player-character-pointafter display scaling and HUD composition- When
- its visibility area is constructed
- Then
- the visibility area is the final rendered play region supplied by
platformer-follow-camera - HUD overlap alone removes no space from this visibility area
- the visibility area is the final rendered play region supplied by
- Diagnostics
platformer-follow-camera-visibility-area-traceplatformer-follow-camera-hud-composition-log
hud-safe-area-defines-visibility-area
Row.id uses its cited HUD-safe area
Does not apply to platformer-follow-camera: no row in coverage-promises matches visibility-area hud safe area.
margin-insets-the-visibility-area · player-character-point
player-character-point insets its visibility area by four margins
Applies to the player-character-point row.
The four clearances with units cited at presentation.player-character-view-margin inset player-character-point's visibility area. A subject or reference point exactly on the inset boundary fits. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
promise
player-character-point, its visibility area, and the four clearances with units cited atpresentation.player-character-view-margin- When
- the margin is inset
- Then
- the top, right, bottom, and left clearances from
presentation.player-character-view-margininset the visibility area - a subject or reference point exactly on the boundary of the inset area fits
- the top, right, bottom, and left clearances from
- Diagnostics
platformer-follow-camera-visibility-area-traceplatformer-follow-camera-settled-margin-record
activity-selects-affected-promises · movement-look-ahead
movement-look-ahead affects exactly its selected promises
Applies to the movement-look-ahead row.
Activity movement-look-ahead affects exactly the applicable promises selected for platformer-follow-camera. Where this row cites a promises list, that fixed list is exact; where it cites none, every applicable promise on platformer-follow-camera is affected. The test names no list contents and restates nothing from the citation.
Test steps and diagnostics
- Given
active activity row
movement-look-aheadonplatformer-follow-camera, the fixed promise list this row cites in its promises field, when it has one, and every applicable promise on that camera- When
- the activity's affected set is built
- Then
- where this row cites a promises list, the affected promises are exactly the ones it names
- where it cites no promises list, the affected set is every applicable promise on
platformer-follow-camera - the affected-promise-set record names each promise the citation lists, or every applicable promise on
platformer-follow-camerawhen the row cites none - the selection record distinguishes an unaffected promise from an affected promise that happened not to change
- Diagnostics
platformer-follow-camera-activity-logplatformer-follow-camera-affected-promise-set
may-suspend-releases-and-restores-promises
Row.id suspends only its affected promises
Does not apply to platformer-follow-camera: no row in camera-activities matches promise-effect may suspend.
keeps-promise-preserves-other-suspensions · movement-look-ahead
movement-look-ahead keeps its promise without cancelling another suspension
Applies to the movement-look-ahead row.
Activity movement-look-ahead supplies no suspension of its own. If another active activity suspends the same promise, movement-look-ahead does not cancel it; where this adoption cannot construct that overlap, the overlap clause asserts nothing. The interval comes from movement.player-character-grounded-run-or-airborne-arc, whose content this test does not restate.
Test steps and diagnostics
- Given
active keeps-promise activity
movement-look-aheadand each overlap with another active suspending activity on the same promise thatplatformer-follow-cameracan construct; where no overlap can be constructed, the overlap clause asserts nothing- When
- the final promise set is tested during
movement-look-ahead's interval cited atmovement.player-character-grounded-run-or-airborne-arc
- the final promise set is tested during
- Then
movement-look-aheadsupplies no suspension of its own- a different active suspension affecting the same promise remains active until its own interval ends
- Diagnostics
platformer-follow-camera-suspension-logplatformer-follow-camera-activity-log
recenter-manual-pan-defines-suspension-interval
suspending manual pan uses the recentered interval
Does not apply to platformer-follow-camera: no row in camera-activities matches promise-effect may suspend and activity-kind manual pan.
controller-disposes-of-kept-player-proposals
the controller disposes of kept player proposals
Does not apply to platformer-follow-camera: no row in camera-activities matches promise-effect keeps promise and activity-kind manual pan or aim or peek offset.
camera-without-activity-uses-base-alone
a camera without an activity builds from its base alone
Applies to platformer-follow-camera.
For each active camera and moment with no active camera-activities row, the candidate is built from the settled base position alone and has no activity offset. If this adoption has no such moment, the test asserts nothing.
Test steps and diagnostics
- Given
each active camera and displayed play moment for which
platformer-follow-camerahas no active camera-activities row; if every active camera has an activity, this test asserts nothing- When
- the candidate position is built
- Then
- the candidate has the settled base position and no activity offset
- Diagnostics
platformer-follow-camera-candidate-traceplatformer-follow-camera-activity-log
fixed-view-uses-authored-base
Row.id uses only its authored base position
Does not apply to platformer-follow-camera: no row in cameras matches follow-mode fixed view.
locked-follow-uses-target-point
Row.id follows only its cited target point
Does not apply to platformer-follow-camera: no row in cameras matches follow-mode locked follow.
slack-follow-stays-in-allowed-set · platformer-follow-camera
platformer-follow-camera stays in its cited slack set
Applies to the platformer-follow-camera row.
Slack-follow camera platformer-follow-camera selects only positions inside the allowed set around its target cited at movement.player-character-follow-target-and-slack-region. It never searches outside that set. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
active slack-follow camera
platformer-follow-cameraand the target and allowed positions cited atmovement.player-character-follow-target-and-slack-region- When
- the controller selects a base position across target motion and direction changes
- Then
- every selected base position lies inside the cited allowed set around the target before the travel limit is applied
- the controller searches no position outside that set
- Diagnostics
platformer-follow-camera-candidate-traceplatformer-follow-camera-follow-target-trace
free-camera-starts-from-player-pan
Row.id starts from its player pan proposal
Does not apply to platformer-follow-camera: no row in cameras matches follow-mode free view or free with recenter.
free-with-recenter-selects-target
Row.id returns to its cited target on recenter
Does not apply to platformer-follow-camera: no row in cameras matches follow-mode free with recenter.
no-travel-limit-does-not-clamp
Row.id applies no camera travel clamp
Does not apply to platformer-follow-camera: no row in cameras matches travel-limit no camera travel limit.
travel-limit-clamps-base-position · platformer-follow-camera
platformer-follow-camera clamps its base position to the cited region
Applies to the platformer-follow-camera row.
Camera platformer-follow-camera clamps its base position to the one camera-position region cited at world.platformer-camera-region. The limit constrains camera position, not the visible region. A promise not tested by the final composed-view test is not recorded as kept. Its edge condition reduces only the clamped-side margin by the exact shortfall, never below zero, while the subject still stays inside the underlying area; the margin record distinguishes that thinning from an ordinary fit. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
camera
platformer-follow-camera, base proposals inside and outside the one camera-position region cited atworld.platformer-camera-region, and a subject near each region edge- When
- the travel limit is applied before activity offsets
- Then
- the base position is clamped to the one camera-position region
- the clamp constrains camera position, not the visible region
- a promise not tested by the final composed-view test is not recorded as kept
- where the clamp alone prevents the subject from meeting a margin, the clamped-side margin is reduced by the exact shortfall and no lower than zero, while the subject remains inside the underlying uninset visibility area
- the margin-settlement record distinguishes a thinned margin from a subject that merely fit inside the original inset
- Diagnostics
platformer-follow-camera-candidate-traceplatformer-follow-camera-settled-margin-recordplatformer-follow-camera-visibility-area-trace
activity-offset-follows-settled-base · movement-look-ahead
movement-look-ahead applies its bounded change after the base settles
Applies to the movement-look-ahead row.
Activity movement-look-ahead applies after the base settles and is bounded by the strongest change cited at presentation.movement-look-ahead-extent. A position-changing activity is an offset outside the set this follow mode supplies and can pass any travel limit the camera declares; the final test still decides every promise. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
active activity
movement-look-aheadat its strongest displacement cited atpresentation.movement-look-ahead-extent- When
- the candidate is built after the base position and travel clamp settle
- Then
- the activity change is bounded by
presentation.movement-look-ahead-extentand is applied after the base settles - a position-changing activity is an activity offset outside the set this follow mode supplies and can carry the candidate past any travel limit the camera declares
- the offset never substitutes for the final composed-view test
- the activity change is bounded by
- Diagnostics
platformer-follow-camera-activity-logplatformer-follow-camera-candidate-traceplatformer-follow-camera-displayed-frame-log
temporary-zoom-settles-one-proposed-size
Row.id proposes and settles one temporary view size
Does not apply to platformer-follow-camera: no row in camera-activities matches activity-kind temporary zoom.
aim-offset-uses-cited-actions
Row.id receives proposals through its cited aim actions
Does not apply to platformer-follow-camera: no row in camera-activities matches activity-kind aim or peek offset.
fixed-size-uses-authored-size · platformer-follow-camera
platformer-follow-camera uses its authored view size
Applies to the platformer-follow-camera row.
Fixed-size camera platformer-follow-camera uses the authored size named at presentation.platformer-play-view. Only an active temporary-zoom activity can propose another temporary size. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
active fixed-size camera
platformer-follow-cameraacross ordinary activity and, where this adoption has such an activity, every active temporary-zoom activity it can construct- When
- view size settles
- Then
- without an active temporary-zoom activity the size is exactly the authored size named at
presentation.platformer-play-view - only an active temporary-zoom activity can propose a different temporary size
- without an active temporary-zoom activity the size is exactly the authored size named at
- Diagnostics
platformer-follow-camera-view-size-traceplatformer-follow-camera-activity-log
player-held-zoom-starts-in-cited-range
Row.id starts from held zoom inside its cited range
Does not apply to platformer-follow-camera: no row in cameras matches view-size player held zoom.
automatic-fit-chooses-largest-valid-size
Row.id chooses the largest allowed fitting size
Does not apply to platformer-follow-camera: no row in cameras matches view-size automatic fit.
automatic-fit-respects-travel-region
Row.id continues automatic fitting after its centre is clamped
Does not apply to platformer-follow-camera: no row in cameras matches view-size automatic fit and travel-limit one world region or changes by situation.
final-composed-test-decides-frame
the final composed-view test decides every promise
Applies to platformer-follow-camera.
After the final view and HUD are composed, every applicable unsuspended promise is tested against its inset visibility area. That result alone decides validity; no follow trigger, recenter action, travel limit, or earlier candidate substitutes for it. When every applicable unsuspended promise passes, that composed view is the displayed play moment. Exactly one view size settles per displayed play moment on each active camera, and the controller disposes of every size and position proposal under the activity permission and all unsuspended promises together.
Test steps and diagnostics
- Given
each candidate
platformer-follow-cameracan construct, including candidates that pass an earlier follow, recenter, travel, or position check- When
- the final view and HUD are composed
- Then
- every applicable unsuspended promise is tested against its inset visibility area
- only this final test decides whether the frame is valid
- no follow trigger, recenter action, travel limit, or earlier candidate substitutes for the final test
- when every applicable unsuspended promise passes, that composed view is the displayed play moment
- exactly one view size settles for each displayed play moment on each active camera
- the controller disposes of every size and position proposal under the activity permission and all unsuspended promises together
- Diagnostics
platformer-follow-camera-candidate-traceplatformer-follow-camera-visibility-area-traceplatformer-follow-camera-displayed-frame-log
keeps-promise-holds-through-full-interval · movement-look-ahead
movement-look-ahead keeps every affected promise for its full interval
Applies to the movement-look-ahead row.
Activity movement-look-ahead is demonstrated as keeps-promise only when the final test passes for every affected unsuspended promise on every displayed play moment in its interval at movement.player-character-grounded-run-or-airborne-arc, including the strongest displacement or size change cited at presentation.movement-look-ahead-extent. The test names the addresses and restates nothing from them.
Test steps and diagnostics
- Holds
the final composed-view test passes for every affected unsuspended promise on every displayed play moment in the interval cited at
movement.player-character-grounded-run-or-airborne-arc, including the strongest displacement or size change cited atpresentation.movement-look-ahead-extent- Seeds
["activity-route-a","activity-route-b"]- Scope
the full cited activity interval, including boundary moments and strongest legal proposals- Diagnostics
platformer-follow-camera-activity-logplatformer-follow-camera-displayed-frame-logplatformer-follow-camera-visibility-area-trace
keeps-promise-holds-for-pan-and-zoom
Row.id keeps every affected promise across its proposals
Does not apply to platformer-follow-camera: no row in camera-activities matches promise-effect keeps promise and activity-kind manual pan or player zoom.
failure-record-follows-exhausted-search · platformer-follow-camera
platformer-follow-camera creates one complete failure record after search
Applies to the platformer-follow-camera row.
For camera platformer-follow-camera, one complete framing failure is created only after no allowed candidate passes. It records the camera, failed promises, display size, visibility areas, settled margins, attempted position and size, travel limit, active activities, and selected response. Before that point, the response weakens no coverage row. If this adoption can construct no exhausted search, the failure branch asserts nothing.
Test steps and diagnostics
- Given
active camera
platformer-follow-cameraand each situation the adoption can construct where every allowed candidate fails; where no such situation is reachable, the failure branch asserts nothing- When
- the allowed position and view-size search is exhausted
- Then
- exactly one framing failure is created only after no allowed candidate passes
- the record contains the camera id, failed promise ids, display size, visibility areas, settled margins, attempted position and view size, travel limit, active activities, and selected failure response
- before this step, the failure response weakens no coverage row
- Diagnostics
platformer-follow-camera-candidate-traceplatformer-follow-camera-failure-recordplatformer-follow-camera-visibility-area-trace
hold-valid-frame-keeps-invalid-candidate-offscreen
Row.id holds a valid frame on failure
Does not apply to platformer-follow-camera: no row in cameras matches failure-response hold valid frame.
keep-priority-content-displays-best-allowed-frame
Row.id applies its total priority on failure
Does not apply to platformer-follow-camera: no row in cameras matches failure-response keep priority content.
show-framing-failure-adds-cited-state
Row.id shows its cited framing-failure state
Does not apply to platformer-follow-camera: no row in cameras matches failure-response show framing failure.
change-world-reruns-framing-before-display
Row.id changes the world and reruns framing
Does not apply to platformer-follow-camera: no row in cameras matches failure-response change world to restore frame.
failure-unreachable-invalidates-reached-claim · platformer-follow-camera
platformer-follow-camera treats a reached failure as an invalid claim
Applies to the platformer-follow-camera row.
Camera platformer-follow-camera declares no failure handling beyond the failure record itself. A failure record for this camera contradicts the complete unreachability argument cited at world.player-character-always-fits-platformer-camera-region, and the design claim fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
camera
platformer-follow-cameraand the complete unreachability argument cited atworld.player-character-always-fits-platformer-camera-region- When
- the run exercises every supported display size and route named by the cited argument
- Then
- no failure handling beyond the failure record itself is declared
- a failure record for this camera contradicts the argument cited at
world.player-character-always-fits-platformer-camera-regionand the design claim fails
- Diagnostics
platformer-follow-camera-candidate-traceplatformer-follow-camera-failure-recordplatformer-follow-camera-first-unreachable-counterexample
failure-persists-until-valid-or-inactive
a framing failure persists until settlement or deactivation
Applies to platformer-follow-camera.
Every reached framing failure persists until a later valid settlement or camera deactivation. Priority, a notice, or a started world change does not itself make an invalid frame satisfy a promise. If this adoption cannot reach failure, the template asserts nothing.
Test steps and diagnostics
- Given
each framing failure
platformer-follow-cameracan reach; if none is reachable, this test asserts nothing- When
- priority is applied, a notice is shown, a world change starts, and later settlement or deactivation occurs as available
- Then
- the failure remains a failure until a later settlement produces a valid frame or the camera deactivates
- priority, a visible notice, or a started world change does not by itself turn an invalid frame into a kept promise
- Diagnostics
platformer-follow-camera-failure-recordplatformer-follow-camera-displayed-frame-logplatformer-follow-camera-active-camera-trace
recovery-and-handover-insert-no-unchecked-frame
recovery and handover insert no unchecked frame
Applies to platformer-follow-camera.
Neither the end of a suspension nor a camera switch inserts an unchecked frame, and neither leaves two cameras active in one play region. An adoption in which no camera activation follows a deactivation has no handover case to construct.
Test steps and diagnostics
- Given
each suspension end and camera handover
platformer-follow-cameracan construct; an adoption in which no camera activation follows a deactivation has no handover case to construct- When
- the next displayed play moment is prepared
- Then
- neither recovery nor switching inserts an unchecked frame or leaves two cameras active in one play region
- Diagnostics
platformer-follow-camera-active-camera-traceplatformer-follow-camera-displayed-frame-log
recovery-and-handover-first-frame-is-settled
recovery and handover settle a checked first frame
Applies to platformer-follow-camera.
After a suspension ends, the mechanism reruns promise selection through the final composed-view test before the next displayed play moment; that moment is valid or enters failure settlement. A handover runs active-region selection through the final composed-view test with the incoming camera's own promises and visibility areas. An adoption in which no camera activation follows a deactivation has no handover case to construct.
Test steps and diagnostics
- Given
each suspension end and camera handover
platformer-follow-cameracan construct; an adoption in which no camera activation follows a deactivation has no handover case to construct- When
- the next displayed play moment is prepared
- Then
- after a suspension ends, steps 2 through 10 run and the first unsuspended moment is valid or enters steps 11 through 13
- at handover, steps 1 through 10 run with the incoming camera's own promise set and visibility areas
- Diagnostics
platformer-follow-camera-suspension-logplatformer-follow-camera-active-camera-traceplatformer-follow-camera-displayed-frame-logplatformer-follow-camera-failure-record
camera-first-frame-is-checked · platformer-follow-camera
platformer-follow-camera checks its first frame after every activation
Applies to the platformer-follow-camera row.
Whenever camera platformer-follow-camera becomes active, whether at a handover or a reactivation, its first displayed play moment in the region cited at presentation.platformer-play-view is tested against this camera's own applicable promises and visibility areas. It is valid or enters failure settlement under the failure response this camera declares.
Test steps and diagnostics
- Given
each activation of camera
platformer-follow-camera, whether at a handover or a reactivation- When
- its first displayed play moment is prepared in the region cited at
presentation.platformer-play-view
- its first displayed play moment is prepared in the region cited at
- Then
- the first displayed play moment is tested against this camera's own applicable promises and visibility areas
- that moment is valid or enters failure settlement under this camera's own
failure-unreachableanswer
- Diagnostics
platformer-follow-camera-active-camera-traceplatformer-follow-camera-visibility-area-traceplatformer-follow-camera-displayed-frame-logplatformer-follow-camera-failure-record
promise-camera-id-joins-one-camera · player-character-point
declaration check: player-character-point names exactly one camera in this adoption
Applies to the player-character-point row.
Declaration check: coverage promise player-character-point is legal only when platformer-follow-camera names exactly one cameras row in this adoption. A missing or ambiguous name is a defect this test fails by construction. This check reads the adoption, not the running game; the validator cannot check this join, so the reviewer does.
Test steps and diagnostics
- Given
coverage-promises row
player-character-pointwith camera-idplatformer-follow-camera- When
- the cameras rows are inspected
- Then
platformer-follow-cameranames exactly one cameras row in this adoption; a missing or ambiguous join is a defect this test fails by construction
- Diagnostics
platformer-follow-camera-declaration-record
activity-camera-id-joins-one-camera · movement-look-ahead
declaration check: movement-look-ahead names exactly one camera in this adoption
Applies to the movement-look-ahead row.
Declaration check: camera activity movement-look-ahead is legal only when platformer-follow-camera names exactly one cameras row in this adoption. A missing or ambiguous name is a defect this test fails by construction. This check reads the adoption, not the running game; the validator cannot check this join, so the reviewer does.
Test steps and diagnostics
- Given
camera-activities row
movement-look-aheadwith camera-idplatformer-follow-camera- When
- the cameras rows are inspected
- Then
platformer-follow-cameranames exactly one cameras row in this adoption; a missing or ambiguous join is a defect this test fails by construction
- Diagnostics
platformer-follow-camera-declaration-record
activity-promise-list-stays-on-camera · movement-look-ahead
declaration check: movement-look-ahead cites promises only from its own camera
Applies to the movement-look-ahead row.
Declaration check: where activity movement-look-ahead cites a promises list, every named promise must exist and belong to platformer-follow-camera. A stale, missing, or foreign-camera name is a defect this test fails by construction. Where the row cites no list, this join test asserts nothing. This check reads the adoption, not the running game. The test names no list contents and restates nothing from its citation.
Test steps and diagnostics
- Given
camera-activities row
movement-look-aheadand the fixed promise list this row cites in its promises field, when it has one; where it cites none, the list clause asserts nothing- When
- the named coverage-promises rows and their camera-id fields are inspected
- Then
- every named promise exists and has camera-id
platformer-follow-camera; a missing promise or a promise on another camera is a defect this test fails by construction
- every named promise exists and has camera-id
- Diagnostics
platformer-follow-camera-declaration-record
adoption-declares-a-camera
declaration check: the adoption declares at least one camera
Applies to platformer-follow-camera.
Declaration check: a camera-framing adoption declares at least one cameras row. An adoption with none describes no play view and is a defect this test fails by construction. This check reads the adoption, not the running game.
Test steps and diagnostics
- Given
the cameras row set for
platformer-follow-camera- When
- the adoption is reviewed as a camera-framing adoption
- Then
- at least one cameras row exists; an adoption with none describes no play view and is a defect this test fails by construction
- Diagnostics
platformer-follow-camera-declaration-record
declared-content-has-a-promise
declaration check: declared content includes at least one coverage promise
Applies to platformer-follow-camera.
Declaration check: an adoption answering declared-content declares at least one coverage-promises row. If it declares none, it has no visibility promise to test and fails this test by construction. This check reads the adoption, not the running game.
Test steps and diagnostics
- Given
platformer-follow-cameraanswering declared-content- When
- its coverage-promises rows are inspected
- Then
- at least one coverage-promises row exists; an adoption that answers declared-content and declares none has no promise to test and is a defect this test fails by construction
- Diagnostics
platformer-follow-camera-declaration-record
free-promise-camera-has-manual-pan-activity
declaration check: a free promise-bearing camera declares manual-pan activity
Does not apply to platformer-follow-camera: no row in cameras matches follow-mode free view or free with recenter.
no-content-guarantee-keeps-promise-shape-empty
declaration check: no-content-guarantee declares no promise machinery
Does not apply to platformer-follow-camera: content visibility is declared content, not no content guarantee.
framing-holds
the framing authority order holds for the whole run
Applies to platformer-follow-camera.
Across sequences of displayed play moments across activations, activities, suspensions, handovers, and failures, every displayed play moment follows the mechanism's authority order. Later stages never rewrite an earlier declaration, no question answer or row field changes the settlement order, and no displayed moment is both invalid and outside failure settlement. An adoption answering no-content-guarantee audits only the active-region and displayed-moment stages. The adoption supplies the audit seeds through verification inputs.
Test steps and diagnostics
- Holds
every displayed play moment passes in order through active play region, applicable promise, each coverage row's visibility area and margin, activity suspension, player proposal and controller disposal, camera-position travel limit, allowed position and view-size settlement, final composed-view test, and failure response; later stages never rewrite an earlier declaration; no question answer or row field changes the order in which these stages settle; no displayed play moment is both invalid and outside steps 11 through 13; an adoption answering no-content-guarantee audits only the active-region and displayed-moment stages
- Seeds
["framing-audit-a","framing-audit-b"]- Scope
sequences of displayed play moments across activations, activities, suspensions, handovers, and failures- Diagnostics
platformer-follow-camera-displayed-frame-logplatformer-follow-camera-active-camera-traceplatformer-follow-camera-candidate-traceplatformer-follow-camera-suspension-logplatformer-follow-camera-failure-recordplatformer-follow-camera-first-authority-order-violation
JSONthe adoption as one file
The adoption file as supplied. Answers you try on this page are not written into it; to change an adoption, open it in the authoring tool.
{
"contract": "camera-framing",
"version": 1,
"summary": "Covers the views used during play and what each one keeps visible. It records fixed, follow, and free-camera modes, manual panning, view size, travel limits, safe areas, clearance, camera activities, and failure handling. Camera feel, physical input mappings, unit commands, HUD layout, and 3D occlusion stay elsewhere.",
"questions": {
"content-visibility": {
"asks": "In normal play, must these cameras keep anything from your game on screen?",
"rationale": "A follow target or camera travel limit does not prove that game content remains visible. This choice states whether these cameras make that promise.",
"options": {
"declared-content": {
"meaning": "The cameras keep named game content visible. A party view keeps every active hero on screen.",
"semantics": "Every visibility promise lives in a coverage-promises row and every effect on one lives in a camera-activities row; nothing outside those rows is promised."
},
"no-content-guarantee": {
"meaning": "The cameras make no promise about game content staying visible. An endless runner may leave the view during a fast fall.",
"semantics": "No visibility promise exists; the promise and activity row sets are declared empty."
}
}
}
},
"declares": {
"values": {},
"rows": {
"cameras": {
"description": "The play views in this camera family and the rules that move or limit each one.",
"when-empty": "An adoption without a camera row describes no play view, and a reviewer rejects it.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "A stable camera name in game language, such as board-camera or tactical-view."
},
"active-when": {
"type": "citation",
"required": true,
"description": "The complete rule for when this camera supplies a displayed play view."
},
"view-declared-in": {
"type": "citation",
"required": true,
"description": "The rule naming this camera's final play region, aspect handling, and display sizes. For a fixed view it also names the authored base position; for a fixed size it also names the authored view size."
},
"follow-mode": {
"type": "string",
"required": true,
"options": [
"fixed-view",
"locked-follow",
"slack-follow",
"free-view",
"free-with-recenter"
],
"description": "A fixed room view's base position never moves or follows anything, and no input moves it; only a declared activity can offset it. Locked follow keeps a hero at the centre. Slack follow lets a runner move before the view follows. A free tactical view begins where the player moves it. A free map with recenter can return to a selected group."
},
"follow-target-declared-in": {
"type": "citation",
"when": {
"row": {
"follow-mode": [
"locked-follow",
"slack-follow",
"free-with-recenter"
]
}
},
"description": "The rule naming the followed target or the target used by recenter. For slack follow it also names the allowed positions around that target."
},
"manual-pan": {
"type": "string",
"when": {
"row": {
"follow-mode": [
"free-view",
"free-with-recenter"
]
}
},
"options": [
"edge-scroll",
"drag-view",
"move-view-actions",
"several-methods"
],
"description": "Edge scroll moves a strategy view at the screen edge. Drag view pulls a mission map. Move-view actions pan a tactics camera through mapped actions. Several methods gives a world map at least two of these."
},
"pan-actions-declared-in": {
"type": "citation",
"when": {
"row": {
"follow-mode": [
"free-view",
"free-with-recenter"
]
}
},
"description": "The game actions that pan this camera. Several methods names at least two methods; platform inputs stay with Control options."
},
"recenter-action-declared-in": {
"type": "citation",
"when": {
"row": {
"follow-mode": [
"free-with-recenter"
]
}
},
"description": "The game action that returns this view to its cited target."
},
"travel-limit": {
"type": "string",
"when": {
"row": {
"follow-mode": [
"locked-follow",
"slack-follow",
"free-view",
"free-with-recenter"
]
}
},
"options": [
"no-camera-travel-limit",
"one-world-region",
"changes-by-situation"
],
"description": "No limit lets a runner view keep moving. One region keeps a board view inside its room. Situation changes can give a tactical map different regions by mission phase. A fixed view travels nowhere and is not asked."
},
"travel-limit-declared-in": {
"type": "citation",
"when": {
"row": {
"travel-limit": [
"one-world-region",
"changes-by-situation"
]
}
},
"description": "The complete camera-position region and, when needed, the rule selecting the current region."
},
"view-size": {
"type": "string",
"required": true,
"options": [
"fixed-size",
"player-held-zoom",
"automatic-fit"
],
"description": "Fixed size keeps a runner at its authored view size. Player-held zoom lets a strategy player hold a chosen zoom level. Automatic fit widens a co-op view until the party and margins fit."
},
"view-size-rule-declared-in": {
"type": "citation",
"when": {
"row": {
"view-size": [
"player-held-zoom",
"automatic-fit"
]
}
},
"description": "For player-held zoom, the zoom actions and allowed range. For automatic fit, the allowed range, aspect response, update timing, and simultaneous-promise rule."
},
"failure-response": {
"type": "string",
"when": {
"flag": {
"content-visibility": [
"declared-content"
]
}
},
"options": [
"hold-valid-frame",
"keep-priority-content",
"show-framing-failure",
"change-world-to-restore-frame",
"failure-unreachable"
],
"description": "Hold valid frame leaves a puzzle transition on its last valid view. Keep priority content protects a tactics leader and records hidden allies as failed. Show framing failure adds a warning to a strategy view. Change world to restore frame applies a co-op tether or defeat rule. Failure unreachable cites why a fixed arena fits on every reachable display."
},
"failure-handling-declared-in": {
"type": "citation",
"when": {
"flag": {
"content-visibility": [
"declared-content"
]
}
},
"description": "The exact wait, priority, warning, or game rule used after failure, or the complete argument that failure cannot be reached."
}
}
},
"coverage-promises": {
"description": "The subjects or areas each camera keeps visible in named play situations.",
"when-empty": "No camera in this adoption promises to keep game content visible.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "A stable promise name in game language, such as whole-board or selected-group."
},
"camera-id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"description": "The camera that keeps this promise, by the name you gave it."
},
"subject": {
"type": "citation",
"required": true,
"description": "The Fixed game prose naming the subject or area that stays visible."
},
"applies-when": {
"type": "citation",
"required": true,
"description": "The complete play conditions in which this promise applies."
},
"coverage": {
"type": "string",
"required": true,
"options": [
"whole-extent",
"reference-point"
],
"description": "Whole extent keeps every edge of a selected squad visible. Reference point keeps a runner's cited centre visible even when the sprite reaches past the view."
},
"reference-point": {
"type": "citation",
"when": {
"row": {
"coverage": [
"reference-point"
]
}
},
"description": "The exact point that stays visible."
},
"visibility-area": {
"type": "string",
"required": true,
"options": [
"rendered-view",
"hud-safe-area"
],
"description": "Rendered view measures a runner from the final view edges, so HUD overlap alone does not fail. HUD safe area measures a tactics objective from the cited unobscured area, so HUD-covered space counts outside."
},
"safe-area-declared-in": {
"type": "citation",
"when": {
"row": {
"visibility-area": [
"hud-safe-area"
]
}
},
"description": "The final unobscured rectangle or shape after the HUD elements named by this promise's conditions are placed."
},
"margin-declared-in": {
"type": "citation",
"required": true,
"description": "The top, right, bottom, and left clearance inside the chosen visibility area, with units. Zero is stated explicitly. A camera clamped at its travel limit may hold less than this clearance on the clamped side, but the subject still stays inside the area."
}
}
},
"camera-activities": {
"description": "Frame-changing situations and whether each one keeps or suspends all or named promises on its camera.",
"when-empty": "No camera activity has a visibility-promise effect in this adoption. With declared content, the promise-bearing cameras use none of the seven listed activities.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "A stable activity name in game language, such as sprint-look-ahead or boss-hit-shake."
},
"camera-id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"description": "The camera this activity changes, by the name you gave it."
},
"activity-kind": {
"type": "string",
"required": true,
"options": [
"look-ahead",
"manual-pan",
"aim-or-peek-offset",
"player-zoom",
"shake",
"temporary-zoom",
"scripted-move"
],
"description": "Look-ahead leads a runner. Manual pan moves a tactical view. Aim or peek offsets a follow camera toward a target. Player zoom holds a strategy view at a chosen size. Shake offsets a boss hit. Temporary zoom changes a combat view's size. A scripted move frames a dialogue reveal."
},
"applies-when": {
"type": "citation",
"required": true,
"description": "The complete start and end conditions for this camera activity."
},
"extent-declared-in": {
"type": "citation",
"when": {
"row": {
"activity-kind": [
"look-ahead",
"aim-or-peek-offset",
"shake",
"temporary-zoom",
"scripted-move"
]
}
},
"description": "The rule naming this activity's strongest displacement or size change. Manual pan is bounded by the travel limit and controller instead; player zoom is bounded by the view-size citation."
},
"actions-declared-in": {
"type": "citation",
"when": {
"row": {
"activity-kind": [
"aim-or-peek-offset"
]
}
},
"description": "The game actions that produce this offset. Platform inputs stay with Control options."
},
"promises": {
"type": "citation",
"description": "The fixed list of promise names affected by this activity. When absent, the activity affects every promise on its camera."
},
"promise-effect": {
"type": "string",
"required": true,
"options": [
"keeps-promise",
"may-suspend"
],
"description": "Keeps promise preserves the affected rows, as when runner look-ahead stays inside its margin. May suspend allows those rows to fail only for this activity, as during a boss reveal."
}
}
}
}
},
"rules": {},
"origin": "https://opengdd.org/contracts/camera-framing-1",
"mechanism": [
"This is the single normative authority for each displayed play moment: which camera is active, what must remain visible, who moves the view, what may suspend a promise, how travel and view size are applied, what happens when content cannot fit, and when a suspended promise returns. Questions and rows supply choices and cited game rules; they do not define another order.",
"A **displayed play moment** is the final play image presented at one moment, after follow motion, manual pan, aim or peek offset, player-held zoom, shake, temporary zoom, scripted movement, viewport scaling, and HUD composition. A **play region** is the screen area named by `view-declared-in`; two regions are the same region whenever their screen areas overlap at all. A coverage row's **visibility area** is either the final rendered play region or that row's cited HUD-safe area. A **valid frame** satisfies every applicable, unsuspended coverage row at its settled margin. A **framing failure** exists only when no camera position and view size allowed by the camera can produce a valid frame.",
"### Select the view and promises",
"1. Read every camera whose `active-when` rule holds. Each active camera supplies the final play region named by `view-declared-in`. At most one camera may be active in one play region. Simultaneous split views settle independently only when their regions are distinct. 2. For each active camera, collect its coverage rows whose `applies-when` rules hold. `whole-extent` contributes the subject's complete displayed extent. For a set-valued subject, the whole extent is the union of its members' displayed extents. `reference-point` contributes only the cited point. 3. Construct each row's visibility area after display scaling and the HUD placement named by that row's conditions. HUD-covered space is outside a HUD-safe area; a rendered-view row deliberately ignores HUD overlap. Inset the area by the cited top, right, bottom, and left margin. Attach the one contract-supplied edge condition: a later travel clamp may reduce only the margin on its clamped side, never the underlying visibility area. A whole extent fits only when all of it lies inside the settled inset area. A reference point fits when that point lies inside it. A subject or point lying exactly on the boundary of the settled inset area fits.",
"### Apply activity permissions",
"4. Read every active activity row for the camera. Its `promises` citation, when present, selects the affected applicable promises; when absent, it selects every applicable promise on that camera. An active `may-suspend` row suspends only that set for its cited interval. Active `keeps-promise` rows do not cancel a different active suspension affecting the same promise. 5. A suspended promise is not tested and cannot create a framing failure. It becomes required again on the first displayed play moment after the last suspending activity affecting it ends. On a free-with-recenter camera, a suspending manual-pan interval begins when the view leaves its recentered state and ends on recenter or camera deactivation. 6. The player proposes motion and held zoom through the cited game actions; the camera controller disposes of the final frame. `free-view` and `free-with-recenter` name who initiates position changes, not who owns the displayed result. A `keeps-promise` manual-pan or aim-or-peek row therefore requires the controller to stop, redirect, or resize the proposed view before an affected promise fails.",
"### Build and test the frame",
"7. Build the candidate position in two stages. Stage one selects the base position inside the follow mode's set. A fixed view has only the base position named by `view-declared-in`. A locked follow has only its target point. A slack follow may use the allowed positions its citation names around the target. A free view starts from the player's proposal; a free-with-recenter view does the same until recenter selects its target point. The controller may search only within the set supplied by that mode. Apply any travel limit to the base position; a fixed view declares none. It constrains camera position, not the visible region, and it never proves that a subject is visible. Resolve the step-3 edge condition now: when this clamp alone prevents the subject from meeting a margin, reduce only the clamped-side margin by the exact shortfall, no lower than zero. The subject must still lie inside the underlying, uninset visibility area. Stage two applies each active position-changing activity as an offset to the settled base, bounded by its cited extent. An activity offset is outside the mode's search set and may carry the view past the travel limit; the final test in step 9 still decides every promise. 8. Settle view size once. `fixed-size` uses the size named by `view-declared-in`. `player-held-zoom` starts from the player's held level inside the cited range; its `player-zoom` activity row's effect decides whether the controller must keep every promise or may let the named ones suspend; with no such row, the controller must keep every applicable promise at every held level. `automatic-fit` applies the cited fit rule, choosing the largest allowed size at which the extent, the margins, the strongest cited displacement of every position-changing `keeps-promise` activity, and the largest cited size of every size-changing one fit together. On any view-size answer, an active temporary-zoom activity may propose its cited extent as a temporary size; an accepted temporary size replaces the size the answer would otherwise settle, for the activity's cited interval, and the authored size, held level, or fit result returns on the first displayed moment after it ends. The controller disposes of every proposal under the activity permission and all unsuspended promises together. The travel region still binds camera position only: if fitting needs a centre outside it, clamp the centre and continue fitting inside the allowed zoom range, even when the visible region extends beyond the travel region. If no allowed size and clamped position fits, step 11 applies. 9. Compose the final view and HUD, then test every unsuspended promise against its inset visibility area. This final test decides the outcome; a follow trigger, recenter action, camera travel limit, or earlier candidate frame never substitutes for it. 10. If every row passes, display the valid frame. A `keeps-promise` activity is demonstrated only when this final test passes on every displayed moment of its cited interval, including the strongest displacement or size change its extent citation names.",
"### Settle a framing failure and recovery",
"11. Only after no allowed candidate can pass, create one framing failure containing the camera id, failed promise ids, display size, visibility areas, settled margins, attempted position and view size, travel limit, active activities, and selected failure response. A failure response is not an ordinary precondition and cannot weaken a coverage row before this step. 12. `hold-valid-frame` does not display the invalid candidate. It keeps the last valid displayed frame or, before one exists, the cited non-play transition surface; the cited game rule decides whether play or a transition advances. `keep-priority-content` applies the cited total priority, displays the best allowed frame, and records each promise that did not fit. `show-framing-failure` displays the best allowed frame with its cited player-facing failure state. `change-world-to-restore-frame` applies the cited game rule to tether, defeat, or move content, then reruns steps 2–10 before another play moment is displayed; the cited rule may not change the active camera set or create a play region. `failure-unreachable` declares no runtime handling: reaching this step contradicts its cited argument and invalidates the design claim. 13. A failure remains a failure until a later settlement produces a valid frame or the camera deactivates. Priority, a visible notice, or starting a cited world change does not by itself turn an invalid frame into a kept promise. 14. When a suspension ends, run steps 2–10 before displaying the next play moment. The first displayed moment without an active suspension must be valid or must enter steps 11–13. At a camera handover, run steps 1–10: the incoming camera brings its own promise set and visibility areas, and its first frame follows this same first-valid-frame recovery path. Switching cannot insert an unchecked frame or leave two cameras active in one region.",
"The authority order is therefore: active play region, applicable promise, each coverage row's visibility area and margin, activity suspension, player proposal and controller disposal, camera-position travel limit, allowed position and view-size settlement, final composed-view test, failure response. Later stages never rewrite an earlier declaration."
],
"answers": {
"content-visibility": "declared-content"
},
"values": {},
"rows": {
"cameras": [
{
"id": "platformer-follow-camera",
"active-when": "movement.platformer-play-active",
"view-declared-in": "presentation.platformer-play-view",
"follow-mode": "slack-follow",
"follow-target-declared-in": "movement.player-character-follow-target-and-slack-region",
"travel-limit": "one-world-region",
"travel-limit-declared-in": "world.platformer-camera-region",
"view-size": "fixed-size",
"failure-response": "failure-unreachable",
"failure-handling-declared-in": "world.player-character-always-fits-platformer-camera-region"
}
],
"coverage-promises": [
{
"id": "player-character-point",
"camera-id": "platformer-follow-camera",
"subject": "movement.player-character",
"applies-when": "movement.player-character-in-play",
"coverage": "reference-point",
"reference-point": "movement.player-character-reference-point",
"visibility-area": "rendered-view",
"margin-declared-in": "presentation.player-character-view-margin"
}
],
"camera-activities": [
{
"id": "movement-look-ahead",
"camera-id": "platformer-follow-camera",
"activity-kind": "look-ahead",
"applies-when": "movement.player-character-grounded-run-or-airborne-arc",
"extent-declared-in": "presentation.movement-look-ahead-extent",
"promise-effect": "keeps-promise"
}
]
},
"pack": "sha256:4caf436eee5950d06c4368a78c14f9c4bff965e124c8d84695700ba82e2e7129"
}