Assess supplied jn-engine research and capture evidence
This commit is contained in:
1 parent
c0acf58d9c
commit
c6eb1861cd
8 files changed
+347
-1
No files matched your search
@@ -231,3 +231,11 @@
|
||||
mount/control handoff and wheel-dependent drive/support cannot be represented
|
||||
by a Jimmy mode or an invented constant wheel count. Preserve the source
|
||||
report/exporter and close wheel bodies before live Scooter integration.
|
||||
41. **Use supplied jn-engine as research, not a replacement runtime.** Same EXE
|
||||
declaration and415 byte-identical shared assets support cross-indexing its
|
||||
class specs/decompiler bodies and adapting bounded tests. Different declared
|
||||
OMT2.dll, mixed pointer bases, forced prototypes and explicit native gameplay
|
||||
tunings require independent checks. Retain C#/.NET10/SDL3/Vulkan and REA byte
|
||||
evidence. Capture tooling/derived scenes are present; raw OMTC, analysed
|
||||
Ghidra database and proposed gameplay state traces are not. Record offered
|
||||
permission before source import. Assessment: reviews/jn-engine-survey.md.
|
||||
Reference in new issue
Block a user