abe7a43eec
We are getting some more error reports coming in that don't have enough info in them. It turns out that populating the stack trace was gated behind the dev flag; in reality, production builds are where we need it most. Even if it ends up being obfuscated (source maps should prevent this), we can figure out the actual source lines with enough effort if need be. This also changes to using the actual stack trace, rather than the "component" trace (the tree of JSX objects), since knowing where the code failed is far more valuable. Also, it ensures we get the full error details when things go wrong in savefile loading. |
||
|---|---|---|
| .github | ||
| assets | ||
| dist | ||
| doc | ||
| electron | ||
| lore | ||
| markdown | ||
| src | ||
| test | ||
| tools | ||
| .browserslistrc | ||
| .dockerignore | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .git_blame_ignore_revs | ||
| .gitattributes | ||
| .gitignore | ||
| .nojekyll | ||
| .npmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| .readthedocs.yaml | ||
| api-extractor.json | ||
| babel.config.js | ||
| changelog.md | ||
| CODE_OF_CONDUCT.md | ||
| favicon.ico | ||
| FixJSDOMEnvironment.ts | ||
| jest.config.js | ||
| jest.polyfills.js | ||
| license.txt | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| requirements.txt | ||
| tsconfig.json | ||
| webpack.config.js | ||
Bitburner
Bitburner is a programming-based incremental game that revolves around hacking and cyberpunk themes. The game can be played at https://bitburner-official.github.io/ (release build), https://bitburner-official.github.io/bitburner-src/ (development build), or installed through Steam. The location of the release build may change in the near future.
See the frequently asked questions for more information . To discuss the game or get help, join the official Discord server.
Documentation
The game's official documentation can be found in-game.
The in-game documentation is generated from the TypeScript definitions.
Anyone is welcome to contribute to the documentation by editing the source files and then making a pull request with your contributions. For further guidance, please refer to the "As A Documenter" section of CONTRIBUTING.
Contribution
There are many ways to contribute to the game. It can be as simple as fixing a typo, correcting a bug, or improving the UI. For guidance on doing so, please refer to the CONTRIBUTING document.
You will retain all ownership of the Copyright of any contributions you make, and will have the same rights to use or license your contributions. By submitting a pull request you agree to grant me perpetual, worldwide, non-exclusive, transferable, royalty-free, and irrevocable rights to use, publish, and distribute your contributions to the project. A formal Contributor's License Agreement will be drawn up in the future.
If you would like to make significant contributions to the project as a collaborator, please reach out in #suggestions or #development on Discord to help coordinate the effort.