¶ Coding 
Coding is a section of the game unlocked via the Research Tree that allows the players to generate and use Coding Speed to create variables and Code. Code can be committed for experience or built for unique unlocks and upgrades, such as new nodes, reduced CPU costs, and increased productivity from your hardware nodes.
¶ Modifiers
Code can be given modifiers to increase or decrease the value of the code when commited and built. A unit of code can have none, all, or any combination of the following modifiers:
| Modifier | Quality |
|---|---|
| Bugged[1] | 0.25x |
| Tested | 4x |
| Optimized[2] | 4x |
[1] The bugged debuff from Pull Optimization, Pull Application, and Pull Driver is currently a separate, second, and identical modifier. Be aware that due to this duplication, they both can be stacked if debugging pulled code requiring two instances of Bug Fix
[2] With Research Tree unlocks, a unit of code can be optimized up to three times.
¶ Coding Guide
¶ Coding 101: Pulling Code and Bug Fixing
To unlock Coding, purchase the Coding Unlock in the Research Tree for 1.00e08 Research.
Unlocking the IDE in the Token Menu is highly recommended for Quality of Life.
Starting with the Code Interface:
- Generate Code Speed
- Use Code Speed to Pull Optimization Code to generate bugged Optimization Code
- Bugged modifier reduces Code Quality by 4x
- Use Code Speed to generate Primitive Variables for the Code Bug Fix node to generate Bug Fix Code
- Input Optimization Code and Bug Fix Code into the Fix Code node to remove the bugged modifier.
- Commit the debugged Optimization Code for Contribution.
- Connect the Contribution to the Code Interface to grow Code Level until better code (Applications) is unlocked.
The
If node is invaluable in balancing a Code System. It is vital to balance code systems to generate at the highest potential.
¶ Recommended Code Speed Allocation:
| Node | Ops Required |
|---|---|
| Optimization Code | |
| Pull Code Optimization | 4 |
| Bug Fix Code | |
| Code Bug Fix | -- |
| Code bool | 1 |
| Code int | 1 |
Upon unlocking Build Tools for 1.00e08 Research in the Research Tree, the Build node is unlocked. Split the output of Fix Code between Commit and Build. This will generate Optimization Points upon inputting enough Optimization Code. Collected automatically, these points allow the purchase of CPU upgrades to specific nodes of your choosing, reducing CPU Clock Speed costs by 50%.
¶ Coding 201: Building Optimization Code and Debugging
Purchasing the Optimizations unlock for 1.00e09 Research in the Research Tree will unlock the ability to use Primitive Variables and Variable Combiners to generate Optimization Code without the bugged modifier. Replacing the Pull Optimization Code node with the Code Optimization node will generate 50% more Optimization Code by temporarily removing the need to Fix Code.
¶ Recommended Code Speed Allocation:
| Node | Ops Required |
|---|---|
| Optimization Code | |
| Code Optimization | -- |
| Code bool | 1 |
| Code int | 1 |
| Code float | 2 |
Creating Code from Variables will always be more efficient than Pulling Code.
¶ Unlocking Debug
Purchasing the Debugging unlock for 1.90e10 Research in the Research Tree will unlock the Debug which applies the Tested Modifier improving quality of the code and the resulting output of Contribution and Optimization Point build rate. Fix Code will need to be re-added to the system as the Debug splits the inputted code in half; half Tested and Tested and Bugged. Fix the bugged output from the Debug node and combine the Tested and Fixed Code from the Fix Code node in a Repository and then split the output between Commit and Build.
Take advantage of nested If nodes to balance Code Speed to the three systems:
¶ Recommended Code Speed Allocation:
| Node | Ops Required |
|---|---|
| Optimization Code | |
| Code Optimization | -- |
| Code bool | 1 |
| Code int | 1 |
| Code float | 2 |
| Debugging | |
| Debug | 4 |
| Bug Fix Code | |
| Code Bug Fix | -- |
| Code bool | 0.5[1] |
| Code int | 0.5[1] |
[1] For Code Bug Fix, at this point you'll want to send the equivilant of 1 ops to Code Bug Fix instead of 2 ops because only half the output of the Debug Node requires to be sent to the Fix Code Node.
¶ Coding 202: Applications
Purchasing the Applications unlock for 1.00e11 Research in the Research Tree will unlock the Code Application node and Array Variables. At this point, create a system to generate Application Code and mirror the Debug set-up for Optimization Code. Replacing Commit Optimizations with Commit Applications will generate significantly more Contribution. Continue to Build Tested Optimizations, while building and committing the newly generated Tested Application Code.
Remember to use nested If nodes to balance the new additional system.
¶ Recommended Code Speed Allocation:
| Node | Ops Required |
|---|---|
| Optimization Code | |
| Code Optimization | -- |
| Code bool | 1 |
| Code int | 1 |
| Code float | 2 |
| Debugging | |
| Debug | 4 |
| Bug Fix Code | |
| Code Bug Fix | -- |
| Code bool | 0.5 |
| Code int | 0.5 |
| Application Code | |
| Code Application | -- |
| Code int | 4 |
| Code char | 4 |
| Debugging | |
| Debug | 8 |
| Bug Fix Code | |
| Code Bug Fix | -- |
| Code bool | 0.5 |
| Code int | 0.5 |
General Rule of Thumb:
- Commit only the highest tier of Tested Code available:
- Optimization Code → Application Code → || Driver Code ||
- Build all Code Types with the Tested Modifier until you do not require any more of their respective points.
¶ Coding 301: Code Optimization
Purchasing the Code Optimizations unlock for 1.60e13 Research, Double Optimizations for 3.30e15 Research, and Triple Optimizations for 1.10e18 Research in the Research Tree will unlock the ability to further increase Code Quality by 4x/16x/64x respectively by using generated Optimization Code in the Optimize Code node in combination with other code.
At this point, it is prudent to redesign the systems for efficiency. Start by:
- Create a system that generates Optimization Code
- Split the output of Code Optimization to all the inputs of Optimize Code evenly.
- Take the output of the Optimize Code node and input into the Debug node.
Note: This method will be simpler than balancing the output of Code Optimization between the other systems and futureproof the system for Double Optimizations.
- Create a new Application Code system or redesign the current system by removing the Debug.
- Optimize Code passes any modifiers on the Optimization Code to the targeted Code, including Tested and Optimized.
¶ Recommended Code Speed Allocation:
| Node | Ops for Build Optimize Only | Ops for Double Build |
|---|---|---|
| Optimization Code | ||
| Code Optimization | -- | -- |
| Code bool | 2 | 4 |
| Code int | 2 | 4 |
| Code float | 4 | 8 |
| Debugging | ||
| Debug | 4 | 8 |
| Bug Fix Code | ||
| Code Bug Fix | -- | -- |
| Code bool | 0.5 | 1 |
| Code int | 0.5 | 1 |
| Application Code | ||
| Code Application | -- | -- |
| Code int | -- | 4 |
| Code char | -- | 4 |
Continue to build this optimization code while splitting the output between Build and Optimize Code: Application. Overall, these three modified systems will generate a higher throughput of quality Optimization and Application Code and build both while committing Application Code.
¶ Coding 401: Drivers and Hardware Multiplier
Purchasing the Drivers unlock for 1.00e14 Research in the Research Tree will unlock the ability to generate Driver Code which, when built, will provide Hardware Multiplier providing a boost to Hardware Nodes, such as the Network, Processor, and GPU Cluster nodes.
¶ Recommended Code Speed Allocation:
| Node | Ops for Driver Build Only | Ops for Driver + Optimization Build | Ops for Triple Build |
|---|---|---|---|
| Optimization Code | |||
| Code Optimization | -- | -- | -- |
| Code bool | 3 | 6 | 9 |
| Code int | 3 | 6 | 9 |
| Code float | 6 | 12 | 18 |
| Debugging | |||
| Debug | 4 | 8 | 12 |
| Bug Fix Code | |||
| Code Bug Fix | -- | -- | -- |
| Code bool | 0.5 | 1 | 1.5 |
| Code int | 0.5 | 1 | 1.5 |
| Application Code | |||
| Code Application | -- | -- | -- |
| Code int | -- | -- | 4 |
| Code char | -- | -- | 4 |
| Driver Code | |||
| Code Driver | -- | -- | -- |
| Code int | 2 | 2 | 2 |
| Code float | 6 | 6 | 6 |
| Code char | 8 | 8 | 8 |
Once unlocked, Driver Code should be the only code type Committed to Contribution.
Ensure to use and balance your system with
After purchasing Double Optimizations for 3.30e15 Research, the system will automatically apply two stacks of Optimization to Drivers apply an additional 4x multiplier to Build and Commit rates. The Code Optimization node that receives drivers will pass the current modifiers on the Optimization Code (Optimized + Debugged) while adding a second Optimized modifier on top.
Due to a bug, if Code Optimization is not applying the correct amount of modifiers, delete and replace the node.
After purchasing Triple Optimizations for 1.10e18 Research in the Research Tree a second Optimize Code node should be added between the first Optimize Code node and Debug.
¶ Final Recommended Code Speed Allocation:
WIP
¶ List of Coding Nodes
Interface
Management
Procesess
Pull Optimization Code
Pull Application Code
Pull Driver Code
Commit
Fix Code
Build
Debug
Optimize Code
Variables
Related
¶ List of Coding Resources
Basics
Unused Array Variables
Complex Array Variables
Primitive Array Variables
Unused HashMap Variables
Complex HashMap Variables
Primitive HashMap Variables
