Add a "stop mod" and "restart mod" button

Hi Aktanusa,

Nice Add-on for CookieClicker, CookieMonster BTW, thanks a lot...

I like your Add-on for the Stats and the Calculations (especially for how many Cookies to keep like the ""Lucky!" Cookies Required (Frenzy) : 52.989 Sext" (even if I think the Calculation might be wrong...), but your Add-on when loaded sucks about 30% of the Resources of the JS Engine on FF or PM (Pale Moon).

And the only way to get rid of it is to save and then reload the Game and start all my other Scripts running on the Game... (1 .js Script and 1 iMacros Script on the CookieClicker Page, + other iMacros Scripts running on other Pages running each in different Browser (=PM) Instances.) => So I miss an easy 'Kill me' Button (from the CC 'Menu' Page)... => As well as an easy way to land on your GitHub Repository (Forum), instead of having to google "CookieMonster"...

The other .js Script I use (not really public, made by a Friend, I first need to check with him if that Info can be disclosed...) has a RealTime CPS Calculator, and CPS go down instantly from Max 100cps to Max 60cps (hum => 40% JS Engine "Suck" actually) as soon as CookieMonster is loaded... This Friend of mine has already implemented a few things that are on your Requests List (like Buying the Most Profitable Building) and he found a few flaws in your Code, you might be interested to get in contact if he agrees... (but he doesn't really want to go public...)

(Your 'Next Cookie' and 'Next Reindeer' Time Calculations are always wrong BTW...)

(Using CookieMonster v.0466 (+v.0465) on Pale Moon v.24.6.2 (=FF31), Win7-64. + CookieMonster running from your Server, latest Version I reckon, even if it's difficult to find the Version...)

Whoa a lot of stuff here. I'll do little by little.

Thanks for the compliment.

I would like to know how is the cookies required calculation is wrong.

Are you requesting a "kill me" button? My impression is that you think the older Cookie Monster had such a button. If it did, I've never seen it before. It did have a performance setting though. When you say "miss" I usually get the impression that it was there before.

I'm surprise it was hard to find this forum as the Wikia links it. It even indirectly links it. How did you find out about Cookie Monster?

I would be interested in the flaws in my code. That be nice to know as I don't think I'm the best coder in the world or anything, lol. So yes I wouldn't mind talking to your friend.

If you didn't know, the way next cookie and next reindeer works is that there is a minimum time span and a maximum time span it can spawn. But it is random. I cannot right out tell you when it will spawn as it is random in CC itself. I can only tell you when the minimum time ends (grey bar) and when is the maximum time ends (color bar). There is a known guesstimated time span when it will span due to the way random is used though.

Version is listed on the bottom bar on the bottom left in yellow (default color) (if you have it enabled). There is also a tooltip that shows the version loaded when you first load the script.

Edit: FF (unsure about PM) is known to not have the best Javascript engine even though I dev on it. I made sure there was no memory leaks with Chrome though. Yes performance can be slow with slower computers, but a few things to speed up is the minimize CM stats you have no interest in or change the stats update interval in settings.

Hi Aktanusa, thanks for your quick Follow-up (which I saw when you posted it, except for EDIT only a few days ago), sorry I couldn't find the time to reply earlier but I wanted to do it right...

1- 'Kill me!' Button: "Are you requesting a "kill me" button? My impression is that you think the older Cookie Monster had such a button. If it did, I've never seen it before. It did have a performance setting though. When you say "miss" I usually get the impression that it was there before.

=> Yep-yep, by "I miss..." I mean "I would like to have a way to switch your Add-on easily off." I mean it as an EnhReq thus... The only way at this moment is to save the Game at some appropriate moment and to reload the Game (without CM), but very often I want to load your Add-on just a few seconds and kill it after... (because of the 40% JS Engine Suck), and yep, I know I can reduce a bit the JS Engine Suck by lowering/switching off some Features, but still, that's not optimal, because I like all the Info/Stats you provide...

2- "I would like to know how is the cookies required calculation is wrong."

=> Only from empiric Observations, the differences I notice between your Calculation for '"Lucky!" Reward (CUR)' and the actual Amount given by Golden Cookies is only before the Frenzy Threshold has been reached. From there it's OK. Your Calculation is made (and displayed) in real time, but you seem to be all the time in advance with Orteil's Calculation by 10-20-30 sec, and the real Amount is always a bit less than your Calculation, like if Orteil is not calculating '"Lucky!" Reward (CUR)' in real time, but based on some Save from some 10-30 sec ago. It's not from the automatic every 60 sec Save I think, maybe he's using some Temp Cookie...? Only once we reach about 90% of ""Lucky!" Reward (MAX) (Frenzy) : 3.351 Sext", then both Calculations are the same for a short while, and between 90% until reaching 100%, the real Amount is then greater than your Calculation...

3- "I'm surprise it was hard to find this forum as the Wikia links it. It even indirectly links it. How did you find out about Cookie Monster?

=> I actually found CM indirectly because of my Friend, as we were making a kind of a Competition between us with his Script in JS and mine in iMacros. Then we played a kind of a funny Hide and Seek and he told me he had uploaded it somewhere on Internet into some Git Repository he had created. So I ended up on GitHub searching for it (it was not there) and searched and downloaded all Projects on GitHub related to CookieClicker, with yours among them, which I tried... and liked. But after a few weeks, I only had your Bookmarklet (with Menu and Stats) with just a name to find Documentation and Forum.

4- "I would be interested in the flaws in my code. That be nice to know as I don't think I'm the best coder in the world or anything, lol. So yes I wouldn't mind talking to your friend."

=> Yep of course, I haven't spoken to him since, all I know was from loose Chat Conversations, he mentioned a "dirty" Loop like "while (1+1)>1...", but I couldn't find it in your Code myself. Next time I speak to him, I'll ask him a precise Feedback and if he maybe wants to post it himself...

5- Time Calculations for Next Golden Cookie and Reindeer: "If you didn't know, the way next cookie and next reindeer works is that there is a minimum time span and a maximum time span it can spawn. But it is random. I cannot right out tell you when it will spawn as it is random in CC itself. I can only tell you when the minimum time ends (grey bar) and when is the maximum time ends (color bar). There is a known guesstimated time span when it will span due to the way random is used though."

=> OK, I didn't (really) know indeed, though I had noticed there were some variation indeed.

For that one, I'm sure, it's always wrong (in my case), as I think that for your Calculations, you don't take into account certain Upgrades where GC's and Reindeers will appear twice or 5% more often...

Here are my empiric (again) Measurements:

Next Golden Cookie: Your Bar = 215s = 72s + 143s (gray-fixed + pink-random). => I always have between 85s and 114s left (from your 215s). => "My" Bar = 130s = 101s + 29s (fixed + random). (130s = 215s - 85s)
Next Reindeer: Your Bar = 180s = 89 + 91 (gray-fixed + orange-random). => I currently always have between 48s and 65s left (from your 180s). (Hum, and I'd even seen better before my last Reset, but I still miss 4 Eggs, then it was always between 65s and 85s left...) => "My" Bar = 132s = 115s + 17s (fixed + random). (132s = 180s - 48s)

6- CM Version: "Version is listed on the bottom bar on the bottom left in yellow (default color) (if you have it enabled). There is also a tooltip that shows the version loaded when you first load the script."

=> Ah OK, indeed, as it was the same Version like CC with just a Number and no Name, I thought it was CC's Version... (You would still have some space to add "CM" in front to avoid any confusion...) => Now running CM v1.0466.1 (on CC v1.0466).

7- Performance: "Edit: FF (unsure about PM) is known to not have the best Javascript engine even though I dev on it. I made sure there was no memory leaks with Chrome though. Yes performance can be slow with slower computers, but a few things to speed up is the minimize CM stats you have no interest in or change the stats update interval in settings."

=> Yep, I know, and I don't use FF indeed because of Memory Leak but Pale Moon (as I mentioned in my first Post) which is a Forked Browser based on FF, but optimized for Performance and without Memory Leaks. I can have 100+ Tabs loaded in 3 or 4 Browser Instances for weeks (and no Memory Leak), and 2 or 3 iMacros Scripts running + the JS Script from my Friend on CC, as soon as I load your Script on CC, cps on CC go down by 40%. ("cps" = Clicks Per Second)

A few more things, hope it's not too much for you, you may want to split all those Items in separate Issues, otherwise you'll never have the Pleasure to close an Issue with me...!

8- Time Calculations for Buildings: For the 'Warning' and 'Caution' Time Calculations for buying a Building, 30s = 20s real seconds, both in normal and Frenzy Modes. Same thing for 'Time left' for the 'Bonus Income' and 'BCI' Section.

9- Time Calculation before reaching all the green 'Cookie Required' Values is jumping like crazy with 5s = 1s real time, especially when in Frenzy x7 Mode.

10- The 'Warning' and 'Caution' Boxes should not be even displayed when there are not enough Cookies in the Bank to even be able to buy that Building...

11- Mini EnhReq for '"Lucky!" Reward (CUR) : 482.619 Quint' and '"Chain" Reward (CUR) : 777.777 Quint': You currently only display the one Current Value corresponding to the Normal or Frenzy Mode, and the Value will switch automatically between Normal and Frenzy Value for both Fields (CUR Lucky and CUR Chain. (Oh...!, and maybe for CUR Chain Wrath as well, but I never see this Mode, only for a short time after a Reset to catch the Halloween Cookies...)). More interesting would be to always have both Values (Normal + Frenzy) and that the correct Value which corresponds to the Current Mode (Normal or Frenzy) gets Bold and highlighted in Yellow or Orange or Light Blue... (Choose your Colour!!)

12- And I'll finish with a Compliment, you've already implement in the last or one of the last Versions of CM (but I had not noticed) stg I was asking my Friend to implement, which is the Value we would get by selling one or all Buildings of a sort... Good! One more thing I've asked him is the Value of a next_n Building (Price x 1.15 x 1.15 x 1.15 etc...). Let's say you have 300 Cursors, you know the Price for the next one, but you'd like to know the Price for the 400th...

OK, greetings, Friends are waiting for me... Thanks again for your nice Add-on...

Wow that's a lot you wrote again. Going over the parts:

1- 'Kill me!' Button: This should be pretty easy to do as it is mostly just stopping the loop, but it can be more complex if you want to automatically remove all the UI also.

2- "I would like to know how is the cookies required calculation is wrong." Orteil calculates the amount you get in real time, so the fact you see it as what it was a while ago makes me start to think any third party JS besides vanilla CC may be interfering. I'll go more about this below.

4- "I would be interested in the flaws in my code. That be nice to know as I don't think I'm the best coder in the world or anything, lol. So yes I wouldn't mind talking to your friend." Yea I knew that while loop was pretty bad, so I implemented a semi recursive solution later. It went to recursion when someone else found a different flaw in the beta. Anything else to note I would love to know.

5- Time Calculations for Next Golden Cookie and Reindeer: This is where again I think an extra JS is conflicting with CM. I take the numbers CC already calculate as the bar so it definitely includes the upgrades unless of course CC has a bug where it didn't include the upgrades (which I've not seen). Basically the bar is reading off of the game itself, so it shouldn't be wrong at all.

7- Performance: The biggest hit is the copy of the data, which I do to make sure I don't screw up the game when a new version comes out. A new copy is made every time the CPS changes and with Century Egg, it changes every 10 seconds. I've not figured out a way to make it faster. If you or your friend has any ideas, I would like to hear it.

8- Time Calculations for Buildings: 9- Time Calculation before reaching all the green 'Cookie Required' Values is jumping like crazy with 5s = 1s real time, especially when in Frenzy x7 Mode. This is again where I think a third party JS is conflicting with CM. It doesn't show up here at all. Does it still happen when you are only running CC and CM on a new start of PM? These are very glaring bugs which I would think someone else would have seen by now.

11- Mini EnhReq for '"Lucky!" Reward (CUR) : Can you please put this request in another issue?

12- Not sure is this a request or not. Sounds like a calculator for any x building, which I have no idea how to fit into the UI. If it is a request, can you put it in another issue?

1- 'Kill me!' Button: This should be pretty easy to do as it is mostly just stopping the loop, but it can be more complex if you want to automatically remove all the UI also.

That sounds more like a 'pause' button. Might be enough for chivracq. But reloading it after you press this button will probably not work.

5- Time Calculations for Next Golden Cookie and Reindeer: [...snip...]

About the golden cookie timer and reindeer timers, the purple and orange bars are the absolute limits, but it's a bell-like curve. For example with the golden cookie with the standard lucky bonuses the 5th percentile is at 114 seconds (from the start); 25th percentile is at 125 seconds, 50th percentile (average) is at 131.5 seconds, 75th percentile is at 137.5 seconds and 95th percentile is at 145 seconds (from the start).

From the end those are resp. 111, 100, 93.5, 87.5 and 80 seconds.

The way the calculation works, the bell curve is depending on the actual frames per second (by default 30).

I can create calculations for all the other timers too. Would be nice if the bars somehow show this. Unfortunately it does not scale linearly.

That sounds more like a 'pause' button. Might be enough for chivracq. But reloading it after you press this button will probably not work.

I was more like thinking pause and resume so reloading won't be necessary.

" That sounds more like a 'pause' button. Might be enough for chivracq. But reloading it after you press this button will probably not work.

I was more like thinking pause and resume so reloading won't be necessary."

Quick Answer on this one, after coming back from my 'Beaujolais Nouveau' Evening, sorry, I'm French, BJ is sacred every year... But yep, 'Pause' why not, if it releases the 40% JS Engine Sucking..., I don't mind, even if for me launching CM is just 1 Click on my Bookmarklet...

@svschouw...: 5- Time Calculations for Next Golden Cookie and Reindeer: [...snip...]

About the golden cookie timer and reindeer timers, the purple and orange bars are the absolute limits, but it's a bell-like curve. For example with the golden cookie with the standard lucky bonuses the 5th percentile is at 114 seconds (from the start); 25th percentile is at 125 seconds, 50th percentile (average) is at 131.5 seconds, 75th percentile is at 137.5 seconds and 95th percentile is at 145 seconds (from the start).

From the end those are resp. 111, 100, 93.5, 87.5 and 80 seconds.

The way the calculation works, the bell curve is depending on the actual frames per second (by default 30).

I can create calculations for all the other timers too. Would be nice if the bars somehow show this. Unfortunately it does not scale linearly. => I didn't completely understand your Answer, not because of the BJ, but because I didn't recognize any of my (empiric) Stop-Values...

Shit, and one more stupid Question, how do you Guys quote sbd else on this Forum...? Grrr.!! EDIT: "who do you..." = "how do you..."

"8- Time Calculations for Buildings: 9- Time Calculation before reaching all the green 'Cookie Required' Values is jumping like crazy with 5s = 1s real time, especially when in Frenzy x7 Mode. This is again where I think a third party JS is conflicting with CM. It doesn't show up here at all. Does it still happen when you are only running CC and CM on a new start of PM? These are very glaring bugs which I would think someone else would have seen by now."

=> Nope, because your part "... cookies left to amortize..." is correct, "your" seconds are real seconds... I will check by stopping this other Add-on from my Friend (and mine!) and monitoring the Scene for a bit, but I don't expect any change...

Ok, my calculations were a bit off; the formula was adjusted since I last calculated it (few months ago). Updated list (Golden goose egg + all lucky upgrades):

5%	25%	50%	75%	95%
114	104	98	92	86

(times are in seconds left on the timer).

Note that 5% means: there is a 5% chance that the golden cookie will appear faster than this, and 95% means that there is a 95% chance that the golden cookie will appear faster than this.

8- Time Calculations for Buildings: 9- Time Calculation before reaching all the green 'Cookie Required' Values is jumping like crazy with 5s = 1s real time, especially when in Frenzy x7 Mode. This is again where I think a third party JS is conflicting with CM. It doesn't show up here at all. Does it still happen when you are only running CC and CM on a new start of PM? These are very glaring bugs which I would think someone else would have seen by now."

I also notice no "jumping like crazy" behavior. The countdown is perfectly smooth here.

Shit, and one more stupid Question, who do you Guys quote sbd else on this Forum...? Grrr.!!

Above the comment box is a link "Markdown supported". Clicking on it shows a help page on how to do certain formatting. Quoting for example is done by putting a "> " in front of the line.

Thanks 'svschouw' for the Quote Functionality, I've been able to edit my previous Posts to make them more readable...

8- 9- Time Calculations for Buildings and Green 'Cookies Required', I managed to do some Testing with solely CC and CM loaded in 1 Tab in 1 Browser Instance (without my 150 other Tabs loaded...) and indeed, the Time Calculation is then correct, and as soon as I load my Auto-Clicker JS Script from my Friend and/or my iMacros Script, about 4s = 1s real time. I guess it's because you must be using the 'Cookies per second' Value from Orteil from:

Normal Mode: Cookies per second : 769.007 Quadr (multiplier : 881.107 M%) Cookies per click : 65.134 Quadr Cookie clicks : 1.594 M

Frenzy Mode: Cookies per second : 5.382 Quint (multiplier : 6.167 B%) Cookies per click : 455.937 Quadr Cookie clicks : 1.596 M

It was funny btw for a while to click again manually on the Golden Cookies and the Reindeers, I had forgotten about this kind of fun...! LOL...! But I normally constantly "click" at 30-70cps, make it 50cps Average, 60Qd Cpc x 50 = 3Qt Cps + 769Qd => about 3.5Qt Cps = more than 4 times 769Qd Cps. (C=Cookie / c=Click / s=Second) But again, at all times, the Time Calculation for "... cookies left to amortize..." is correct. You must be using a different Method for that one, independent from the 'Cookies per second' Value from Orteil... (If I'm correct with my Assumption, of course...) But don't worry, I just mentioned it FYI, I don't really care, it actually feels like being a "Super Hero" with 4s=1s real time...!

It would actually be interesting to have a real Value for Cps based on the real Amount of Cookies in the Bank, per Second and an Average based on the last 10 and 60 seconds maybe, including the original Cps from CC + all the cps, that would be interesting for People using Auto-Clickers like me, especially with (Cpc x cps) = Cps x 4, we only have the Cps Value, but the (Cpc x cps) Value is 4 times more important (for me)... (I asked my Friend to implement that, but he didn't understand the Use, maybe I explained it better here...)

5- Time Calculations for Next Golden Cookie and Reindeer:

Next Golden Cookie: Your Bar = 215s = 72s + 143s (gray-fixed + pink-random). => I always have between 85s and 114s left (from your 215s). => "My" Bar = 130s = 101s + 29s (fixed + random). (130s = 215s - 85s)

Next Reindeer: Your Bar = 180s = 89 + 91 (gray-fixed + orange-random). => I currently always have between 48s and 65s left (from your 180s). (Hum, and I'd even seen better before my last Reset, but I still miss 4 Eggs, then it was always between 65s and 85s left...) => "My" Bar = 132s = 115s + 17s (fixed + random). (132s = 180s - 48s)

Ok, my calculations were a bit off; the formula was adjusted since I last calculated it (few months ago). Updated list (Golden goose egg + all lucky upgrades): 5% 25% 50% 75% 95% 114 104 98 92 86 (times are in seconds left on the timer).

This is where again I think an extra JS is conflicting with CM. I take the numbers CC already calculate as the bar so it definitely includes the upgrades unless of course CC has a bug where it didn't include the upgrades (which I've not seen). Basically the bar is reading off of the game itself, so it shouldn't be wrong at all.

OK, looks like 'svshouw' agrees with me, we both find the same Values (for Golden Cookies) for the 2 Extremes (114s and 85s) left on the Timer... (The Timer for all Frenzy, Chain and Clot Modes is always correct...)

7- Performance:

The biggest hit is the copy of the data, which I do to make sure I don't screw up the game when a new version comes out. A new copy is made every time the CPS changes and with Century Egg, it changes every 10 seconds. I've not figured out a way to make it faster. If you or your friend has any ideas, I would like to hear it.

Still haven't spoken to him, he's the JS Guru (between us two)... He went for absolute Performance with his Add-on and we have a long History of Performance Competition (from some other Game) between his Scripts and mine, he might have some Golden ideas...

But now that you mention it, I do indeed notice a big Peak every 10s, with my cps going from about 50cps to 10-15cps for about 1-2s... (above the 40% average damage...)

11- Mini EnhReq for '"Lucky!" Reward (CUR) :

Can you please put this request in another issue?

OK, will do...

12- Price Next_n Building:

Not sure is this a request or not. Sounds like a calculator for any x building, which I have no idea how to fit into the UI. If it is a request, can you put it in another issue?

OK... Place to display it would be on the Popup for 'Buy 10' where Orteil already displays the Full Amount for the 10 Buildings, you could add the Price for the 10th Building only, the 20th, the 50th, the n_th until the next 100/200/300/400 Buildings owned and the 100th...

Ok, my calculations were a bit off; the formula was adjusted since I last calculated it (few months ago). Updated list (Golden goose egg + all lucky upgrades): 5% 25% 50% 75% 95% 114 104 98 92 86 (times are in seconds left on the timer).

OK, looks like 'svshouw' agrees with me, we both find the same Values (for Golden Cookies) for the 2 Extremes (114s and 85s) left on the Timer... (The Timer for all Frenzy, Chain and Clot Modes is always correct...)

Well, I agree only partially. Yes, usually the timer is between 86 and 114, but only 90% of the time. 8% of the time the timer will be either between between 81 and 86 or between 114 and 120. And if you go even more extreme: 1.8% of the time, the timer will be between 77 and 81 or between 120 and 127. That's the the thing about chance. The only real limits are 143 and 0, which is the purple bar (although a value lower than 73 has a less than 0.01% chance). It would be nice if there were some visual cues about this distribution, but that might be annoying to implement.

But again, at all times, the Time Calculation for "... cookies left to amortize..." is correct. You must be using a different Method for that one, independent from the 'Cookies per second' Value from Orteil... (If I'm correct with my Assumption, of course...)

Amortize is calculated from what the building actually made, aka cookies from golden cookie lucky or manually clicking has no affect on it (Orteil's code, not mine). All I do is read the stats store in the game and calculate time left.

It would actually be interesting to have a real Value for Cps based on the real Amount of Cookies in the Bank, per Second and an Average based on the last 10 and 60 seconds maybe, including the original Cps from CC + all the cps, that would be interesting for People using Auto-Clickers like me, especially with (Cpc x cps) = Cps x 4, we only have the Cps Value, but the (Cpc x cps) Value is 4 times more important (for me)... (I asked my Friend to implement that, but he didn't understand the Use, maybe I explained it better here...)

See Issue #34 (basically I was planning on doing something like that)

Place to display it would be on the Popup for 'Buy 10' where Orteil already displays the Full Amount for the 10 Buildings, you could add the Price for the 10th Building only, the 20th, the 50th, the n_th until the next 100/200/300/400 Buildings owned and the 100th...

I actually put that information on how much buy 10 cost, not Orteil. But that popup is for buy 10, why would I show how much it cost for the rest?

Well, I agree only partially. Yes, usually the timer is between 86 and 114, but only 90% of the time. 8% of the time the timer will be either between between 81 and 86 or between 114 and 120. And if you go even more extreme: 1.8% of the time, the timer will be between 77 and 81 or between 120 and 127. That's the the thing about chance. The only real limits are 143 and 0, which is the purple bar (although a value lower than 73 has a less than 0.01% chance). It would be nice if there were some visual cues about this distribution, but that might be annoying to implement.

Hmm, I could make it lighter-darker-lighter color bar to show it...

I think if there are actionable pieces in here they should be split into their own suggestions, or this whole thing should be closed since this is quite old and quite verbose.

I think if there are actionable pieces in here they should be split into their own suggestions, or this whole thing should be closed since this is quite old and quite verbose. Euh..., yep you're right, and that was actually my "Intention" indeed as well, hum..., 3 years ago already...!?, but I never took the time/courage to open the separate Threads...

Original Thread was about the "'Kill me' Button" (or 'Pause'), that I still miss (sometimes, ah-ah...!), while running now (Septb 2017) CC v2.0042 + running the corresponding Cookie Monster Version from your Server directly. (+ Pale Moon v26.3.3-x32 (=FF47), Win10-x64, + iMacros v8.82 for FF + Self-made Autoclicker in JS => 100-140 Clicks per Second.)

(With 18,000 Buildings (1350 Cursors - 1088 Chancemakers), 2 10^40 Tredec Cookies (=2 10^82 Cookies) in Bank, 1.3048378574739092e+32 Tredec (=1.3,048,378,574,739,092e+74) per Second.) Legacy started : 1160 days, 3 hours, 44 minutes, 6 seconds ago, with 23 ascensions Run started : 159 days, 0 hours, 57 minutes, 25 seconds ago (Running 24/7) Buildings owned : 18,000

I would say, if you want to keep this current Thread open, only focus on the 'Kill me' Functionality if it will be implemented one day, all other Items could/should become separate Threads, but I've been living already 3 years without the 'Kill me' Button, so I'm not dieing for it, ah-ah...!, and I can understand if you simply want to close the Thread, no problem...

And I still love Cookie Monster, ah-ah...!

CookieMonsterTeam / CookieMonster

Add a "stop mod" and "restart mod" button #32