• 4 Posts
  • 108 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle
  • Gacha can be moderately acceptable if the math is fully documented and enforced. If you know it will take <= 180 pulls to get Raiden Shogun, and each pull costs $3, then it’s just a $540 DLC with extra steps and the tease thst it might be cheaper if you’re lucky or have banked pulls.

    But transparency is key-- the developer should be expected to offer a calculator or lookup table for any RNG item, especially if it’s some combination of multiple drop mechanics or hsrd-to-convert currencies that dissuades back-of-the-envelope estimates.

    Even in Vegas, the slot machines are required to disclose their payout rate.

    There’s also significant differences in the gacha appeal factor. If there are no leaderboards or PvP, and the game mechanics can be completed with F2P only, that is inherently less pressure to spend then on a game where you regularly get your ass handed to you by a someone with a Black Amex and all seven-star limited banner units.




  • The experience could be somewhat tamed by a lottery process.

    Accept a token deposit for a week or two, and then draw from people contending for a given seat, then give them another week to pay the balance. Any unclaimed seats are put up at will call night-of-the-show. Limit the number of deposits taken from any given card to prevent “I’ll claim 30 seats and only buy 1” gaming of the lottery.

    There’s probably some more complexity about it (if you want N seats together), but I think that would dramatically cut back on the frustration for “the tickets were only available for 14 seconds and the server was being DDOSed by scalper bots.”

    Having to put down a deposit with no guarantee of a ticket also makes “buy All The Seats” scalping theoretically impossible and economically riskier. If there’s 5/1 contention for a ticket, you’d have to find a way to get 3 lottery slots for a better than even chance of getting it. If the deposit was $10, you’re spending $30 for the chance to buy a $50 ticket-- so if you can’t resell the ticket for at least $80, you lose. Under current policies, if you can sell that $50 ticket for $51, you’re ahead.









  • They’ve got a guy at work whose job title is basically AI Evangelist. This is terrifying in that it’s a financial tech firm handling twelve figures a year of business-- the last place where people will put up with “plausible bullshit” in their products.

    I grudgingly installed the Copilot plugin, but I’m not sure what it can do for me better than a snippet library.

    I asked it to generate a test suite for a function, as a rudimentary exercise, so it was able to identify “yes, there are n return values, so write n test cases” and “You’re going to actually have to CALL the function under test”, but was unable to figure out how to build the object being fed in to trigger any of those cases; to do so would require grokking much of the code base. I didn’t need to burn half a barrel of oil for that.

    I’d be hesitant to trust it with “summarize this obtuse spec document” when half the time said documents are self-contradictory or downright wrong. Again, plausible bullshit isn’t suitable.

    Maybe the problem is that I’m too close to the specific problem. AI tooling might be better for open-ended or free-association “why not try glue on pizza” type discussions, but when you already know “send exactly 4-7-Q-unicorn emoji in this field or the transaction is converted from USD to KPW” having to coax the machine to come to that conclusion 100% of the time is harder than just doing it yourself.

    I can see the marketing and sales people love it, maybe customer service too, click one button and take one coherent “here’s why it’s broken” sentence and turn it into 500 words of flowery says-nothing prose, but I demand better from my machine overlords.

    Tell me when Stable Diffusion figures out that “Carrying battleaxe” doesn’t mean “katana randomly jutting out from forearms”, maybe at that point AI will be good enough for code.


  • I suppose the weird surprise lesson of the Windows 8 fiasco is no matter how badly they bollixed it up, they wouldn’t lose enough customers that they could afford break a lot more of the user experience than they ever originally thought.

    Even Vista, while people had issues*, still provided a largely familiar interface and didn’t go out of its way to break muscle memory and traditional workflows.

    IMO, Vista wasn’t as bad as is commonly held. A lot of the problem was that it was more resource-intensive than previous systems-- it really asked for decent graphics cards and 2Gb memory, but they sold a lot of cheap machines with 512Mb and crappy shared-memory chipsets that only qualified as “Vista Basic Capable” so that the manufacturers wouldn’t have to formally declare them obsolete. Some drivers had teething trouble, but switching to 64 bit was going to have growing pains anyway.