You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 5, 2019. It is now read-only.
Diamond ore planets are very powerful and have the potential to completely inflate the economy of a space server. As a result, there should be a way to either limit them or "hide" them a little better from players.
This could be done with a configurable boolean in the config.yml giving the administrator the discretion to decide whether he or she wishes for diamond ore to only be cores or if it can also be planet shells.
The text was updated successfully, but these errors were encountered:
Based on what I saw in planets.yml diamond ore isn't not a part of the shell generation possibilities, do you think it should be added (if we add the boolean value system like you said)?
Doing this means we would need to alter
allowedCoreIds = new HashMap.Set.MaterialData>, Float>();
allowedShellIds = new HashMap.Set.MaterialData>, Float>();
(Note, I replaced < with . because github text hides stuff in the sideways carrots.
So that the Set contained in the the HashMap is actually another Map type that maps the block types to booleans.
After that we must then find where allowedCoreIds, and allowedShellIds are accessed and change the readin process so it takes advantage of the boolean check for config. Also because it would break since we changed the data storage type.
Diamond ore planets are very powerful and have the potential to completely inflate the economy of a space server. As a result, there should be a way to either limit them or "hide" them a little better from players.
This could be done with a configurable boolean in the
config.yml
giving the administrator the discretion to decide whether he or she wishes for diamond ore to only be cores or if it can also be planet shells.The text was updated successfully, but these errors were encountered: