add ideas for handling "same-location" spawnpoints that sometimes seem to happen to README.md
This commit is contained in:
parent
d1ee8fea63
commit
30a4888bfb
13
README.md
13
README.md
@ -117,3 +117,16 @@ When the archives are ready, run
|
|||||||
|
|
||||||
The program will process the dumps to generate the loot files and stores them directly in the correct place
|
The program will process the dumps to generate the loot files and stores them directly in the correct place
|
||||||
in your SPT-AKI server development folder specified in *server/location* in the config.yaml
|
in your SPT-AKI server development folder specified in *server/location* in the config.yaml
|
||||||
|
|
||||||
|
# Todos:
|
||||||
|
|
||||||
|
- Check for spawnpoints with location duplicates
|
||||||
|
- Option 1
|
||||||
|
- If that happens only group by xyz-coords, without rotation
|
||||||
|
- spawnpoints with different rotations but same position will be combined
|
||||||
|
- each item in the distribution will receive a rotation attribute to define how to place it
|
||||||
|
- Pro/Con: simpler server code, simpler generation code, larger file size
|
||||||
|
- Option 2
|
||||||
|
- keep spawnpoints as is (same location but different rotation lead to separate spawnpoints)
|
||||||
|
- make a "xyz location id" and after drawing, filter out all with same id from pool
|
||||||
|
- Pro/Con: smaller file size, not sure yet how to create such a location id in the current generation code
|
Loading…
x
Reference in New Issue
Block a user