First off apologies. that came off a lot harsher than it needed to.
and yeah rather than screaming it would probably be way more productive to go over what my layout looks like and either figure out if you can simply have a similar layout option or allow enough customization for me to get back to where i am.
first off i completely removed the header. page content starts at the very top of the page. all menu related everything is on the sides. I play a lot on my phone in landscape mode. the header takes up half the screen. I'm not after a fancy banner, im after the game.
secondly I did a lot of css wizardry manipulating the dashboard notepad and spoilers to have buttons that open image menues for pages i go to all the time.
i enlarged the buttons for taking your turn, go to battle quests, refight challenger, and a few others relating to battling so theyre easier to click and i moved them all so theyre all in the exact same spot. doing my daily battle quests literally is me clicking on the exact same spot over and over with no actual changes. super convenient. i worked very hard to get the css to do that, to have my weapon queue strong enough to do that and my battle pet strong enough to do that. id prefer my hard work for the sake of future convenience to not be in vain.
i css display:none a lot of images that just make pages a lot larger than they need to be, again im a minimalist.
this one you'll probably consider cheatie but i replaced all the 3x3 sliding puzzle images to always be the dinosaur one, easy to tell at a glance which piece is which as its a circle. a lot of the art chosen is confusing, sliding puzzles are annoying enough as it is imo without needing to decypher the art.
possible options: -have a similar landscape mobile friendly layout
-allow removal of most of the layout elements you have and allow a method of adding custom menus (dashboard notepad + CSS is how i do this presently, would be cleaner if the spoiler tags allowed for identifying names/ids for the elements.)
-allow limited css that modified page content for things like my battle and sliding puzzle modifications, your altarations of the layout shouldnt affect individual pages much unless ur 100% revamping everything.
-I'd also recommend making it so custom CSS isnt applied to the page for adding custom CSS so if you accidentally remove the text area or somesuch it wont actually remove the ability to fix it. also stress use CSS as your own risk.
I'm just hoping I can get the game looking similar after this goes down to how I have it now. I'm ok with needing to put in my own legwork, possibly throwing some CSC to unlock customization or something, and needing to wait for approval which hopefully wont be a hassle. Just was upsetting to read all the work ive done customizing my experience may be all for naught and needless to say i was upset.
is there a way i could send you my css (or if admin godmode lets u look at it just do that) and/or images to illustrate what ive done?

Thanks. I recommend reading through the reply to in my last staff post on this thread, as it explains the best working compromise I've come up with so far, as well as some of the new constraints we have to work within for v2. I'd love to hear your ideas and feedback on that. :)
Regarding the "cheatie" game modifications: if you're aware that something could be seen as cheating by staff, either don't do it, or file a ticket for a rule clarification to find out if you can safely do it or not. I'll need to clarify with the UA department where the line is for that, but it goes without saying that we won't go out of our way to accommodate rule-breaking CSS.
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
Hey, I finally actually inspected the HTML a bit, and I noticed something about our UI components (provided by Chakra UI) that is really good news for us. Chakra components have deterministic classes specifically to allow for this kind of customization! For instance, buttons have [tt].chakra-button[/tt] class name, and the entire webpage has [tt].chakra-ui-light[/tt] or [tt].chakra-ui-dark[/tt] so you can even have separate styles for day/night mode with ease.
I asked them and confirmed that these class names can be relied upon even in future versions of Chakra. (They also confirmed there is no official documentation listing these for now, but they would consider adding some in the future.) This is great news because it gives you access to customize a lot of our UI building blocks without us having to manually label those.
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
That's really good to hear about Chakra UI! I noticed some like the chakra-image one as I was trying to see if I could force a white background on my custom pets with transparent images in the (wip) pets page - for consistency on dark mode aha. But that is super useful and looking at the ones I've spotted now, even without documentation they're fairly easy to find/understand.
The brainstorm/steps from your last response are sounding like a really good base imo. Allowing users to request custom selectors means you'd also always be in the loop about what users what to customise (and hopefully also why!) which is honestly a uniquely invaluable trait and I would go wild for that level of feedback on my own projects.
On a separate yet related note, as a lot of the custom CSS people are noting is related to accessibility - I absolutely approve of the move to React for V2. A little bit of backstory - I work in the public sector in the UK so it's a legal requirement for any web/mobile apps I develop to meet WCAG 2.1 AA standard (as opposed to private sector which has a requirement to make 'reasonable adjustments' but no particular standard to meet). You already mentioned, but React has some great stuff built in to help with this! And again, it's fantastic to see Subeta in a more mobile friendly form.
Indeed! Part of our decision to use Chakra for UI components is that all of their components meet WCAG by default. We are trying to pay attention to this in our own design decisions as well moving forward. For instance, the colors chosen for night mode and day mode should meet WCAG color contrast guidelines (though it's possible I missed a few places - I intend to go back and polish everything ofc!)
It's a really awesome thing we get with v2, that is so important. It's impossible to make our current website accessible at this point - 16 years with thousands of files. I've always felt a little bad about that, but now we've got an opportunity to make this right.
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
Last i had a staff member comment the consensus was as long as im still manually doing the puzzle they dont care. Ive just changed the art for clarity.
As for the idea of browser based css changes i think you'd need to amend the rules. Pretty sure as theyre written now that falls under "Do not use external software to gain an advantage over other users." Which is why thus far ive always strictly stuck to custom css as its in no way external.
I dont mind a rule change id just make sure theres a discussion both internally and with the community. Id look forward to making a subeta script if it was allowed. Perhaps even allow user made scripts to earn a staff member stamp of approval as not rule breaking and allowed to be shared on the forums.

I've just gone through and added some new CustomCSS based on what other users are using. What I've decided to add are:
(PS thanks u da real one)