mehirc
18-04-04, 19:45
Maybe that idea has been mentioned somewhere sometime ago already but i will post it anyway. This idea is to improve click&wait processes without affecting the time KK wants to need things and without beeing too automated.
The problem is, that there are lot of things that you have to do repeatedly up to hundred times but each thing is not long enough to do something else meanwhile. So you have to click and wait all the time.
What we need is to be able to queue processes a few times.
My idea is to put for example a researchtool and an item into the processor together with ten empty cubes and start it. All ten would be done one after another but would still need the same time.
Or put the constructor tool in it together with eleven blueprints.
Same with LOMs, use as many LOMs as synaptic impairment you can have. You could at least take two LOMs at once.
There are also other processes that could be handled like this and make people a little less click&wait.
The problem is, that there are lot of things that you have to do repeatedly up to hundred times but each thing is not long enough to do something else meanwhile. So you have to click and wait all the time.
What we need is to be able to queue processes a few times.
My idea is to put for example a researchtool and an item into the processor together with ten empty cubes and start it. All ten would be done one after another but would still need the same time.
Or put the constructor tool in it together with eleven blueprints.
Same with LOMs, use as many LOMs as synaptic impairment you can have. You could at least take two LOMs at once.
There are also other processes that could be handled like this and make people a little less click&wait.