Right now, there is no way to just buy buildings. Adding a button to the menu and a check for the state of the button allows users to personalize their experience

Is your feature request related to a problem? Please describe.
Notifications are annoying
Describe the solution you'd like
Turn them off

Since they require confirmation AND can change the game, they should be excluded. This will cause a rewrite of how upgrades are

• selected and determined
• bought (since we always buy the element with the id upgrade0

Is your feature request related to a problem? Please describe.
When the autobuyer is on, it's rather hard to upgrade Santa or the dragon with cookies

Describe the solution you'd like
Allow the autobuyer to keep santa in the autobuy circulation and also the stages of the dragon you can pay with cookies fo

This issue is only to provide a checklist to the milestone

• switch to HTML Templating #21
• Cache Scroll Position in Buying Timeline #20
• Calculate Prices with discounts #24
• Fix timeline sorting #26
• adjust name text size dynamically #27
• Change Slider #29
• switch document.getElementById() to cookie clicker build in l('ID')
• If all buying is turned off, remove the next buy container
• look for other cookie clicker functions (like binding click event listeners) and implement them (unnecessary)
• consider moving some functions out of mod context scope into global scope for easier access (unnecessary)
• use Game.Version on Image strings, so these dynamically scale with the game

The way it is done right now, is incredibly complicated, maybe the HTML can be generated differently?

HTML has templates, or rather allows templating. If I include basic "skeleton" html files in the mod folder and load them in with an XMLHttpRequest, the code looks cleaner and I can catch HTML syntax errors while programming. However doing this would either be async and could cause content to load in too late or sync and could cause the game to freeze while it loads heavy content

Show in a box (near the store somewhere) what item will be bought next. Will for sure look better than what I've done now

Styling idea

Describe the bug
Changing the slider will only show the new value after mouse up

To Reproduce
Steps to reproduce the behavior:

1. Go to Options
2. Use slider

Expected behavior
Show current value on slide

Game Version:

• all

Additional context
Use the oninput Event

Is your feature request related to a problem? Please describe.
Cookie Clicker renders (for whatever reason) the Menu every draw tick. This means if you scroll down in the Timeline container, you'll quickly be reset back to the top

Describe the solution you'd like
Save Scroll Position until user closes menu (maybe even for the whole session) and render the scrollbar to that position

Additional context
Would require finding out how to set and read scrollbar position

Is your feature request related to a problem? Please describe.
Autobuyer miscalculates quite a lot when discounts are applied. Discounts have to be included

Describe the solution you'd like
Factor in Discounts

Describe the bug
The buying timeline appends new elements to the end of itself

To Reproduce
Steps to reproduce the behavior:

1. Let the autobuyer buy something
2. Look into timeline
3. Its at the end

Expected behavior
Object appearing at the front

Game Version:

• all

The way cookie clicker is programmed it (for whatever reason) redraws the menu every draw tick. This makes typing in values in the input box incredibly hard.

Either change to a slider (could be pretty bad UX) or save the last typed thing as a temporary variable until the set bulk amount is clicked or the menu is disabled (gross)

Keep track of what has been bought and show it in a scrollable container in the options menu. This can be done by keeping an array of objects or simply an object of objects

This will likely need a rewrite of how variables as stored, as we need a JSON Object next to the bulkAmount variable, but we can only store one thing in between sessions

The Bulk Buyer will request the price for 0 buildings when the value is set to 0. This will lead to buildings always being the cheapest because 0 buildings cost 0 cookies. Implementing this skip, allows the user to personalize their experience so that they only auto buy upgrades

Describe the bug
Showing the buying timeline in the menu when it contains a lot of items causes the menu to slow down

To Reproduce
Steps to reproduce the behavior:

1. Let the autobuyer buy a lot of things
2. Click on menu
3. Every Draw Tick, the game stutters

Expected behavior
Obviously no stutter

Game Version:

• all

Additional context
Ideas: Append Elements async, allow clearing timeline or disabling it. Construct html element at autobuy and just simply append whole HTML sting when menu is loaded

Describe the bug
The name of the Upgrade/Product that will be bought next, clips into the image container when it gets too large

To Reproduce
Steps to reproduce the behavior:

1. Wait for autoclicker to target anything with a long name
2. Look at the name

Expected behavior
Name not clipping

Game Version:

• all

Additional context
Should just dynamically scale names

Let the user know what will be bought next so that they don't have to calculate

The idea for this is that normal elements, like buttons can be created with a function that gets passed content, an onclick function, an optional label and an optional ID

Other elements can be injected with a separate functions that takes the desired HTML code as string

Nobody will be assigned to this in hopes that the bot doesn't create a branch for this, as this can and should be done with another issue

Appending to menu, when it's not empty, causes the options to appear on options, stats and info. This is obviously not intended behavior