nte-exporter/docs/limitations.md
Golumpa 20b2086299 Anchor scans to page 1; export stable prefixes
Anchor page-run selection to start at page 1 (select_continuous_run_from_page_1) instead of picking the longest run, so newest pages are preserved and the newest timestamp ordinal 0 is always captured. Change boundary logic to always assign stable UIDs and export the captured prefix of an oldest timestamp group even when it may be an unfinished 10-pull, emitting informational warnings (INCOMPLETE_TIMESTAMP_GROUP_EXPORTED / INCOMPLETE_ARC_10_PULL_EXPORTED) instead of dropping rows. Apply the same policy to Arc groups and update arc group annotation and warnings accordingly. Add a new console module for improved CLI output and update cli, live_capture, adapters, and session code to use the new run selection and console helpers. Update docs, mappings, and tests to reflect the new boundary/export behavior and messaging.
2026-06-11 12:22:34 +01:00

1.1 KiB

Limitations

This is a prototype and supports Lottery_Permanent, Lottery_LimitedCharacter, and Arc_MiracleBox.

Known limitations:

  • Other NTE banners are not implemented yet.
  • The game appears not to provide a unique server-side roll ID in the decoded record body.
  • UIDs are generated deterministically from decoded fields and timestamp-group order.
  • An incomplete oldest timestamp group is still exported (its captured prefix has stable UIDs) and flagged so the user can scroll further on a later scan.
  • Pages are anchored to the continuous run starting at page 1; pages after the first gap are ignored and reported as warnings.
  • Live capture currently uses Windows raw sockets and requires administrator permission.
  • The file adapter reads mitmproxy .flows captures for research and testing.
  • The more stable and reliable Npcap/libpcap capture is not implemented yet.
  • Reward keys decode to their reward id string, so unknown rewards still export a usable reward_id; display names/ranks come from the mapping JSON files and should be expanded as new rewards appear.

Privacy guardrail: raw packet data must not be included in sanitized exports.