Terasology / Terasology/ModuleTestingEnvironment
provide in-memory world implementation (MapWorldProvider)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
While converting some tests from WorldProvidingHeadlessEnvironment to ModuleTestingEnvironment, I discovered that WPHE uses MapWorldProvider, which generates chunks on demand.
There might be a handful of modules providing large-scale features that need to deal with the intricacies of chunk loading, and they should be able to use the default WorldProvider so they don't get a false sense of security. But I think most tests for most modules are only interested a small area, and this on-demand behavior would make things much easier for them. It would eliminate the need for them to use things like forceAndWaitForGeneration.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the existing MapWorldProvider with the WorldProvidingHeadlessEnvironment and ModuleTestingEnvironment paths mentioned in the issue. Check how tests currently use forceAndWaitForGeneration; done means most small-area module tests can use the in-memory provider with chunks generated on demand, while preserving the default provider for chunk-loading behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100