RE: RE: 🚧 Ongoing Site Updates: Python ➡️ Next.js
You are viewing a single comment's thread from:

RE: 🚧 Ongoing Site Updates: Python ➡️ Next.js

Words
198
Reading
1 min
1y

I definitely agree with you—this method isn’t exact. I’ve thought about various alternatives, but honestly, none of them are perfect either.

For example, using resource cost as the base can vary a lot depending on how the player generates Aura—like using a magical plot vs. a regular one (100% output difference), plus all the possible boosts that come into play.

Some might argue that you should use the highest resource price for buying and the lowest for selling, but calculating values based on markets like the Auction Marks adds even more complexity—especially considering the other required resources involved.

That’s why I’ve stuck with using Midnight Potions for now. While not perfect, they’re currently tied to the least valued resource (and I expect that to stay consistent due to the recipe requirements), and it’s the most straightforward method for users to understand.

That said, my ultimate goal is to make the calculation player-specific—so in the player overview, you’d see Aura cost based on their actual plots and setup. Every plot would have a net DEC value, allowing us to determine exactly what that specific player can produce Aura for. Just whish there is more time in a day 🤣

@beaker007: I definitely | Ecency