Description

Currently, the teleport position (TP pos) is stored within the region type, separate from the area definition. To improve consistency and maintainability, the TP pos should be moved into the area definition of a region. This change ensures that all spatial information is contained within a single structure.

Expected Behavior

• The TP pos should be part of the area definition rather than the region type.
• Existing logic that accesses or modifies the TP pos should be updated accordingly.
• Any serialization or deserialization of regions should reflect this change.

Possible Solutions

• Modify the area definition to include a TP pos field.
• Update region handling logic to retrieve and store the TP pos in the new location.
• Ensure backward compatibility or provide migration for existing data.

Steps to Implement

• Add a TP pos field to the area definition structure.
• Consider multiple named TP positions for areas
• Adjust existing code that references TP pos from the region type.
• Update serialization/deserialization logic.
• Test with existing and newly created regions to ensure proper functionality.