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

implemented user configurable world height, cleaned up commits #4102

Open
wants to merge 2 commits into
base: v3.0
Choose a base branch
from

Conversation

JurgenKuyper
Copy link
Collaborator

continuation of #4100, now only one commit wrt v3.0

Copy link

@minimusubi minimusubi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in general, im personally not a fan of having to configure the world height and negative adjustment per-world in a config file. i believe it would be a better user experience if we could detect the world height automatically. this is where mikeprimm's input would be valuable

}
else{
worldheight = configuration.getInteger("worldheight", 348);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

384, not 348 (64 + 320). however, i would caution against this, as it now requires users to manually specify the world height for nether and end worlds

fillcolor = new Color[worldheight]; /* Color by Y, must be range of total world height, offset by +64*/
/* Load defined colors from parameters */
for(int i = 0; i < worldheight; i++) {
fillcolor[i] = configuration.getColor("color" + (i - 64), null); /* need to substract by 64 because Color does not accept <0 indexes*/

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i - 64 will be incorrect for end and nether worlds (they still use 0-255)

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

Successfully merging this pull request may close these issues.

2 participants