fix(docs): rename QuestProgressExtended packet definition and harden IP resolver setup

[Rhefew]

This PR contains documentation updates, IP resolver initialization hardening, and minor web styling cleanups:

Packet Definition Documentation:

• Renames the QuestProgressExtended packet definition document from C1 F6 0C to C2 F6 0C to reflect the correct C2 message code formatting.

IP Resolver Hardening:

• Resolves startup crashes when an invalid custom IP resolver configuration parameter (empty/whitespace string) is supplied, falling back to environment-based resolution.
• Adds diagnostic console logging in IpAddressResolverFactory.cs showing detailed resolving metrics during server startup.

CSS layout formatting:

• Cleans up custom range settings and expand alignments in Bootstrap stylesheet imports.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a series of maintenance improvements focused on documentation accuracy, system stability during network initialization, and UI styling consistency. The changes ensure that packet definitions align with current standards, prevent potential runtime exceptions in the IP resolution logic, and clean up CSS definitions to maintain a cleaner layout.

Highlights

• Packet Documentation: Renamed the QuestProgressExtended packet definition from C1 to C2 to match correct message code formatting and updated relevant documentation.
• IP Resolver Hardening: Improved robustness of the IP resolver by adding validation to prevent startup crashes when invalid custom parameters are provided, and added diagnostic logging.
• CSS Cleanup: Refactored Bootstrap stylesheet imports to improve alignment and layout consistency for custom range settings and navbar elements.

New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates packet documentation for QuestProgressExtended, refactors CSS properties in shared.css, and enhances IP address resolution logic in IpAddressResolverFactory.cs to handle invalid custom configurations. The review feedback suggests replacing a debug Console.WriteLine with structured logging using the existing logger factory, and simplifying an empty conditional block by inverting its logic.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.