Question: What does the □ mean -> skipped
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 540
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
Quick question. In my output I see something like that:
[4d 0h 45m 13.147999999986496s] 84.3499% 216.89m/257.14m @ 275/s | ✓ 216.89m □ 100.78m | 1d 16h 40m 8s left
So there are 100.78m tiles skipped. But what does that mean? Were there error generating those (if so... any change I can see what those are)? Is it save to use the resulting tileset? Or will there be missing things? Or is this just something like "There is no data here... e.g. sea"?!?
Couldn't find a README for that...
Contributor guide
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 with the displayed tile-generation output and trace how the skipped-tile count and □ marker are produced. Document what skipped tiles represent, whether they indicate errors or expected empty areas, and how users can identify them; the result should answer the questions raised in the issue and provide the missing README guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100