Maybe might explode? who knows.
NEW AWESOME TIMING SECTION
"help: Displays this menu" (displays help menu)
"go: ends initalization starts program" (displays the display and enables reactor processing! NEEDED TO START)
"stop: Ends Program" (Halts the program)
"fueledit: lets you edit fuel ratio" (Fuel edit mode, edit the input gasses and view them too!)
"rodedit: lets you edit control rods" (View individual rod type and integrities, and insert (or remove) rods)
"rp: Rod insertion percent" (self explainatory)
"fire: shoots level 3 pa blast" (basically turning the PA on for one blast at level 3)
"sync: toggles time syncing" (the jump ahead when you pause or go too fast)
"speed: sim speed" (Simulation speed, literally the time it takes between process ticks (and commands))
"clearalarms: clears alarms"
"skip: skip forward in time" (skips that amount of process ticks, every process tick is 2 seconds real time)
"display: toggles display, disabling increases speed" (says what it is)
"displayclear: toggles display clearing, disabling increases speed at the cost of your vision" (says what it is)
"polledit: setup averages polling or reset" (how many samples we will take before looping, and also views samples, resets taken samples on save)
just compile and run the .exe make sure the config.txt is there
^^ should look like this
Dont input commands or numbers incorrectly or you DIE (Not actually, just press ctrl+c to get out of infinite loops, file system is READ ONLY)
This is my first time actually coding.
example:
fueledit
GAS_O2
14
GAS_N2
15
GAS_PLASMA 42
mols
100
view
save
close
AND:
fueledit GAS_O2 14 GAS_N2 15 GAS_PLASMA 42 mols 100 view save close
are functionally equivalent.
go + fire does not work (anything that closes the command prompt)
Use at the risk of infinite console spam (press ctrl+c to close duh)
Likes to trigger windows defender, You can just read the source code within 10 mins its tiny. Ok maybe not anymore... doesn't trigger windows defender anymore for me though!
If you want to simulate really really fast, set pollcount to 0, and use skip, or turn off display and display clear and set speed to 0 depending on your purposes. Skip uses unsigned long int, though since every process is 2 seconds divide that by two and you have the max skip amount... not that you will be able to simulate millions of years though. Maximum reasonable time to skip is like 4-11 hours, which is like a millisecond, 130 years takes like 5 minutes maybe... (you arnt playing spessmans that long i fucking hope) Skip also stops when the reactor is a process tick away from meltdown, usually when the rods deplete or stability effects past 8/12mw destroy you with 90-c temp jumps from two tesla zaps.
Skip may seem weirdly slow at small values, a sim speed of 2000ms (default) will have any command take 2000ms to take effect dispite how fast it may be.
EXCEPT NOT NOW HAHA
IF YOU WANT TO SYNC WITH AN IN GAME REACTOR PRESS 9 AS SOON AS THE ACCELERATOR STUFF HITS THE REACTOR!, THIS WILL WORK "GOOD ENOUGH"
I USE THE G++ compiler with make (so i dont have to type in commands every time) if you have ever compiled C++ from command line with make its the exact same as anything else just type "make" (with the cmd directory at the same locaton as the makefile obviously) it just runs, "g++ -O2 STORMDRIVE.cpp -o STORMDRIVE.exe"
Thanks and have fun :)