I'm glad you asked! Strawberi uses ::before pseudo-elements in fixed positions to create the illusion of a magic button that does whatever you want it to do. ::before is a little bit special; you don't need HTML access to "create" a ::before element on the screen, which is one of the reasons that it's a pseudo-element and not a proper element. So, by assigning these ::before elements to buttons or links that disappear after you click them, you can create a priority system for tasks on the screen. Here's an example: For the Party Module, Strawberi's CSS selectors check for the Next button (.mu_navlink.next) and all of the different buttons for feeding Pokémon on the site (.berrybuttons[data-berry], .action button, .action>a). For each of these, it assigns a ::before pseudo-element with a content value of "🍓", activating the invisible stack of buttons at the bottom of the screen whenever something in those categories is clickable. Then, when the user clicks that button, the action buttons next to the Pokémon disappear, and the user can then press the button after that, and so on and so on until they finally click the Next button and go to the next user. Modules can be very complicated (like the Fishing Module) or very simple (like the Daycare Module, which is literally just one line), but they all do effectively the same thing: Activate one of the invisible ::before elements by giving it a content value so that you can click on it and do something convenient. I hope that this is clear from the explanation, but Strawberi doesn't do anything "automatically." You have to personally press the button once for each action you want to do. This is so that I don't violate Pokéfarm's Terms of Service, of course, but CSS is also limited enough that it kind of can't do anything on its own. That's why I used CSS to create Strawberi: There was absolutely no chance that I would accidentally create an autoclicker or anything else that would violate TOS.

If you go to the Nearby Places page of your Farm, Strawberi has Modules for the first nine areas on that list (so, the Lab, the Fields, the Shelter, the Daycare, the Garden, the Scour Area, the Wishforge, the Fishing Hut, and the Trade Center). On top of that, there are smaller Modules for other things. The Boxes Module helps with opening Treasure Boxes, the Notification Module helps with clicking on notification links, the Dialog Module helps close pop-up dialog boxes (confirmation windows), the Daycare Module helps with adopting Eggs, the Evolve Module helps with the QOL Script's easy evolution function, and the Training Module helps collect all of your Training Bags. Strawberi's buttons usually mean "Yes." Would you like to open a box? Yes. Would you like to throw this Pokéball? Yes. If you want to say No (like refusing a gift), or do something with a little bit more finesse (like planting many different berries), you'll have to do those actions yourself. If the thought of unintentionally saying Yes to something makes you feel a little queasy, you can disable the nausea-inducing Module whenever you like by removing the clearly labeled CSS from the code. I've done my best to make sure that you can't do anything really dangerous, like mass-release Pokémon, so if you run into something that players really shouldn't be spamming Yes about you should send in a bug report right away.

(This section may be updated in the future.) Q: Can Strawberi be used with Google Chrome? (Or Edge, or Opera, or any other Chromium browser?) A: Yes. However, you may run into visual glitches, especially with the Site Skins. If a visual glitch is preventing you from using the site normally, please create an issue on the Github's issue tracker. Thank you! Q: How does this Field Module compare to Winterbraid's One Button Fields? A: It's a different implementation.

• OBF is developed for Chrome;
• Strawberi is developed for Firefox.
• OBF is lightweight and standalone;
• Strawberi covers most of the site.
• OBF uses precise CSS selectors;
• Strawberi is designed to be scalable.
• OBF can be toggled with the QOL script;
• Strawberi cannot.

Use whichever you like. Q: Are you worried about releasing this during the PFQ Recode? A: Not really. If the HTML changes, Strawberi will be updated accordingly.

Wow, thank you for this! Currently testing it with your provided skins :) (by the way, it's nice! Lots of little extra styling I hadn't thought of!) One thing from Winterbraid's OBF I miss though is being able to turn the button off when browsing public fields; sometimes I browse to buy, not to click, and currently Strawberri is in the way, it hides about the whole last row...

I'd like to double the height of the strawberry button . can you walk me thru that?

This looks incredibly convinent! However...is there a way to just plug in the strawberry part and not the colors of the site skin?? Either one hurts my eyes lol ( I have my skin had dark mode, like black, cuz my eyes r sensitive after staring too long lol)

I have another question! in the shelter module, are we able to program it to utilize either flute instead of refreshing? sometimes I prefer just eggs, sometimes just 'mons, but never just reload if it were possible to program in just one or the other, it would make life so much easier!

This could be possible, with the new button architecture. I'll make an issue for it in the tracker. Edit: I forgot to say, there's also an option to pick just one of the white flute or black flute to be the reload button instead. It's under the Shelter Module. I'm talking about having multiple reload buttons on the screen at the same time.