Oh god, please fix the battling one, I'm stuck in a Willowisp cycle SEND HELP

Also, there's no battle text displaying. It's making battling quite ... interesting.

Finishing a BQ on database server gives me

instead of completing the quest. Also, that should have been win 11, not win 1.

Doing the BQ on subeta.net does finish the quest without adding wins to my count.

I don't think they've been fully reset, as I tried against Prodigy and was given the proper difficulty for win ... 21? 25? I don't recall where I left off on him. I believe it is only "resetting" the wins on the database server for BQs, which I assume are handled differently than a normal battle because the challenger is always at base stats.

Got a blank white page when moving an item to my vault on the DB site, but not the regular site. The item did make it to my vault though, so it wasn't lost:

https://database.subeta.net/item.php?act=movetovault&itemid=3017965689

I don't think the edit on my post saved. :(

Battle text is missing again.

Also, I would not be against you resetting battle counts, entirely. Just saying. 👼

Last I saw, battle text was also missing on the main site, not just the DB site.

Database error - send this to Keith: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ') AND itemid='1815' GROUP BY shopid' at line 1 (SQL: SELECT shopid, SUM(amount) AS total FROM ushop_stock WHERE shopid IN () AND itemid='1815' GROUP BY shopid)

When doing account search on an item

While account searching for a Siren Stein

Shop Search Database error - send this to Keith: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ') AND itemid='147944' GROUP BY shopid' at line 1 (SQL: SELECT shopid, SUM(amount) AS total FROM ushop_stock WHERE shopid IN () AND itemid='147944' GROUP BY shopid)

Chrome OS and Browser.

Baking with Fantine I can confirm is now fixed. It accepts appropriate items and the completed baked item is recieved and it is not forced off of the database.version url of subeta.

Buying items in the Carnival Prize shop is now fixed and stays on database.subeta urls.

Ordering a pet treasure https://database.subeta.net/pet_treasure.php?petid=5876504 Blank white page except for 5023716 - 1 and the header and sidebar. Tabs and the footer have disappeared.

Okay, so, interestingly, the BQs that are done and counting as "wins" ([number] win + relevant loot) on the database server are actually showing up as losses.

If you look at Ennui's stats for Prodigy, it shows as 25 wins, 0 ties,11 losses and 11 losses. Before I tried to do Prodigy as a BQ on the database server, I looked at my stats and they had previously been 25 wins, 0 ties, 7 losses. You can see my wins / losses here. It also shows 1 loss on Blood Bat, 1 loss on Jeremy, and 1 loss on Technicant.

Googlechrome browser Trying to get into wardrobe to remove items on http://database.subeta.net/wardrobe_items.php Application error An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details. You can do this from the Heroku CLI with the command

white page trying to move item into vault.

white page trying to open old gallery.

Got this while searching my account for fallen verdant leaf: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ') AND itemid='131265' GROUP BY shopid' at line 1 (SQL: SELECT shopid, SUM(amount) AS total FROM ushop_stock WHERE shopid IN () AND itemid='131265' GROUP BY shopid)

The battle text issues are only on subeta.net. But the other battling issues (BQ wins counting as losses) are only on the database server.

When searching user shops for an item, many shops just don't show up in the database version, leading to things like The Database version being empty vs The base site version having plenty for sale