Algodoo

The white circle was supposed to be a cookie. Oh well.

Nothing different happens after 15 cookies.

Also, what is an "upgrade"? You do not explain it.

Also, you say in the scene "upgrades stop at 1000 because number will overflow to infinity". Why will that happen? It makes no sense unless you are doing something weird in the calculations.

No, I mean if it did, some values will go to "Infinity" because it goes past the largest finite value (3.4028235e38).

And a upgrade is 1 cookie per second at first, but multiplies the number 1 by 1.07 and repeats every time you buy again. But the value will be nonillions at the end. So this is why it will stop at 1,000.

The "0 total wasted cookies in total" was a accident when I did not notice it. But I will fix the bugs soon.

And also, this was some of the "first" correct clicker games in Algobox.
It has a reactor which adds up the cookies by the cPs "cookies per second" value divided by 50. Why 50?, because 60 is uneven sometimes with the "6" trail.
The upgrades and the text is the ones with the most code.

Really badly done. lemme tell you why

-It doesn't work. You didn't even care to download the scene and check the console.

-Instead of ranting about your obsession with number types and stuff, why didn't you find a way around it? There are lots of ways I'm thinking of right now, which would give you more than enough (3.4e38 ^ 2 is enough for you I guess? Or ^3?) The easiest one would be continuously asking if the total number is above a certain number (for example you could use 1e38) and subtracting 1e38 to it if it is, then adding 1 to another variable. Like:
(use any object's postStep or update)
postStep = (e)=>{scene.my.total > 1e38? {
scene.my.total = scene.my.total - 1e38;
scene.my.totalx = scene.my.totalx + 1
}:{}
}
Then just find a way to let your code know.

-You use scene.my everywhere... You can use much less and make a much better code if you actually use local values on the cookie. Just write
_total = 0
and as many variables as you can use to do internal calculations, on the blank textbox below the title of the cookie's script menu and use that instead of the scene.my on the code. Then put the text script on the cookie, and output the text via one scene.my. For the upgrades you can use a scene.my variable that outputs true once you click the box (onclick scene.my.c=true), and when the cookie receives it (sc.my.c ? {sc.my.c = false; whatever code you need}) it executes code. THis way you cramp all of the code on the cookie and only get data from local variables.
Also you can sue functions if you want to reduce the code size on postStep or onClick, but I didn't find much code where you could use functions

But it was for fun for myself anyway.

3.4028237e38 ^ 2 AND 3 will be past the boundaries. (2^128^2=1.157920892e77).
(2^128^3=3.94020062e115)­.
And because for making me a bit sad about this comment, I will remove this game tommorow for 2 days.

And JEEZ, you will not need to write a WHOLE NOVEL on this game.
I thought "Xray" would comment. But it was you... "The Linkage"...
I will see your comment, but if it is ANOTHER NOVEL, then I will delete it PERMANENTLY.

And if it is VERY BAD "The Linkage", then it is MY OPINION. YOUR COMMENT IS YOUR OPINION AND I WILL NOT LEARN WHAT YOU SAID AT ALL!!!!!!

Why? Because if I did that, then I will hate you "The Linkage".

Hey GoAnimateCPUAlgodoo -- Settle down! The Linkage did not say anything that was maligning, insulting, or threatening you. He was only trying to help you by giving you some technical suggestions. Maybe you didn't like the fact that he was a little verbose, but that's not a reason for you to overreact like you did. If you don't like his reply, or if you don't agree with it, either tell him that, or just ignore him. The wrong thing to do would be to lash out at him your own threatening comments.

You have the right to remove your scene if that's what you want to do, but you do not have the right to send him hate comments like the one that you recently posted.

Algobox is all about fun and education. So, lets just focus on those goals!

Thanks,

Xray, Algodoo Admin

Ok.

Okay, I guess I'll cool down a bit. but you seemingly didn't get my suggestion about bigger numbers

If I write a novel it's because there are lots of things to correct in your scene. More so when you claim that it will overflow and stuff like that... if you are working with numbers this big, instead of putting limits and thinking there's no other possibility, you can fix this with just a minute of thought:

Think about an old 7-segment calculator screen. The minimum number it can display is 0 and the maximum, 9. yet the whole screen can show numbers much bigger, say, 99999999 for an 8 digit screeen. So how is this possible, when the maximum number is 9? Sending a 10 to the screen would not make sense...
So you can separate your number in, say, 8 parts if you have an 8 digit screen, so that 12345678 will be distributed between all 8 screens. Here you can do something similar but much easier:

Say you have 1e10, that's 10000000000. Imagine that the maximum number Algodoo can handle is that one. When you get to that number, you can simply separate it into two parts: you just make a variable that will hold values above 1e10, and you put the ones below 1e10 on the one you already had. So if you want to save the number 4237992450, you can do:
_value = 237992450
_value10 = 4

For the number 132534534543254354 you can do:

_value = 543254354
_value10 = 132534534

Maybe now you'll notice that if you save two numbers you can get double the exponent, so if you had a maximum of 1e10, now you can save numbers with 1e20 size. But you can't do operations directly because they would overflow. Just find workarounds, it's not hard in any way

Or just do this. (Start at 1e-36, then make it that looks like one. So that way, this makes number until 2^250-ish (Trevigintillions).

I have 8 digit, 10 digit and 12 digit calculators that include 7-segment numbers.

Or one day, we will make 64-bit floats for algodoo with extensive Thyme coding.

64-bit floats support a range from 5e-324 to 1.8e308.)

And even then, how am I going to make the "_val10" variable move properly? A floor function?

I have a system for decimal point number that is running all the time. Not in Algodoo yet. Like this: ("5"/"13")="0.38461538461538461538"

It is complicated, but it does the job.

And why it is overflowing? Because if I use 1200 upgrades, it will be too powerful and make a special number called "+Inf".
And _value integers can be useful, but sometimes you will need to make _val10, _val20 etc., Then I need to make a way that makes the numbers go to 0 in a thyme function.

And this. Could I "keep this(A)" or "remove it completely(B)"?

And I did not know The Linkage will appear here. I think when i commented, I type "code" in, and caused The Linkage to see my project.

Me looking at my older comments just... just makes me embarassed! How stupid was I back then? Very I guess!

No, you were not being stupid. You were just learning. Sometimes we make statements which are not accurate or may be confusing, but that doesn't mean we are stupid. We just need to learn better ways of expressing ourselves. And you are never too old to learn. I'm pretty sure that I am the oldest person who uses Algobox. I won't say exactly how old I am because it doesn't matter, but my point is, even at my age, I still have a lot to learn, and I love learning about new things and new concepts and new ways to do things!

Well, ok I guess.

OFFTOPIC! Personally, my new hobby is coin collecting, if you don't know what this means, I will tell them. What coin collecting means is someone that has old, commemorative or otherwise, error coins. I don't like posting massive comments so I will end it here. I will tell more if someone makes a comment here.

This is bad.
Reasons:
-You need to reset to be able to play the game
-Why is there half cookies or 0.01 cookies? That doesnt makes sense.
-the upgrades doesnt even have names!
-There is no visual stuff
-The cookie is a white circle
-you didnt edit to change anything..