Change Details

If a blueprint is converted into chunk32 from a chunk16 version of starmade, when that blueprint is used as part of a response fleet the docked entities will separate. This can be worked around since spawning the blueprint as admin without use of a response fleet will spawn the entity with all docks connected, you can then blueprint this one in the chunk 32 environment and it will function correctly in response fleets. chunk16 test print:{F8881}

If a blueprint is converted into chunk32 from a chunk16 version of starmade, when that blueprint is used as part of a response fleet the docked entities will separate. This can be worked around since spawning the blueprint as admin without use of a response fleet will spawn the entity with all docks connected, you can then blueprint this one in the chunk 32 environment and the new blueprint will function correctly in response fleets. https://youtu.be/VmJEABd06q0 chunk16 test print:{F8881}

If a blueprint is converted into chunk32 from a chunk16 version of starmade, when that blueprint is used as part of a response fleet the docked entities will separate. This can be worked around since spawning the blueprint as admin without use of a response fleet will spawn the entity with all docks connected, you can then blueprint this one in the chunk 32 environment and itthe new blueprint will function correctly in response fleets. https://youtu.be/VmJEABd06q0 chunk16 test print:{F8881}