Skip to content
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

Add Guiding Land Locations to Monsters #144

Open
DeveloperPaul123 opened this issue Feb 6, 2020 · 2 comments
Open

Add Guiding Land Locations to Monsters #144

DeveloperPaul123 opened this issue Feb 6, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@DeveloperPaul123
Copy link

Would be good to add locations monsters can spawn in the Guiding Lands to the monster object. We can also include the spawn change for these based on the level of the guiding lands zone.

Given it's complexity, not sure if it makes sense to put this in the monster endpoint or make it a different endpoint.

@LartTyler LartTyler added the enhancement New feature or request label Feb 10, 2020
@LartTyler
Copy link
Owner

Definitely think this is a good idea. I'll add it to the backlog, though I'm not sure how to best add this information. I think a new endpoint might be the best option, but I'll have to think on it.

@DeveloperPaul123
Copy link
Author

I think it depends on what information you want to include. I think it would be good to include:

  • Collectibles (i.e. bones/ores and drop rates) this info can also be added to the other locations so it would make sense to leave this in the locations end point
  • Monster spawn rate: I think you could make this a sub object inside the monster endpoint. Basically a guiding_lands_spawns that contains an array of zones in the guiding lands with a spawn rating (1 - 3 stars), the zone level associated with the spawn and then an indication of whether the spawn is tempered or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants