-
Notifications
You must be signed in to change notification settings - Fork 762
Feat: Troop transport retreats to closest owned tile #2789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
WalkthroughTransportShipExecution enhanced to track and reuse retreat destinations. When boats retreat, the system now computes the nearest owned shore tile once using Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Pre-merge checks✅ Passed checks (5 passed)
📜 Recent review detailsConfiguration used: Organization UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used🧠 Learnings (2)📓 Common learnings📚 Learning: 2025-05-19T06:00:38.007ZApplied to files:
🧬 Code graph analysis (1)src/core/execution/TransportShipExecution.ts (2)
🔇 Additional comments (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
If this PR fixes an issue, link it below. If not, delete these two lines.
Resolves #1139
Description:
Adds logic to troop transport retreat behaviour which retreats a transport to the closest owned tile instead of the source. Realized we can use the existing
closestShoreFromPlayer()function here without adding any additional logic. Now if no shores are detected (you lost all your shoreline while the transport was out) we handle the return case same as if the original source was no longer your territory.Screen.Recording.2026-01-04.031913.mp4
Please complete the following:
Please put your Discord username so you can be contacted if a bug or regression is found:
bijx