I agree that this should be fixed, though if you Dertseha make it as some sort of patch for the. Judging by the comments, those new to the game hardly see a difference and are even given a chance to avoid backtracking if they don't like to - and veterans note down the digits right away anyway, since they're spoiled already. * People are at some arbitrary point in the game and would like to have their savegame retro-fitted (would require a small executable patcher, which is easier to do) * People stumble over EE, read about the problem before starting a new game, and download the patched archive to use Though, thinking some more - what is more likely: To make things even more interesting, level 1 has only 20 slots free for such marker objects to implement this chain.
While the variables are handled as binary values, the actual code is stored as BCD (Binary Coded Decimal - i.e. This whole chain needs some extra logic to keep the numbers sane.
This tile-entry-trigger stops the 6 timer. Then, set a tile-entry-trigger at some tile hacker has to go through, like the passage before the mutant cyborg guarding the CPU room. My thinking goes: Start 6 timer on level entry with various randomness. Then I remembered that you can start timer with a randomness in them! I was thinking about taking the security value into account, yet this one has low entropy, especially since the reactor code should be fixed before the first CPU nodes are destroyed. It is possible to set game variables, yet for the reactor code we'd need some random seed. Thinking about it, there is a chance to "fudge" a semi-random number. Whether by accident or intentional is up to the maintainers. This then concludes that the fixed code comes from the engine. Finally, I did a binary compare between the EE archive.dat and the one from the original CD and found no differences. I did a search in the archive and a quick glancing look at the first level, and I couldn't find an action that would set the two variables. Update: I've had a look at the archive and two test savegames.įor my installation I can confirm that the code is the same as for the other people.
0 kommentar(er)
