Replies: 2 comments 1 reply
-
|
I'm not sure what gave you the idea that the current system is entirely fabricated but I can assure you it is not. I worked with someone (Wiggo iirc) on gathering retail captures for several weeks and then implemented what we have now. I believe the underlying system is retail accurate. I will admit that the plant data (seeds + crystal) results are somewhat fabricated as there was never much data accumulated for them as it'd take a very long time to do so. You are welcome to investigate and see if I did happen to miss something. This project was like the second thing I did for the codebase and it was about 8 years ago at this point. If you are going to look into it I recommend digging into the pot extra data first as I believe that is where all the details live. Good luck! |
Beta Was this translation helpful? Give feedback.
-
|
It's all good I know that a great deal of what was added to legacy DSP code was more fabricated than retail accurate. It's been a long time but I believe everything was tested for the gardening system including things like it not updating the plants unless you zone in. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently the way gardening works is when the player enters their mog house, the server will check if their plants need to be updated and if so, advances them to the next stage (or withers them). When the player examines their plants, a bit is flipped in the database to signify that it was examined for the current stage, and the bit is unset when the stage advances.
This has a number of problems like:
I feel like this should be pretty easy to fix into something that makes more sense - the goal being that plants advance at a constant pace regardless of when you enter your mog house and withering happens if you don't check your plants once per ~24 hours. I don't know if any real gardening data exists to know exactly how it should work, but the current system is entirely fabricated so updating it to something that "feels" better seems reasonable.
There's two main problems causing the current state.
Before I do any work here (I think it's probably only about 10-20 lines of code total), I'd be curious to know if anyone has thoughts about why this might be a bad idea, what changes might be needed to ensure the PR isn't rejected, or any reasons why those extra flowerpot bytes can't be used.
Beta Was this translation helpful? Give feedback.
All reactions