Easy Chapter Generator
EnglishEspañol

Scripting

Legacy API Migration

Replace retained compatibility wrappers deliberately while preserving serialized UnityEvent targets during an upgrade.

Compatibility wrappers protect serialized listeners

V1 retains selected obsolete Spanish-named entry points and migration attributes so existing scene data and UnityEvents can survive the move to the public English API. Examples include FinalizarObjetivo, ComprobarObjetivo, IniciarCapitulo, SeleccionarCapitulo, branch activation wrappers, and ReposicionarJugador.

These methods remain callable but produce compiler obsolescence guidance. New code and new UnityEvent bindings should use the documented English replacements.

Representative replacements

Legacy memberReplacementBehavior note
Objective.FinalizarObjetivoObjective.TryCompleteReturns accepted completion
ButtonObjective.ComprobarObjetivoButtonObjective.EvaluatePreserves invalid-option behavior
Chapter.IniciarCapituloChapter.StartChapterFresh start resets known Chapter progress
Chapter.ComprobarObjetivoChapter.TryCompleteObjectiveLegacy extra log parameter is not part of V1 behavior
ChapterManager.SeleccionarCapituloChapterManager.SelectChapterPrefer TrySelectChapter with stable ID for integrations
ActivarRama / DesactivarRamaActivateBranch / DeactivateBranchString and index overloads remain
ReposicionarJugadorRepositionPlayerSame checkpoint lookup

Migrate without breaking scenes

  1. 1
    Create a version-control checkpoint and back up scenes and prefabs.
  2. 2
    Compile and list obsolete call sites in project C# separately from serialized UnityEvent listeners.
  3. 3
    Replace C# calls with English API and handle the current return value.
  4. 4
    Open each affected UnityEvent, select the same receiver, and choose the English method explicitly. Save the owning scene or prefab.
  5. 5
    Run Validation and the relevant lifecycle tests. Inspect serialized diffs for lost targets.
  6. 6
    Keep package wrappers until release notes explicitly declare their removal; do not delete product compatibility code locally.

Attributes and stable data

FormerlySerializedAs preserves renamed field values, while MovedFrom helps Unity resolve moved types. Removing those attributes may make a clean new scene look unaffected while existing buyer scenes silently lose data. They are part of migration safety, not unused clutter.

Identifiers are an independent compatibility surface. Renaming a Chapter or Objective ID can invalidate links, handoff destinations, API calls, and stored keys even when serialized fields load successfully. Plan an explicit content migration before changing shipped IDs.