Skip to content

fix(FieldManager): handle FieldToHome portal migration correctly - #539

Merged
AngeloTadeucci merged 1 commit into
masterfrom
dev-1
Jul 10, 2025
Merged

fix(FieldManager): handle FieldToHome portal migration correctly#539
AngeloTadeucci merged 1 commit into
masterfrom
dev-1

Conversation

@AngeloTadeucci

@AngeloTadeucci AngeloTadeucci commented Jul 10, 2025

Copy link
Copy Markdown
Collaborator

Summary by CodeRabbit

  • New Features
    • Added support for portals that transport players directly to their home map.

@coderabbitai

coderabbitai Bot commented Jul 10, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

A new case for the PortalType.FieldToHome was added in the UsePortal method within FieldManager.cs. This enables player migration to a default home map using the portal's HomeId when this portal type is used. No other logic or public interface changes were introduced.

Changes

File(s) Change Summary
Maple2.Server.Game/Manager/Field/FieldManager/FieldManager.cs Added handling for PortalType.FieldToHome in the UsePortal method to migrate players to their home map.

Sequence Diagram(s)

sequenceDiagram
    participant Player
    participant FieldManager
    participant Session

    Player->>FieldManager: UsePortal(portal)
    FieldManager->>FieldManager: switch(portal.Type)
    alt PortalType.FieldToHome
        FieldManager->>Session: MigrateToMap(Constant.DefaultHomeMapId, portal.HomeId)
    else Other portal types
        FieldManager->>Session: Existing portal handling logic
    end
Loading

Possibly related PRs

Suggested reviewers

  • Zintixx

Poem

In the fields where portals gleam,
A new path home now joins the stream.
Step through the gate, don’t delay—
To your cozy home, you’ll find your way.
With a hop and a skip, the code is done,
Another adventure has just begun!
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
Maple2.Server.Game/Manager/Field/FieldManager/FieldManager.cs (1)

553-555: LGTM! Clean implementation of FieldToHome portal handling.

The new case correctly handles PortalType.FieldToHome by migrating the player to the default home map using the portal's HomeId as the owner identifier. The implementation follows the established pattern of other portal types in the switch statement.

Consider adding validation for fieldPortal.HomeId to ensure it's a valid home identifier:

 case PortalType.FieldToHome:
+    if (fieldPortal.HomeId <= 0) {
+        session.Send(FieldEnterPacket.Error(MigrationError.s_move_err_default));
+        return false;
+    }
     session.Migrate(Constant.DefaultHomeMapId, fieldPortal.HomeId);
     break;
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7ab0160 and db26c04.

📒 Files selected for processing (1)
  • Maple2.Server.Game/Manager/Field/FieldManager/FieldManager.cs (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
Maple2.Server.Game/Manager/Field/FieldManager/FieldManager.cs (2)
Maple2.Server.Game/Session/GameSession.cs (1)
  • Migrate (674-706)
Maple2.Model/Metadata/Constants.cs (1)
  • Constant (10-960)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: build
  • GitHub Check: build
  • GitHub Check: format

@AngeloTadeucci
AngeloTadeucci merged commit 4c39caf into master Jul 10, 2025
4 checks passed
@AngeloTadeucci
AngeloTadeucci deleted the dev-1 branch July 10, 2025 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant