Record the key and the action before editing
If a shortcut changes after adding a script, keep the physical key, expected action and observed action in a short note. Identify the Celluloid package and version. A desktop global shortcut can also intercept input, so confirm that the player window actually has focus during the test.
Choose one known local file and a harmless playback action. Keep an ordinary menu or mouse route available for recovery. Do not test the conflict through a command that deletes files or closes unsaved work; the goal is to understand input dispatch, not to exercise an irreversible action.
Inspect the documented script and binding layers
Celluloid’s README documents scripts through the Plugins tab and warns that script bindings can conflict with its own keys. It also provides a separate Keybindings file setting. Inspect those actual inputs before assuming a bug in the base player.
Preserve the script file and current binding configuration. Keep its publisher and purpose attached to it. A script obtained from another project can add behavior beyond its visible shortcut, so do not import unrelated scripts merely to restore one familiar key.
Make a narrow presence-and-absence comparison
Use the supported preferences to compare the known action with the suspect script enabled and disabled where the installed build permits that workflow. Keep the same file, focused window and key. Record whether the changed behavior follows that one script.
If a custom binding is required, use the project’s documented input syntax and choose a non-conflicting key deliberately. Preserve the previous mapping and verify both the new action and the ordinary controls. A duplicate assignment can conceal which layer ultimately receives the key.
Retest a normal session
Open another known item or restart normally as appropriate to the documented workflow, then check the intended action again. Keep the final script identity and binding in setup notes. If the conflict remains, provide the minimal input case and relevant versions through the project’s support process.
The expected outcome is a reproducible key assignment with an understood script dependency. It does not certify arbitrary plugins, guarantee the same shortcuts in another frontend or establish that an unreviewed script is suitable for every device. Preserve the original working setup until the ordinary navigation controls remain usable.
Questions answered
What should I include in an input-conflict report?
Name the actual player package, script, physical key, expected action and presence-and-absence result. Keep private source URLs out of it.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.