Empty Requirements
pupnewfster opened this issue ยท 0 comments
Allow things that we annotate in CrT documentation to have optional requirements to actually support having no requirements. Currently we throw an error if they don't give any reqs. This would probably be mainly used for things like traits or dummy traits where they have a skill point cost.
The issue is the check method errors out when the requirements string is null.