I’m upset because some users have insisted this entire time that the issue wasn’t fixed. And those users were repeatedly ignored. Now it can no longer be only certain users problems (example browser blaming, net connection excuses) because more and more people are being affected.
It’s like an infection. It wasn’t treated correctly the first time and now more parts are affected. Subeta used to stand out because unlike other sites, staff was responsive and open to criticism and new ideas. Now it feels like only a few staff members even give a shit about the site and it’s a hollow empty shell of its former self.
This theft of our csc is insulting. Any self respecting site that knows there is a monetary issue would be quick to solve the problem. IF YOU LACK THE ABILITY TO FIX IT THEN SAY SO!!!
It’s a lot more respectable to say “hey we don’t have a programmer who can handle this atm. Be careful when selling your cws”
But nooooo. It seems to be a better choice to refuse to acknowledge the bleeding and sweep it under the rug. 🤷🏻♀️
thank you for being one of the few who cares.
Just to add additional information:
This problem has been ongoing for at least the past two years, as my first ticket about this issue was from October 2021.
The problem occurs when a user or users purchase CWs in quick succession. When you look at your events page, the timestamps for your sidebar events will be identical or nearly identical, though I've heard from other users that it can be up to a two minute time difference. For example, a user purchases CW A at 13:04:02 and CW B at 13:04:02. Then CW C is purchased at 13:04:04 and CW D is purchased at 13:04:07. You will receive the profit for CW A, but not B, C, or D.
It does not matter if the items are unlocked in your CW shop or purchased via invitation.
I love the idea of a log for all CSC sales and purchases in one place. That would truly be helpful to have. It would need to contain purchases from users sP shops too where we purchase second-hand CWs.
An additional idea is to add a timer to CW purchases like we have for other shops. For example, a five or ten second delay between purchases would likely solve the problem. Adding a little pop-up that says "You have to wait 10 seconds to make another purchase" would go a long way and shouldn't be that hard to implement since we have it in other places on the site.
That information is super helpful
And to add on to what you say - I kinda wish the CW shops would run like user shops where the CSC just goes into the till and we take it out. That would help people track it a lot better if it showed purchase log + till log for us. It would be so much easier to go "hey, there are 10 purchases which should've had X profit but I'm only seeing Y profit".
I know everyone is stretched thin, but hopefully something can be done sooner rather than later, especially with sales coming up.
And I am thankful to Jessi for reporting it and continuing to poke at staff on our behalf.
Mayla, thank you so much for that info.
I love the idea of a shop till as well! All the csc profits go into one till, that you can take out however and whenever you want.
I had not heard of this glitch until recently, so I have absolutely no idea if/how much csc I've lost over time. At this point I guess I'll never know either, but it does make the upcoming black friday cw sale sound a lot more concerning :/
PS thank you for attempting to poke Keith about this! We appreciate you <3
2 year old issue? Yikes, I wouldn't even know if I was affected... oof.
I will say that I wasn't aware of this issue and thus, I never really keep track of my on hand CSC. I have no way of knowing if I've been shorted (and since I do a lot of holiday events where CWs are purchased rapid-fire, I probably have...)
Personally, I think this warrants a news post just to make others aware of the issue. It's understandable if no staff resources can be put to figuring out the problem or coding a related fix like a delay or a shop till (which, by the way, I LOVEEEEEEEE the idea of!), but people should at least know that they need to keep an eye on their CSC amount so they can file a ticket if need be for missing CSC.
Hello everyone! I'm really sorry about ignoring this topic, I thought (not anyones fault) that there was a staff response that we were still trying to get to the bottom of it.
I just pushed code that adds a 60 second timer between making CW purchases, and we'll monitor that change. I believe that this is some kind of race condition that comes from buying multiple CWs at a time, and something is stopping it from completing.
To be clear: we do track CW purchases (and could make a page for you to see all of your purchases, more on that soon!), but the code that runs when you make a CW purchase does a lot of things, and one of them is sending the event to you and logging it to our CW logs. The rest are sending the item, removing it from the shop, making sure the PW (if needed) is correct, etc, and I have been unsuccessful in finding where in that process the purchase is falling apart.
Another point - The code to put CSC into your account and send an event would be the same type of code that would put that CSC into a till and send you an event. The code we're using to log the information about the purchase would be the same code we'd use to create a user facing log where you can see all of the purchases. That isn't a solution to this issue.
This is a HUGE code image (sorry!) but it gives you an idea of how much goes on when you click the "buy" button. We have to check if you're using a voucher, we take the CSC, increase the number sold, give the item, make sure to figure out the profit correctly, send events to the releaser and the purchaser, log it to the users logs and our CW purchase logs (we log to two places!)
This is great code that I just don't have the tools to dig in to on new.subeta.net, and so it's been a game of adding logs to particular places in the code to see who gets to what spot and try to determine patterns, and so far all I've been able to determine is that it might be related to the purchase speed.

TLDR: Code has been pushed to add a 60 second timer between purchases, and we're monitoring now to see if that resolves the issue. If not, back to the drawing board!
💖 ✨ 🤗
I really like they idea of this. But let’s say two different people buy at the same time? Wouldn’t the same issue still happen? >_<
I think (I'm not 100% sure) that it shouldn't be an issue, hopefully we'll see that born out!
I'm also going to see how hard it would be to rig up a page where you can see your purchases, since we do really log them, I promise! That's why it was frustrating for the UAs dealing with this in tickets (And y'all trying to write in about it) because the place they expected to see and confirm what you were saying wasn't reflecting that reality. Here is the first entry in the log in 2020!

💖 ✨ 🤗
A log would be amazing! Thank you so much for working on this for us! I got my fingers and toes crossed the timer helps ^0^
Oh yusssss! I love the idea of having a low we can see. I sure do hope the timer works.
Thank you for posting here Keith!
Seeking, click here! Please let me know if you are selling
So the timer is for each CW item so it is not purchased sooner than every 60 seconds correct? That will be awesome if it works. :)
@@ I wasnt aware this issue was still happening so Idek if/how much profit me and yuki lost due to this bug but im glad this got a notice from Keith on what could be causing the issue! Thank you for looking into it!
After reading this thread and then reading through the code, the problem is almost certainly at the part here:
$cw->releaser->giveCSC($creator_cut, 'CW shop sale profit');
combined with your caching code perhaps or rate limiting or some other similar protective mechanism.
I think that, perhaps, if you add to that string 'CW shop sale profit' a code for the specific purchase (itemid, userid, and stringified datetimestamp would be a good start) and then within the giveCSC function itself, log that string so that you capture those values in the CSC giving code (that's the part that's not working when called too frequently in succession; the other parts are working correctly it seems like, including the event notifications which come after the giveCSC call), you will either find it no longer happens (because the calls won't be identical and in too-quick succession), or it's easily determined by admins looking at the log that it has happened (faster ticket handling).