Refactor RiftManager creation logic to be a bit more stable by DB config #347
Labels
Difficulty: Easy
This issue would be easy to do, and has little uncertainty in scope and implementation
good first issue
Good for newcomers
Priority: Low
This ticket is not part of any forseen need or upcoming roadmap item
Refactor
Code maintainability, style, or other non-functional changes
https://github.com/OpenPerpetuum/PerpetuumServer/blob/Development/src/Perpetuum.Bootstrapper/PerpetuumBootstrapper.cs#L2423-L2438
and
https://github.com/OpenPerpetuum/PerpetuumServer/blob/Development/src/Perpetuum/Services/RiftSystem/ZoneRiftConfigs.cs#L10-L31
and
https://github.com/OpenPerpetuum/PerpetuumServer/blob/Development/src/Perpetuum/Services/RiftSystem/RiftManager.cs#L71
Could be refactored to only create a RiftManager instance if the ZoneRiftConfig has a non-zero entry for the zone.
Otherwise zones that are not training/stronghold zones will need a 0'd out entry per zone, and will have an update loop that does nothing.
The text was updated successfully, but these errors were encountered: