-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relic gear #4
Comments
I think this is related to the persistency issue, as currently there is no place to store persistent data. My wife and I are working on a newer version of Frontend to make it possible. Thanks a lot for those constructive suggestions! |
Well, regarding relics I think there are actually three separate issues.
Really this issue was about the second point. Relic gear is much more easily gotten than charms so we could safely consider it to be ‘craftable’ like other parts are already considered. Perhaps there should be separate issues for points 1 and 3.
That's great to hear!
No, thank you for making the software. I planned to eventually cobble something together myself but now I don't have to. |
All of the 3 are valid issues (and not very difficult to implement). I am thinking on how to put them into the UI so that it make more sense to the user. Sorry for replying your issues so late (I overlooked them in May, sorry!) And I've actually learned from you that relic gear skills are limited! With that in mind, we can even gave instructions to the user on which monster/quest to fight/complete next! Saying that, I am really new on web stuff and just learnt it for this project. Still learning it and hopefully can get to be productive soon! Thank you for the encouragement, Fuuzetsu! |
It'd be great if there was an option to allow relic gear or to even prefer relic gear skills instead for fashionhunting.
The text was updated successfully, but these errors were encountered: