Sort numbers
-
This is purely from observation of use by vanilla…
sort = Value from 0-99. Higher the value, higher the precidence. Used to determine priority of overlapping zones. Try to ensure that you have established some sort of scheme to establish this when planning your encounter zones. Rule of Thumb, Patrols always have higher precidence, patrols from more powerful factions in that system have higher precidence over other patrols. Ambient, base, and planet population zones have the lowest precidence.
P.S. When are you gonna join the SWWT team mate?
-
Forsaken pretty much hit the nail on the head. As a general rule of thumb, the bigger the zone, the lower the sort - especially if that zone has other zones inside of it. Any zones that you have “cutting” through multiple zones - like patrols - should have the highest sort. When you think about it, it makes sense.
Just try to make sure you don’t have too many overlapping zones with the same sort value. If too many overlapping zones have the same sort, FLServer will eventually get confused and crash.
-
I have made a tutorial with some more information about sort numbers here:
-
My dumb question: can you remove these for non-encounter zones? In my caseI have asteroid fields that don’t have any NPC populations although there is an overlapping zone that does have an NPC population.
For example…
[Zone]
nickname = Zone_Br03_field_01
pos = -87447, 0, 6437
size = 33798, 21459, 21459
shape = ELLIPSOID
sort = 34 <–— can I delete this?[Zone]
nickname = Zone_Br03_pop_field_02
pos = -87447, 0, 6437
size = 35798, 25459, 25459
shape = ELLIPSOID
repop_time = 15
max_battle_size = 4
pop_type = major_tradelane
relief_time = 15
faction_weight = co_be_grp, 10
faction_weight = co_nws_grp, 10
faction_weight = co_rs_grp, 10
encounter = tradelane_trade_freighter, 5, 0.190000
sort = 40
