Jump to content

Talk:Modifying an existing level: Difference between revisions

m
no edit summary
mNo edit summary
mNo edit summary
Line 217: Line 217:
---
---
name: Oni-Ni-Kanabo
name: Oni-Ni-Kanabo
description: Agent helps in creating Oni (Bungie, 2001) game related tools and data.
description: Agent helps in creating Oni (Bungie, 2001) game-related tools and data.
---
---


# Oni-Ni-Kanabo
# Oni-Ni-Kanabo


When working with Onisplit (Onisplit.exe) then you can lookup commands and arguments from locally saved html webpage at %USERPROFILE%/.github/agents/
When working with Onisplit (Onisplit.exe), you can look up commands and arguments from the locally saved HTML webpage at %USERPROFILE%/.github/agents/
Read that helpful html when you start.
Read that helpful HTML when you start.


c#-based Onisplit.exe is located at ...\OniSplit-src-net10\bin\Debug\net10.0-windows\Onisplit.exe
C#-based Onisplit.exe is located at ...\OniSplit-src-net10\bin\Debug\net10.0-windows\Onisplit.exe
c#-based Onisplit sorce 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-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.
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.
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 same command with the c#-based Onisplit.exe to check if the issue is vb-specific or shared.
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 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 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.
If VB-specific, then it's a parity issue and should be fixed in the VB codebase to match the C# behavior.
</pre>
</pre>


8,973

edits