Skip to content

Keep player input in context when game time is frozen - #675

Closed
RANGROO wants to merge 1 commit into
unstablefrom
codex/discord-1534586971077218334-frozen-timescale-context
Closed

Keep player input in context when game time is frozen#675
RANGROO wants to merge 1 commit into
unstablefrom
codex/discord-1534586971077218334-frozen-timescale-context

Conversation

@RANGROO

@RANGROO RANGROO commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

Problem

When Skyrim's timescale is set to 0, gamets stops advancing while NPC prechat and chat rows retain their synthetic +1/+2 values. buildHistoricContext() therefore keeps ranking NPC rows above newer player input until the bounded history window excludes the player entirely.

Discord source: Open Discord thread

Change

  • Select historic-context rows by descending eventlog rowid, which represents server insertion order.
  • Keep the existing reverse step so the final prompt remains chronological.

Validation

  • php -l lib/data_functions.php: passed.
  • git diff --check: passed.
  • Rollback-only PostgreSQL probe: the old ordering selected four older NPC rows; rowid DESC selected the latest player input first.
  • Existing HistoricContextTest.php: blocked by a pre-existing sql::escapeLiteral() error; the same failure reproduces unchanged on current origin/unstable.
  • Deployed the exact feature file to the local HerikaServer runtime; SHA-256 matched and the UI returned HTTP 200 on the configured Apache port.

Coordination and limits

@RANGROO RANGROO closed this Aug 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant