Global Configuration & Permissions

API status — PROPOSED, NOT IMPLEMENTED. SkCine is currently a design specification in this conversation; no built SkCine.jar or syntax registry was supplied. All SkCine-specific examples are intended API contracts, not verified runnable .sk. Do not advertise these as tested until each example passes a real Skript reload and runtime test.

Scenes must not be authored in configuration. A technical runtime plugins/SkCine/config.yml is permitted.

Example technical config (proposed)

engine:
  max-concurrent-instances: 100
  max-instances-per-player: 1
  busy-viewer-policy: reject
  script-reload-policy: finish-on-snapshot
camera:
  prefer-packet-backend: true
  allow-spectator-fallback: true
  restore-player-state: true
vfx:
  particles-per-viewer-tick: 300
  adaptive-quality: true
  default-quality: auto
safety:
  max-scene-duration-seconds: 300
  max-keyframes-per-track: 4096
  max-temporary-actors: 250
  crash-recovery-journal: true
logging:
  debug: false

Numbers are starting ideas and must be benchmarked; they are not verified defaults.

Proposed permissions

skcine.admin — all maintenance commands.
skcine.command.info — view version/health.
skcine.command.profiler — view performance metrics.
skcine.command.debug — verbose diagnostics.
skcine.scene.skip — allow manual skipping where required.

Who may write Skript files? Control filesystem access and Skript command permissions separately. A SkCine camera event does not grant players automatic permission to define scripts.

Accessibility

Suggested settings: reduce camera shake, lower particle density, respect viewer language, prefer readable subtitle durations.