Non-SRD monsters should be removed about 5e-database

[Alex-frazer]

what's the reason for why they need to be removed?

[ogregoire]

@Alex-frazer Because they're part of the MM, which is entirely proprietary. Only the SRD is subject to the OGL which allows us to put that data in this project. If it's in the SRD, we can put it here. If it's in any other D&D publication, we may not because of copyright laws.

[bagelbits]

I really hate that this is a thing but yeah you're right. @ogregoire If you're going to do this, can you updated the README to say something about things only subject to OGL, which is mostly just SRD?

[benjaminapetersen]

Agree, for legal reasons anything not explicitly SRD should not be included. The repo should be canonical only.

Now, there is nothing stopping people from forking the repo and adding their own separate JSON files of the same format with homebrew, etc. monsters.

[benjaminapetersen]

Seems documents like this could be helpful for understanding legal requirements:

https://github.com/benjaminapetersen/open5e-api/blob/master/data/creature_codex/document.json

[benjaminapetersen]

Also Roll20 seems to do well with SRD content. They have a number of public repos, such as https://github.com/Roll20/roll20-api-scripts.

But I don't know where they get their data.

[benjaminapetersen]

Referencing issue #114 as a possible way to verify before changes.