Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
That's a pretty good idea, never occured to me how the wiki is very active and we can use it for things like this We are going to do a major redesign of the algorithm in this break week and brainstorm ways to prevent pump and dumps, we'll definitely incorporate this into the algorithm as well and i'll hit you up again with the changes before merging Also for the poll, we do want to make it so that the prices require as little human intervention as possible, but we do have a discord bot connected so we could explore this as well. The wiki really opens up a lot of avenues for us, to be honest we could just pass the chapter summary into gemini to help decide the prices |
|
actually yea I never thought of AI, that could add as little bias as possible for the weekly algo and Gemini API is pretty cheap for 1 call per week but the data it gives back is not always structured so that could cause runtime errors. |
|
Gemini api is actually free for 50 requests a minute, at least it was the last time I used it, and i'm pretty sure now they support structured output, even if they don't I wrote a snippet a while back that lets you stream structured output and will use that, but gemini is a longshot, i dont think AI can capture the nuances we want while deciding prices at least for now. |
For more variance of the stocks, I thought adding an appearance tax could be good idea where I fetch on the cron job weekly the characters included in the latest chapter in the wiki (The strawhats get much less tax than other characters since they are the main characters and appear every chapter)
I left a comment onto why I didn't want to change things too much around the DB that's why it's a rather simple feature.
Feature could be improved on if we can store last week chapter appeared characters then randomly poll users if they thought the character had a positive (+10) neutral (+1), negative(-10) showing is another idea I had but I would need to mess around in the DB again.