When two bodies get close and start to move really fast, the simulation accuracy breaks down. This is clear because when two bodies are orbiting each other, their orbital paths should never change (ignoring gravitational wave effects, that's endgame simulation). However, if the bodies get really close, their orbits can change substantially and even launch them into escape velocities. The ultimate problem here is that the simulation timestep is too big for these scenarios. Would it be possible to either lower the global simulation time step, or figure out a way to change local timesteps when planets have high expected velocities?

A body has a few properties:

• Name
• Mass
• Radius
• Position (x, y)
• Velocity (x, y)
• Color

When adding a new body to the universe, the player has to manually input everything through textboxes. This is an ugly solution that makes it difficult to know where things are going and how they'll interact with other bodies. The name and mass I think are fine (except that the mass uses stupidly large units) but position and velocity should be a matter of clicking somewhere in the simulation and dragging to "slingshot" the planet. I think the radius is fine but it'd be cool to make that a visible element before the player places the body and maybe they could change it by scrolling.

• Changed the cookie policy in case of being hosted on another website
• Remove unused name field (for now)
• Simplify drop adder by using preset sizes
• Remove show/hide saves button
• Fix some styling

• Added a cookie policy
• Fixed a critical bug that deletes more bodies than necessary when high velocities are involved
• Added the ability to load and save configurations
• Use cookies to maintain configurations across browsing sessions if enabled

• Fix issue where drop adder isn't disabled when not selected
• Move some text based elements
• Move the debug section to above the canvas where it is more visible

• New body adder lets users drop in planets and drag to give velocity
• Remove bodies from simulation once they get too far away (another canvas size away)
• Separate out current body adder into "precise adder" that allows for precise velocity and position when adding
• Fix bug where bodies don't draw to screen when paused until unpaused

Closes #3

• Fix issue where checked simulation accuracy isn't used on refresh
• Make the settings text visible again
• Add a bit of space between the canvas and the rest of the site and give it a border

• Added a trail quality setting that lets users set the number of particles drawn to the screen
• Added a simulation accuracy setting that lets users set the accuracy of the simulation by choosing whether to use more or less simulation ticks per time step
• Improve the performance of the simulation several times over through a complete refactor of the code
• Set the default accuracy of the simulation to run 5 ticks per time step (instead of 1). This corresponds to 'medium' on the new simulation accuracy. The previous accuracy can be found at the 'low' setting
• Improve the accuracy of the Lagrange point demonstration by using higher precision calculations

Closes #6.

• Adds a debug menu that shows performance for simulation and draw times
• Remove some old print statements I forgot a while ago
• Optimize drawing by only drawing objects within the canvas
• Use JavaScript function requestAnimationFrame for properly drawing to screen

New Features:

• Adds a reset button that clears all the bodies
• Velocity is now a configurable option in the body adder
• Rust wasm is now completely safe (no static mutables)

Right now, the buttons and textboxes that let the player interact with the simulation are hot garbage. We need to stylize those buttons and make them more usable/pretty.