Determine how to mark and behave in functions that require Mystcraft when it is not present.
This library should be usable by clients who want to interoperate with Mystcraft, but don't want to introduce a hard dependency on Mystcraft.
For instance, some mods may wish to provide symbols for their added blocks and fluids if Mystcraft is present, without crashing if Mystcraft isn't installed.
We should probably mark each method in Javadoc as requiring Mystcraft to function or not.
Internal initialization logic that depends on Mystcraft should early exit if Mystcraft is not available.
Functions that return no values should probably just early exit if Mystcraft is not available.
Functions that return values are more tricky. Should they throw an exception? Should they return null?
Should we expose a convenience function to check whether Mystcraft is loaded? I believe it's just a one liner, but even so it's probably worth having a canonical implementation.