thatsumoguy

Hidenoumi J13E

Often. The project was mostly about combining my enjoyment of sumo and trying to use different technologies. The cache is definitely not required, the db would be fast enough by itself, given the load.

Thanks, those are gone now. Basically I moved hosting, forgetting that I use a cache for fast lookup of rikishis by the ID that the JSA provide. I forgot to transfer the cache over, and so it started reassigning the ids. I realised during day 1 and fixed it, and I thought i'd removed all the erroneous matches, but apparently not.

@OctofujiI believe I've resolved this issue and all the erroneous matches have been removed.

Oh thanks for pointing this out. I will check on it. There was a bug due to "reasons" in september, but I thought I'd caught all the issues.

SumoStakes is back once again and ready for registration. Deadline is 2pm (JST) Sunday 10th March. As soon as the first day's torikumi is release you'll be able to make your stakes. I look forward to seeing how everyone fairs this time around. P.S. As always, any issues or problems you notice, please don't hesitate to let me know.

Staking for day 1 is now open and ready for your best efforts. If you haven't registered for sumostakes yet, do so before the deadline on Sunday 2pm JST and make your stakes before 3pm JST. I know where a significant number of my points are going for Day 1 cough kaijuu cough

This is a great use of the sumo api I'm really impressed with how it has come together.

Sumostakes is ready to go for January 2024. Once we get another couple of tournaments of data I will open the player banzuke so you can try to reach Yokozuna.

As part of developing sumostakes, I added infrastructure for sending webhooks from the sumo-api. This feature is now accessible to anyone who wants to use it - you can find the details here. So if you are developing a sumo game or some other service using sumo-api and are currently polling it in order to retrieve data you no longer need to do so. Of course there might still be issues with this service since it is new and I haven't tested it under load. Feel free to subscribe to them and see what happens when the next banzuke is released on 25th December. Feel free to send a DM if you have questions or problems. In addition, I fixed a couple of bugs and I improved the checking for a new banzuke. Previously I only grabbed the new one on the first day of the month in which a basho would take place, but it now checks the Monday 2 weeks before the basho, so there should be no delays in getting this data any more.

All done for 2023 - mostly successful once the formula was tweaked I think. There is a bug in the overall performance table you will see in your profile page now, which is due to how the scoring was adjusted during the basho. I'll see if I can fix it, but it's a long shot... and basically its open beta, so this data is a mess anyway. Please if you played, give me some brief feedback here i'd really appreciate it.

Theorectically, but unlikely I think. I haven't thought of a way around that yet. Is it an issue? It's a game about sumo, not sumo. I'm not sure if it matters.

The finish line is in sight! Keep staking to secure your kachikoshi (8 days or more of point gains). If you can, I'd love your feedback about the game here - max 2-3 minutes to complete.

Added a fix for matches which result in fusen - these are effectively ignored by the point calculator. You can still stake those matches, but your points will simply be returned, no loss, no gain, so better to stake them elsewhere.

It's a good question. As of now nothing, but that is not a good solution. I will add a fix, after today, that returns any points on a fusen result. It's not straightforward to automate anything to prevent staking ahead of time. I expect a few players added stakes on Nishikifuji as a result.