Jump to content

Talk:Modifying an existing level: Difference between revisions

m
no edit summary
mNo edit summary
mNo edit summary
Line 226: Line 226:
The bigger idea is to write '''universal information into agent md''' so the actual '''session instructions can be shortened'''.
The bigger idea is to write '''universal information into agent md''' so the actual '''session instructions can be shortened'''.


Agent md
<pre>
<pre>
---
---
Line 240: Line 241:
C#-based Onisplit source code is located at ...\OniSplit-src-net10
C#-based Onisplit source code is located at ...\OniSplit-src-net10


Read test data from ...\Oni\AE\GameDataFolder if needed, but write outputs to GitHub-ignorable subfolders of the individual's local OniSplit codebase to avoid conflicts with the source code and to keep test outputs organized and separate from source files.
Read test data from ...\Oni\AE\GameDataFolder if needed, but write outputs to github-ignoreable subfolders of the individual's local OniSplit codebase to avoid conflicts with the source code and to keep test outputs organized and separate from source files.
Use .test-output for outputs and comparisons to reach hash-based conclusions about parity between C# and VB builds.
Use .test-output for outputs and comparisons to reach hash-based conclusions about parity between c# and vb builds.


When conversions with this VB-based application fail, test the same command with the C#-based Onisplit.exe to check if the issue is VB-specific or shared.
If roundtripping is requested, get specified files (or naming pattern) from active user prompt, then extract oni files to xml and create oni again. Analyze diff in xml and hash-diffs of old and new oni files. Patch vb codebase to make roundtripping work and reach oni-hash-parity: Ignore-exception: Descriptors IDs like in TRAC id="6787" are not preserved because irrelevant and will be resetted to 0.
If shared, then it's not a parity issue and should be fixed in both builds together. Skip (but document) shared issues for now and focus on VB-only issues.
 
If VB-specific, then it's a parity issue and should be fixed in the VB codebase to match the C# behavior.
When conversions with this vb-based application fail, test same command with the c#-based Onisplit.exe to check if the issue is vb-specific or shared.
If shared, then it's not a parity issue and should be fixed in both builds together. Skip (but document) shared issues for now and focus on vb-only issues.
If vb-specific, then it's a parity issue and should be fixed in the vb codebase to match the c# behavior.
</pre>
</pre>
Prompt
test roundtripping of TxtC*.oni files


=====Session instruction example=====
=====Session instruction example=====
8,979

edits