yaur's Comments

until the dev fixes how numbers are displayed I suggest switching to scientific.

fyi sort is a broken alpha sort so 9k is > 8b

this is what's left on kong... ugh

would like a way to show what percentage each node is contributing to my total at a glance so that I could figure out what blueprints to prioritize.

you don't get a reward if the reward leaves the play area, so make sure you scroll monsters in the forest away from the edge before fighting them.

Game now locks up the browser when trying to load the game :( only able to post from a different browser that doesn't have my save data.

Please make right-click or KEY+click flag a mine

@macosten The way investors work has been significantly altered (as in at least 1000 times faster) since people were complaining about it.

I switched from the largest board to the 4x7 because it cycles faster and have managed to get up to around 2.5b/s. I'm not sure how to get much higher than that, but I suspect it involves portals.

The star of wisdom doesn't doesn't actually know chemistry.

Popup when I try to leave? A new low IMO

Doesn't start for me. Chrome on Linux.

If a mission pushes you over the max for some stat (e.g. health) the game locks up.

It stops being a joke once you monetize it.

unplayably laggy on linux

pro tip: crafting doesn't consume crystals until you click "stop wheel" so at end game when you only need a few specific items you can refresh the page to reset the crafting options.

@tyronull yes, when you craft gear it will be a higher level than your highest level equipped weapon so getting to 999 is not hard, but a bit time consuming.

Shop is useless anyway. Just craft the lowest 2 crystal items, equip your highest level items, and you will be OP in no time.

Unless I'm missing something the angle based multiply profits upgrades don't make much/any sense. It takes 50 angles to get a 500% increase so why would you sacrifice 1 billion to get the same effect?

upgrades are poorly thought out. 1) Xs should block placing a mark. 2) running over an already set x shouldn't unset it.