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

World change causes crash with Mo'Creatures installed #84

Open
twothe opened this issue Oct 29, 2020 · 1 comment
Open

World change causes crash with Mo'Creatures installed #84

twothe opened this issue Oct 29, 2020 · 1 comment

Comments

@twothe
Copy link

twothe commented Oct 29, 2020

In at.feldim2425.moreoverlays.lightoverlay.integration.CustomSpawnerLightScanner

    List<Biome.SpawnListEntry> possibleSpawns = CustomSpawner.instance().getPossibleCustomCreatures(world, environment.entitySpawnTypes.get("MONSTER"), pos.getX(), pos.getY(), pos.getZ());

    return !possibleSpawns.isEmpty();

The returned list possibleSpawns can be null when changing worlds (i.E. to the Nether or back), which will then instantly result in a crash. This can also happen when logging in, which then causes the world to be unplayable until MoreOverlays is deactivated.

Using Minecraft 1.12 with Forge 2854. MoreOverlays 21.7.19, CustomMobSpawner 3.11.5.

@Pyker
Copy link

Pyker commented Jun 2, 2021

This is a duplicate of #72

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

No branches or pull requests

2 participants