MSRevive / MSRevive/map-sources
Propose mapping/compiler parameter standards?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Maps (especially lighting) can look quite different depending on who compiled it. We should have some kind of reference or standard for map compiling parameters that are ideal for modern PCs and players. Always, always use VHLT v34 for compiling!
EXAMPLE MY CONFIG for Nem's batch compiler:
CSG (wads will differ per map)
BSP all defaults
VIS
RAD
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
No repository file or test is named. Start by reviewing the example Nem's batch compiler configuration and the requirement to use VHLT v34, then determine where a shared compiling-parameter reference would belong. Done would require an agreed standard and a documented location for it.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev, tooling
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100