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

spawn locations should be repeatable with the same seed #100

Open
keturn opened this issue Jun 22, 2022 · 0 comments
Open

spawn locations should be repeatable with the same seed #100

keturn opened this issue Jun 22, 2022 · 0 comments
Labels
Good First Issue Good for learners that are new to Terasology Size: S Small effort likely only affecting a single area and requiring little to no research Topic: WorldGen Requests, Issues and Changes related to facets, rasterizers, etc. Type: Improvement Request for or addition/enhancement of a feature

Comments

@keturn
Copy link
Contributor

keturn commented Jun 22, 2022

Games with the same seed and world generator should have the same results when they choose which chunks to spawn in.

@ReceiveEvent
public void onChunkGenerated(OnChunkGenerated event, EntityRef worldEntity) {
boolean trySpawn = config.spawnChanceInPercent > random.nextInt(100);

@keturn keturn added Type: Improvement Request for or addition/enhancement of a feature Size: S Small effort likely only affecting a single area and requiring little to no research Good First Issue Good for learners that are new to Terasology Topic: WorldGen Requests, Issues and Changes related to facets, rasterizers, etc. labels Jun 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Good First Issue Good for learners that are new to Terasology Size: S Small effort likely only affecting a single area and requiring little to no research Topic: WorldGen Requests, Issues and Changes related to facets, rasterizers, etc. Type: Improvement Request for or addition/enhancement of a feature
Projects
None yet
Development

No branches or pull requests

1 participant