I've been looking for a solution to a crash that occurs when someone joins. I scoured the code and found nothing, then a user that worked with me (SilverSnake) said he MOVED his character in the 0,0 spawn location and it all came together. There is an event to trap character movement, this enforces the boundaries in the game. It looks at a data array that is not created until you spawn in your base, and THAT was the issue. The old code worked only for the first player because Brave New World only ever has one Force playing, but Brave New Oarc has many forces. If the first player joins his own force, subsequent players could cause this crash. DOH - Fixed in 4.2.08.
Transport Drones mod running with BNO, causes transports to explode. This is the same issue as the exploding bots, which I have fixed. This is also fixed.
Added Transport drones as a supported mod.
I did some profiling since we played a game with about 7 or 8 players and once we got pretty big - everyone with extra roboports, the game became jittery. The cause is both "World Eater" a part of regrowth and reclaiming parts of the world that need to be covered up to save on cpu load, and Shared Energy. Each of these have loops that run 60 times per second. I will reduce their load, but in the interim, as admin,you can type: /sc global.world_eater_disable=true
World Eater removes abandoned buildings, radars from players that have left the game. It collects a list of chunks that later will be restored to it's previous state, if it's never been scanned by radar. It USED to blow up bots, and remove transports in transport_drones mod - that is fixed. Then it looks for items and chunks of land that were owned by abandoned players. Each chunk is checked slowly over time and maked with a timer, or marked permanent so as not to remove items on the map that are not to be removed. It's pretty awesome code that reclaims parts of the map. I do recommend on a big game to turn it off, in the late game. If you have alot of players joining and quiting - turn it ON, then wait an hour and turn it off. I might add a feature that does that automatically, or better let's you run a routine to do it over a couple seconds and be done with it. If I can't reduce it's load, I'll make a menu selection for CLEAN UP.
