The the same version of Nitrogen (v0.501 which is the latest current build) was fine for the previous map (the first a19 map) we were using. So it is not the map versioning issue, otherwise the same problem would have been present for the first map we were playing for a19.
Hardware wise - it has been OK so far for us. We dont have 16 anyway. More like 4 to 6 players. Its a dedicated physical machine with 32 GB of RAM and an SSD only for the 7d2d files with 1 Gbps net connection. CPU is indeed a bit over decade old but even 16x16 km map is light enough on it that it does not even have to clock up to the max it can other than during blood moons.
Anyway - I went and shut down the current machine, did a new Nitrogen map with the same parameters in 8x8 km size (in case its the size issue) and tried it. Still getting "NO TRADER" after placing the campfire. There is actually 4 traders on the map, looking at the generated map preview.
As far as I can see, this is the problem spot in the server log:
NullReferenceException: Object reference not set to an instance of an object.
at NetPackageQuestGotoPoint.ProcessPackage (World _world, INetConnectionCallbacks _netConnectionCallback) [0x00157] in <bb2961016a004bd4bf77288a67df32f1>:0
at ConnectionManager.ProcessPackages (INetConnection _connection, NetPackageDirection _disallowedDirection) [0x000b2] in <bb2961016a004bd4bf77288a67df32f1>:0
at ConnectionManager.Update () [0x00053] in <bb2961016a004bd4bf77288a67df32f1>:0
(Filename: <> Line: 0)
I do not see a file named "bb2961016a004bd4bf77288a67df32f1" in the server. So my hypothesis is that first time I was playing a19 the file was not there and was generated. Now its sitting somewhere where windows search cant find it and is messing things up. Probably. Each next map I use is trying to look something up in that file, it seems, which is not there because it was for a previous map, obviously. Now I'm not a game dev and that is just my current hypothesis. Maybe someone who knows better than me can enlighten me what do to about that, though.
View attachment 14430