Procrastinidler
Be honest... Your life is a mess, and you’re in dire need of organization and self-improvement. Procrastination might as well be your middle name. But what should you do?
Well, you can deal with all that later—for now, you should play Procrastinidler. Your problems will magically disappear anyway, so why worry?
Play it at the office for all I care. The UI was designed to look like a real application, so your boss won’t suspect a thing.
How to play: Pretend you have things to do. Create tasks and complete them. If it gets too hard, hire fake people to help you out.
Development log
- Performance upgrades1 day ago
Comments
Log in with itch.io to leave a comment.
for some reason i can't get money, i am completing the tasks, but they aren't giving money
Do you see any errors in your browser's console? Press F12 to open it and complete a task. I'll look into this issue later today.
here are the errors
That's annoying. I never had this error before. I'll see if I can fix it.
You cant just let the DOM fill up with an unlimited amount of nodes. Put a limit on it and delete old ones. It doesnt take long for it to completely fill up the allocated memory, and since it is saved that makes it crash instantly upon loading.
I was already limiting them to display 50. Now i reduced it to 30, but also did other performance optimization that should make the game run smoother. Let me know if it's better now please.
I looked more closely at it. Wasnt too easy due to the obfuscation but i found that each new task dets added to a storage object but never removed. This is guaranteed to run out of memory eventually. I saw what looked like code meant to prevent completed tasks getting added but they are already in the object so it does nothing. I recommend changing storage of tasks to be in arrays instead of objects.
Probably smart to make them 3 separate ones and whenever appending to the list use array.shift() right after if it is longer than 50 (For convenience you could add your own method to the array to handle this). If you ever need large key/value with arbitrary keys later i recommend using a Map(). This should be faster in most cases. If you dont need keys then there is Set() instead, but these dont guarantee an ordering to their entries.
Thanks for the thorough investigation haha. Good catch on the completed objects issue. I did have a bug there.
As for the other suggestions, I'll look into them if I decide to go forward with this project. I'll do an overhaul on the whole system for sure.
Very simple and fun, loved it. The only issue i can find is how hungry the the game gets for my cpu as i hit max stats. Maybe a way to hide tasks since they hit full automation?
I just pushed an update with performance optimizations that should make the game run smoother. Let me know if it's better now please.