The particular issue I've got is actually fairly early on.īut then there's five (5) bytes between the end of WidthInCells and the start of HeightInCells. Ok,what's your discord address? and how do I send you my file for you to look at what may be causing the game to fail? Se você quiser entrar no canal de modulação de discórdia, eu ficaria feliz em ajudá-lo a investigar mais! Você pode achar mais fácil de entender em sua forma de monólito pré-refatoradora. Esta seção chega perto do início do arquivo, lista o nome / campos / propriedades de muitos dos objetos usados no arquivo e permite que o analisador manipule a maioria dos dados sem compreendê-lo antecipadamente. O bit estranho é o modelo de dados, que foi dividido em vários arquivos (muitos). Isso geralmente é um bom arquivo para trabalhar, pois contém as principais estruturas do save, e eu tentei manter os campos em ordem.Ī análise real é feita na pasta de implementações, através da função parse (). Mais uma vez, vou precisar do seu arquivo salvo e exatamente o que você está modificando para descobrir o problema.Įu comecei a documentá-lo em um ponto, você pode ver os restantes pedaços de documentação em. Algo sobre o seu arquivo salvo ou o estado do jogo não gosta de uma das mudanças que você está fazendo. Funciona bem, então o problema não é simplesmente modificar qualquer 3. If you want to hop into the discord modding channel, I would be happy to help you dig into it more!Įu tentei modificar qualquer número de habilidades em muitos duplicantes. You might find it easier to understand in its pre-refactor monolith form. This section comes near the start of the file, lists the name/fields/properties of many of the objects used in the file, and allows the parser to handle most of the data without understanding it ahead of time. The weird bit is the template data, which has been split into multiple (too many) files. The actual parsing is done in the implementations folder, through the parse() function. Thats generally a good file to work through, as it contains the major structures of the save, and I tried to keep the fields in order. I had started on documenting it at one point, you can see the remaining bits of documentation over at. you are in a maze of twisty files, all alike. Is there a description of the save format anywhere? I keep seeing references to 600 as the game-time of 1 cycle as well. The experience to the next level from the current one would naturally be the experience from 0 to next, subtracted by the experience from 0 to current (the "num" variable above) upon closer look, I would guess that the total experience required to go from level 0 to level TargetLevel is In my hazy, sleep deprived state, it sort of maybe looks like Triangular Numbers, which I have used when writing similar leveling systems. I'm sure this math can be explained easier, but its too early in the morning for me to attempt to understand what its really doing. (currentLevel + 1) / MAX_GAINED_ATTRIBUTE_LEVEL,
#SAVE GAME EDITOR LICENSE#
The editor and its underlying library is fully open source under the MIT license, meaning you can do whatever with it so long as you include the license and my copyright notice with it.ĬurrentLevel / MAX_GAINED_ATTRIBUTE_LEVEL, The site is built in Typescript using the React framework, with Redux as a backing store.īoth projects are written in Typescript, and can be found here: Please report bugs and make feature requests at: Use the save editor at your own risk! Use it sparingly, and do not report crashes for saves modified in uncanny ways. They are what changes the dup's stress or stanima, but do not trigger the actual behavior. * While you can find effects like "Vomit" and "NarcolepticSleep" in here, they are purely the "effect" of such conditions.
#SAVE GAME EDITOR OFFLINE#
Offline editing: Under settings, enable "Offline Mode" for use when no internet is available. Local editing: The save file is never sent to any server all edits are performed in browser A browser-based tool for editing ONI save filesĬompatility follows the most recent stable branch
0 kommentar(er)
