Refactor SpigotEntityIdProvider ID supplier logic - #45

Merged
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1
Dec 1, 2025
Merged

Refactor SpigotEntityIdProvider ID supplier logic#45
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1

Conversation

@TWME-TW

@TWME-TWTWME-TW commented Nov 19, 2025

Copy link
Copy Markdown
Contributor

Refactor entity ID supplier detection logic to improve maintainability and clarity.

This pull request was written by AI. It currently fixes an issue I encountered in Spigot 1.21.10.

However, since I am not very familiar with reflection, I am not entirely sure about the contents of this PR. Therefore, please make sure to review it carefully to ensure that this PR meets the requirements.

Summary by CodeRabbit

  • Refactor
    • Optimized entity ID generation logic with enhanced support across multiple server versions to improve stability and compatibility.

Refactor entity ID supplier detection logic to improve maintainability and clarity.
@coderabbitai

coderabbitaiBot commented Nov 19, 2025

Copy link
Copy Markdown

Walkthrough

Refactored SpigotEntityIdProvider to improve ID-generation robustness by replacing direct reflection logic with dedicated helper methods that handle multiple entity ID storage mechanisms across different Minecraft and Paper versions.

Changes

Cohort / File(s)Summary
ID-Generation Strategy Refactoring
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java
Replaced monolithic reflection logic with modular helper methods: resolveAtomicSupplier() for 1.14+ AtomicInteger fields, resolveLegacySupplier() for legacy int fields, and getStaticFieldOfType() for generic field location. Added version-specific branching with Paper 1.16+ path preservation via UnsafeValues.nextEntityId. Introduced Modifier import for reflection.

Sequence Diagram

sequenceDiagram
participant Client
participant detectIdSupplier
participant resolveAtomicSupplier
participant resolveLegacySupplier
participant getStaticFieldOfType
Client->>detectIdSupplier: Request ID supplier
alt Paper 1.16+
detectIdSupplier->>detectIdSupplier: Use UnsafeValues.nextEntityId
else Minecraft 1.14+
detectIdSupplier->>resolveAtomicSupplier: Resolve AtomicInteger field
resolveAtomicSupplier->>getStaticFieldOfType: Locate AtomicInteger field
getStaticFieldOfType-->>resolveAtomicSupplier: Field located
resolveAtomicSupplier-->>detectIdSupplier: Increment supplier ready
else Legacy versions
detectIdSupplier->>resolveLegacySupplier: Resolve int field
resolveLegacySupplier->>getStaticFieldOfType: Locate int field
getStaticFieldOfType-->>resolveLegacySupplier: Field located
resolveLegacySupplier-->>detectIdSupplier: Read/increment supplier ready
end
detectIdSupplier-->>Client: ID supplier
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

  • Reflection logic complexity: Review the field-location strategy in getStaticFieldOfType() for correctness across type matching and fallback scanning
  • Version-specific branching: Verify conditional logic for Paper 1.16+ detection and proper delegation between atomic and legacy paths
  • Type safety: Ensure AtomicInteger and int field resolution validates types correctly before wrapping in suppliers
  • Backward compatibility: Confirm all legacy version paths (field names, access patterns) remain intact

Poem

🐰 A rabbit hopped through reflection's maze,
With fields to find through many days,
Now atomic paths and legacy lanes,
Flow smoothly through version chains,
Each ID springs forth with graceful ease! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 40.00% which is insufficient. The required threshold is 80.00%.You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately describes the main change: refactoring the ID supplier logic in SpigotEntityIdProvider with improved maintainability.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

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 (2)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (2)

69-76: Version‑aware supplier selection and helper split look sound

The refactored detectIdSupplier() flow (Paper fast‑path → 1.14+ atomic path → legacy path) plus resolveAtomicSupplier/resolveLegacySupplier is logically consistent and keeps behavior centralized while preserving a clear failure mode via IllegalStateException. The atomic path cleanly falls back to legacy when no suitable AtomicInteger is found.

If you want easier diagnostics on odd future versions, consider (optionally) adding a debug log when:

  • resolveAtomicSupplier returns null despite a 1.14+ version, and/or
  • resolveLegacySupplier throws because no legacy counter field was found.

This would make it much easier to understand reflection breakage on new Spigot/Paper releases without changing current behavior.

Also applies to: 78-112


153-169: getStaticFieldOfType helper improves robustness; watch first‑match fallback semantics

Centralizing the reflection into getStaticFieldOfType with:

  • type checks (desiredType.isAssignableFrom(field.getType())), and
  • a static‑modifier check,

is a solid improvement and should catch most NMS name changes automatically.

One thing to be aware of: the second loop returns the first static field of the requested type. If a future Entity class ever gains multiple static AtomicInteger or int fields, this might pick the wrong one. That’s probably acceptable given current NMS layouts, but if this ever becomes an issue, you could tighten the heuristic (e.g., filter by final, by name prefix, or by requiring uniqueness before accepting a match).

Also, the Javadoc above detectIdSupplier() still mentions only "entityCount"/"d"/"c" and not the newer aliases ("counter", "nextEntityId", "b"); updating that comment would better reflect the actual lookup behavior.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between df6fe0f and 7ba8d1b.

📒 Files selected for processing (1)
  • platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (3 hunks)
🔇 Additional comments (1)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (1)

3-20: Imports for reflection and Bukkit/Paper APIs look correct

The added Modifier import and the Bukkit / Paper / Platform imports align with the new helper and usage; no issues here.

@Tofaa2Tofaa2 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

LGTM!

@Tofaa2

Copy link
Copy Markdown
Owner

Thank you!

@TWME-TW

Copy link
Copy Markdown
ContributorAuthor

Please make sure to review this PR carefully, because I don't really know what I'm doing.

@Tofaa2
Tofaa2 merged commit b8ec880 into Tofaa2:masterDec 1, 2025
2 checks passed
Sign up for freeto 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.

2 participants

@TWME-TW@Tofaa2
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

Refactor SpigotEntityIdProvider ID supplier logic - #45

Merged
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1
Dec 1, 2025
Merged

Refactor SpigotEntityIdProvider ID supplier logic#45
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1

Conversation

@TWME-TW

@TWME-TWTWME-TW commented Nov 19, 2025

Copy link
Copy Markdown
Contributor

Refactor entity ID supplier detection logic to improve maintainability and clarity.

This pull request was written by AI. It currently fixes an issue I encountered in Spigot 1.21.10.

However, since I am not very familiar with reflection, I am not entirely sure about the contents of this PR. Therefore, please make sure to review it carefully to ensure that this PR meets the requirements.

Summary by CodeRabbit

  • Refactor
    • Optimized entity ID generation logic with enhanced support across multiple server versions to improve stability and compatibility.

Refactor entity ID supplier detection logic to improve maintainability and clarity.
@coderabbitai

coderabbitaiBot commented Nov 19, 2025

Copy link
Copy Markdown

Walkthrough

Refactored SpigotEntityIdProvider to improve ID-generation robustness by replacing direct reflection logic with dedicated helper methods that handle multiple entity ID storage mechanisms across different Minecraft and Paper versions.

Changes

Cohort / File(s)Summary
ID-Generation Strategy Refactoring
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java
Replaced monolithic reflection logic with modular helper methods: resolveAtomicSupplier() for 1.14+ AtomicInteger fields, resolveLegacySupplier() for legacy int fields, and getStaticFieldOfType() for generic field location. Added version-specific branching with Paper 1.16+ path preservation via UnsafeValues.nextEntityId. Introduced Modifier import for reflection.

Sequence Diagram

sequenceDiagram
participant Client
participant detectIdSupplier
participant resolveAtomicSupplier
participant resolveLegacySupplier
participant getStaticFieldOfType
Client->>detectIdSupplier: Request ID supplier
alt Paper 1.16+
detectIdSupplier->>detectIdSupplier: Use UnsafeValues.nextEntityId
else Minecraft 1.14+
detectIdSupplier->>resolveAtomicSupplier: Resolve AtomicInteger field
resolveAtomicSupplier->>getStaticFieldOfType: Locate AtomicInteger field
getStaticFieldOfType-->>resolveAtomicSupplier: Field located
resolveAtomicSupplier-->>detectIdSupplier: Increment supplier ready
else Legacy versions
detectIdSupplier->>resolveLegacySupplier: Resolve int field
resolveLegacySupplier->>getStaticFieldOfType: Locate int field
getStaticFieldOfType-->>resolveLegacySupplier: Field located
resolveLegacySupplier-->>detectIdSupplier: Read/increment supplier ready
end
detectIdSupplier-->>Client: ID supplier
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

  • Reflection logic complexity: Review the field-location strategy in getStaticFieldOfType() for correctness across type matching and fallback scanning
  • Version-specific branching: Verify conditional logic for Paper 1.16+ detection and proper delegation between atomic and legacy paths
  • Type safety: Ensure AtomicInteger and int field resolution validates types correctly before wrapping in suppliers
  • Backward compatibility: Confirm all legacy version paths (field names, access patterns) remain intact

Poem

🐰 A rabbit hopped through reflection's maze,
With fields to find through many days,
Now atomic paths and legacy lanes,
Flow smoothly through version chains,
Each ID springs forth with graceful ease! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 40.00% which is insufficient. The required threshold is 80.00%.You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately describes the main change: refactoring the ID supplier logic in SpigotEntityIdProvider with improved maintainability.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

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 (2)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (2)

69-76: Version‑aware supplier selection and helper split look sound

The refactored detectIdSupplier() flow (Paper fast‑path → 1.14+ atomic path → legacy path) plus resolveAtomicSupplier/resolveLegacySupplier is logically consistent and keeps behavior centralized while preserving a clear failure mode via IllegalStateException. The atomic path cleanly falls back to legacy when no suitable AtomicInteger is found.

If you want easier diagnostics on odd future versions, consider (optionally) adding a debug log when:

  • resolveAtomicSupplier returns null despite a 1.14+ version, and/or
  • resolveLegacySupplier throws because no legacy counter field was found.

This would make it much easier to understand reflection breakage on new Spigot/Paper releases without changing current behavior.

Also applies to: 78-112


153-169: getStaticFieldOfType helper improves robustness; watch first‑match fallback semantics

Centralizing the reflection into getStaticFieldOfType with:

  • type checks (desiredType.isAssignableFrom(field.getType())), and
  • a static‑modifier check,

is a solid improvement and should catch most NMS name changes automatically.

One thing to be aware of: the second loop returns the first static field of the requested type. If a future Entity class ever gains multiple static AtomicInteger or int fields, this might pick the wrong one. That’s probably acceptable given current NMS layouts, but if this ever becomes an issue, you could tighten the heuristic (e.g., filter by final, by name prefix, or by requiring uniqueness before accepting a match).

Also, the Javadoc above detectIdSupplier() still mentions only "entityCount"/"d"/"c" and not the newer aliases ("counter", "nextEntityId", "b"); updating that comment would better reflect the actual lookup behavior.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between df6fe0f and 7ba8d1b.

📒 Files selected for processing (1)
  • platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (3 hunks)
🔇 Additional comments (1)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (1)

3-20: Imports for reflection and Bukkit/Paper APIs look correct

The added Modifier import and the Bukkit / Paper / Platform imports align with the new helper and usage; no issues here.

@Tofaa2Tofaa2 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

LGTM!

@Tofaa2

Copy link
Copy Markdown
Owner

Thank you!

@TWME-TW

Copy link
Copy Markdown
ContributorAuthor

Please make sure to review this PR carefully, because I don't really know what I'm doing.

@Tofaa2
Tofaa2 merged commit b8ec880 into Tofaa2:masterDec 1, 2025
2 checks passed
Sign up for freeto 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.

2 participants

@TWME-TW@Tofaa2
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Refactor SpigotEntityIdProvider ID supplier logic - #45

Merged
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1
Dec 1, 2025
Merged

Refactor SpigotEntityIdProvider ID supplier logic#45
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1

Conversation

@TWME-TW

@TWME-TWTWME-TW commented Nov 19, 2025

Copy link
Copy Markdown
Contributor

Refactor entity ID supplier detection logic to improve maintainability and clarity.

This pull request was written by AI. It currently fixes an issue I encountered in Spigot 1.21.10.

However, since I am not very familiar with reflection, I am not entirely sure about the contents of this PR. Therefore, please make sure to review it carefully to ensure that this PR meets the requirements.

Summary by CodeRabbit

  • Refactor
    • Optimized entity ID generation logic with enhanced support across multiple server versions to improve stability and compatibility.

Refactor entity ID supplier detection logic to improve maintainability and clarity.
@coderabbitai

coderabbitaiBot commented Nov 19, 2025

Copy link
Copy Markdown

Walkthrough

Refactored SpigotEntityIdProvider to improve ID-generation robustness by replacing direct reflection logic with dedicated helper methods that handle multiple entity ID storage mechanisms across different Minecraft and Paper versions.

Changes

Cohort / File(s)Summary
ID-Generation Strategy Refactoring
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java
Replaced monolithic reflection logic with modular helper methods: resolveAtomicSupplier() for 1.14+ AtomicInteger fields, resolveLegacySupplier() for legacy int fields, and getStaticFieldOfType() for generic field location. Added version-specific branching with Paper 1.16+ path preservation via UnsafeValues.nextEntityId. Introduced Modifier import for reflection.

Sequence Diagram

sequenceDiagram
participant Client
participant detectIdSupplier
participant resolveAtomicSupplier
participant resolveLegacySupplier
participant getStaticFieldOfType
Client->>detectIdSupplier: Request ID supplier
alt Paper 1.16+
detectIdSupplier->>detectIdSupplier: Use UnsafeValues.nextEntityId
else Minecraft 1.14+
detectIdSupplier->>resolveAtomicSupplier: Resolve AtomicInteger field
resolveAtomicSupplier->>getStaticFieldOfType: Locate AtomicInteger field
getStaticFieldOfType-->>resolveAtomicSupplier: Field located
resolveAtomicSupplier-->>detectIdSupplier: Increment supplier ready
else Legacy versions
detectIdSupplier->>resolveLegacySupplier: Resolve int field
resolveLegacySupplier->>getStaticFieldOfType: Locate int field
getStaticFieldOfType-->>resolveLegacySupplier: Field located
resolveLegacySupplier-->>detectIdSupplier: Read/increment supplier ready
end
detectIdSupplier-->>Client: ID supplier
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

  • Reflection logic complexity: Review the field-location strategy in getStaticFieldOfType() for correctness across type matching and fallback scanning
  • Version-specific branching: Verify conditional logic for Paper 1.16+ detection and proper delegation between atomic and legacy paths
  • Type safety: Ensure AtomicInteger and int field resolution validates types correctly before wrapping in suppliers
  • Backward compatibility: Confirm all legacy version paths (field names, access patterns) remain intact

Poem

🐰 A rabbit hopped through reflection's maze,
With fields to find through many days,
Now atomic paths and legacy lanes,
Flow smoothly through version chains,
Each ID springs forth with graceful ease! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 40.00% which is insufficient. The required threshold is 80.00%.You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately describes the main change: refactoring the ID supplier logic in SpigotEntityIdProvider with improved maintainability.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

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 (2)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (2)

69-76: Version‑aware supplier selection and helper split look sound

The refactored detectIdSupplier() flow (Paper fast‑path → 1.14+ atomic path → legacy path) plus resolveAtomicSupplier/resolveLegacySupplier is logically consistent and keeps behavior centralized while preserving a clear failure mode via IllegalStateException. The atomic path cleanly falls back to legacy when no suitable AtomicInteger is found.

If you want easier diagnostics on odd future versions, consider (optionally) adding a debug log when:

  • resolveAtomicSupplier returns null despite a 1.14+ version, and/or
  • resolveLegacySupplier throws because no legacy counter field was found.

This would make it much easier to understand reflection breakage on new Spigot/Paper releases without changing current behavior.

Also applies to: 78-112


153-169: getStaticFieldOfType helper improves robustness; watch first‑match fallback semantics

Centralizing the reflection into getStaticFieldOfType with:

  • type checks (desiredType.isAssignableFrom(field.getType())), and
  • a static‑modifier check,

is a solid improvement and should catch most NMS name changes automatically.

One thing to be aware of: the second loop returns the first static field of the requested type. If a future Entity class ever gains multiple static AtomicInteger or int fields, this might pick the wrong one. That’s probably acceptable given current NMS layouts, but if this ever becomes an issue, you could tighten the heuristic (e.g., filter by final, by name prefix, or by requiring uniqueness before accepting a match).

Also, the Javadoc above detectIdSupplier() still mentions only "entityCount"/"d"/"c" and not the newer aliases ("counter", "nextEntityId", "b"); updating that comment would better reflect the actual lookup behavior.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between df6fe0f and 7ba8d1b.

📒 Files selected for processing (1)
  • platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (3 hunks)
🔇 Additional comments (1)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (1)

3-20: Imports for reflection and Bukkit/Paper APIs look correct

The added Modifier import and the Bukkit / Paper / Platform imports align with the new helper and usage; no issues here.

@Tofaa2Tofaa2 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

LGTM!

@Tofaa2

Copy link
Copy Markdown
Owner

Thank you!

@TWME-TW

Copy link
Copy Markdown
ContributorAuthor

Please make sure to review this PR carefully, because I don't really know what I'm doing.

@Tofaa2
Tofaa2 merged commit b8ec880 into Tofaa2:masterDec 1, 2025
2 checks passed
Sign up for freeto 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.

2 participants

@TWME-TW@Tofaa2
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Refactor SpigotEntityIdProvider ID supplier logic - #45

Merged
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1
Dec 1, 2025
Merged

Refactor SpigotEntityIdProvider ID supplier logic#45
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1

Conversation

@TWME-TW

@TWME-TWTWME-TW commented Nov 19, 2025

Copy link
Copy Markdown
Contributor

Refactor entity ID supplier detection logic to improve maintainability and clarity.

This pull request was written by AI. It currently fixes an issue I encountered in Spigot 1.21.10.

However, since I am not very familiar with reflection, I am not entirely sure about the contents of this PR. Therefore, please make sure to review it carefully to ensure that this PR meets the requirements.

Summary by CodeRabbit

  • Refactor
    • Optimized entity ID generation logic with enhanced support across multiple server versions to improve stability and compatibility.

Refactor entity ID supplier detection logic to improve maintainability and clarity.
@coderabbitai

coderabbitaiBot commented Nov 19, 2025

Copy link
Copy Markdown

Walkthrough

Refactored SpigotEntityIdProvider to improve ID-generation robustness by replacing direct reflection logic with dedicated helper methods that handle multiple entity ID storage mechanisms across different Minecraft and Paper versions.

Changes

Cohort / File(s)Summary
ID-Generation Strategy Refactoring
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java
Replaced monolithic reflection logic with modular helper methods: resolveAtomicSupplier() for 1.14+ AtomicInteger fields, resolveLegacySupplier() for legacy int fields, and getStaticFieldOfType() for generic field location. Added version-specific branching with Paper 1.16+ path preservation via UnsafeValues.nextEntityId. Introduced Modifier import for reflection.

Sequence Diagram

sequenceDiagram
participant Client
participant detectIdSupplier
participant resolveAtomicSupplier
participant resolveLegacySupplier
participant getStaticFieldOfType
Client->>detectIdSupplier: Request ID supplier
alt Paper 1.16+
detectIdSupplier->>detectIdSupplier: Use UnsafeValues.nextEntityId
else Minecraft 1.14+
detectIdSupplier->>resolveAtomicSupplier: Resolve AtomicInteger field
resolveAtomicSupplier->>getStaticFieldOfType: Locate AtomicInteger field
getStaticFieldOfType-->>resolveAtomicSupplier: Field located
resolveAtomicSupplier-->>detectIdSupplier: Increment supplier ready
else Legacy versions
detectIdSupplier->>resolveLegacySupplier: Resolve int field
resolveLegacySupplier->>getStaticFieldOfType: Locate int field
getStaticFieldOfType-->>resolveLegacySupplier: Field located
resolveLegacySupplier-->>detectIdSupplier: Read/increment supplier ready
end
detectIdSupplier-->>Client: ID supplier
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

  • Reflection logic complexity: Review the field-location strategy in getStaticFieldOfType() for correctness across type matching and fallback scanning
  • Version-specific branching: Verify conditional logic for Paper 1.16+ detection and proper delegation between atomic and legacy paths
  • Type safety: Ensure AtomicInteger and int field resolution validates types correctly before wrapping in suppliers
  • Backward compatibility: Confirm all legacy version paths (field names, access patterns) remain intact

Poem

🐰 A rabbit hopped through reflection's maze,
With fields to find through many days,
Now atomic paths and legacy lanes,
Flow smoothly through version chains,
Each ID springs forth with graceful ease! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 40.00% which is insufficient. The required threshold is 80.00%.You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately describes the main change: refactoring the ID supplier logic in SpigotEntityIdProvider with improved maintainability.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

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 (2)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (2)

69-76: Version‑aware supplier selection and helper split look sound

The refactored detectIdSupplier() flow (Paper fast‑path → 1.14+ atomic path → legacy path) plus resolveAtomicSupplier/resolveLegacySupplier is logically consistent and keeps behavior centralized while preserving a clear failure mode via IllegalStateException. The atomic path cleanly falls back to legacy when no suitable AtomicInteger is found.

If you want easier diagnostics on odd future versions, consider (optionally) adding a debug log when:

  • resolveAtomicSupplier returns null despite a 1.14+ version, and/or
  • resolveLegacySupplier throws because no legacy counter field was found.

This would make it much easier to understand reflection breakage on new Spigot/Paper releases without changing current behavior.

Also applies to: 78-112


153-169: getStaticFieldOfType helper improves robustness; watch first‑match fallback semantics

Centralizing the reflection into getStaticFieldOfType with:

  • type checks (desiredType.isAssignableFrom(field.getType())), and
  • a static‑modifier check,

is a solid improvement and should catch most NMS name changes automatically.

One thing to be aware of: the second loop returns the first static field of the requested type. If a future Entity class ever gains multiple static AtomicInteger or int fields, this might pick the wrong one. That’s probably acceptable given current NMS layouts, but if this ever becomes an issue, you could tighten the heuristic (e.g., filter by final, by name prefix, or by requiring uniqueness before accepting a match).

Also, the Javadoc above detectIdSupplier() still mentions only "entityCount"/"d"/"c" and not the newer aliases ("counter", "nextEntityId", "b"); updating that comment would better reflect the actual lookup behavior.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between df6fe0f and 7ba8d1b.

📒 Files selected for processing (1)
  • platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (3 hunks)
🔇 Additional comments (1)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (1)

3-20: Imports for reflection and Bukkit/Paper APIs look correct

The added Modifier import and the Bukkit / Paper / Platform imports align with the new helper and usage; no issues here.

@Tofaa2Tofaa2 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

LGTM!

@Tofaa2

Copy link
Copy Markdown
Owner

Thank you!

@TWME-TW

Copy link
Copy Markdown
ContributorAuthor

Please make sure to review this PR carefully, because I don't really know what I'm doing.

@Tofaa2
Tofaa2 merged commit b8ec880 into Tofaa2:masterDec 1, 2025
2 checks passed
Sign up for freeto 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.

2 participants

@TWME-TW@Tofaa2
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

Refactor SpigotEntityIdProvider ID supplier logic - #45

Merged
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1
Dec 1, 2025
Merged

Refactor SpigotEntityIdProvider ID supplier logic#45
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1

Conversation

@TWME-TW

@TWME-TWTWME-TW commented Nov 19, 2025

Copy link
Copy Markdown
Contributor

Refactor entity ID supplier detection logic to improve maintainability and clarity.

This pull request was written by AI. It currently fixes an issue I encountered in Spigot 1.21.10.

However, since I am not very familiar with reflection, I am not entirely sure about the contents of this PR. Therefore, please make sure to review it carefully to ensure that this PR meets the requirements.

Summary by CodeRabbit

  • Refactor
    • Optimized entity ID generation logic with enhanced support across multiple server versions to improve stability and compatibility.

Refactor entity ID supplier detection logic to improve maintainability and clarity.
@coderabbitai

coderabbitaiBot commented Nov 19, 2025

Copy link
Copy Markdown

Walkthrough

Refactored SpigotEntityIdProvider to improve ID-generation robustness by replacing direct reflection logic with dedicated helper methods that handle multiple entity ID storage mechanisms across different Minecraft and Paper versions.

Changes

Cohort / File(s)Summary
ID-Generation Strategy Refactoring
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java
Replaced monolithic reflection logic with modular helper methods: resolveAtomicSupplier() for 1.14+ AtomicInteger fields, resolveLegacySupplier() for legacy int fields, and getStaticFieldOfType() for generic field location. Added version-specific branching with Paper 1.16+ path preservation via UnsafeValues.nextEntityId. Introduced Modifier import for reflection.

Sequence Diagram

sequenceDiagram
participant Client
participant detectIdSupplier
participant resolveAtomicSupplier
participant resolveLegacySupplier
participant getStaticFieldOfType
Client->>detectIdSupplier: Request ID supplier
alt Paper 1.16+
detectIdSupplier->>detectIdSupplier: Use UnsafeValues.nextEntityId
else Minecraft 1.14+
detectIdSupplier->>resolveAtomicSupplier: Resolve AtomicInteger field
resolveAtomicSupplier->>getStaticFieldOfType: Locate AtomicInteger field
getStaticFieldOfType-->>resolveAtomicSupplier: Field located
resolveAtomicSupplier-->>detectIdSupplier: Increment supplier ready
else Legacy versions
detectIdSupplier->>resolveLegacySupplier: Resolve int field
resolveLegacySupplier->>getStaticFieldOfType: Locate int field
getStaticFieldOfType-->>resolveLegacySupplier: Field located
resolveLegacySupplier-->>detectIdSupplier: Read/increment supplier ready
end
detectIdSupplier-->>Client: ID supplier
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

  • Reflection logic complexity: Review the field-location strategy in getStaticFieldOfType() for correctness across type matching and fallback scanning
  • Version-specific branching: Verify conditional logic for Paper 1.16+ detection and proper delegation between atomic and legacy paths
  • Type safety: Ensure AtomicInteger and int field resolution validates types correctly before wrapping in suppliers
  • Backward compatibility: Confirm all legacy version paths (field names, access patterns) remain intact

Poem

🐰 A rabbit hopped through reflection's maze,
With fields to find through many days,
Now atomic paths and legacy lanes,
Flow smoothly through version chains,
Each ID springs forth with graceful ease! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 40.00% which is insufficient. The required threshold is 80.00%.You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately describes the main change: refactoring the ID supplier logic in SpigotEntityIdProvider with improved maintainability.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

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 (2)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (2)

69-76: Version‑aware supplier selection and helper split look sound

The refactored detectIdSupplier() flow (Paper fast‑path → 1.14+ atomic path → legacy path) plus resolveAtomicSupplier/resolveLegacySupplier is logically consistent and keeps behavior centralized while preserving a clear failure mode via IllegalStateException. The atomic path cleanly falls back to legacy when no suitable AtomicInteger is found.

If you want easier diagnostics on odd future versions, consider (optionally) adding a debug log when:

  • resolveAtomicSupplier returns null despite a 1.14+ version, and/or
  • resolveLegacySupplier throws because no legacy counter field was found.

This would make it much easier to understand reflection breakage on new Spigot/Paper releases without changing current behavior.

Also applies to: 78-112


153-169: getStaticFieldOfType helper improves robustness; watch first‑match fallback semantics

Centralizing the reflection into getStaticFieldOfType with:

  • type checks (desiredType.isAssignableFrom(field.getType())), and
  • a static‑modifier check,

is a solid improvement and should catch most NMS name changes automatically.

One thing to be aware of: the second loop returns the first static field of the requested type. If a future Entity class ever gains multiple static AtomicInteger or int fields, this might pick the wrong one. That’s probably acceptable given current NMS layouts, but if this ever becomes an issue, you could tighten the heuristic (e.g., filter by final, by name prefix, or by requiring uniqueness before accepting a match).

Also, the Javadoc above detectIdSupplier() still mentions only "entityCount"/"d"/"c" and not the newer aliases ("counter", "nextEntityId", "b"); updating that comment would better reflect the actual lookup behavior.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between df6fe0f and 7ba8d1b.

📒 Files selected for processing (1)
  • platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (3 hunks)
🔇 Additional comments (1)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (1)

3-20: Imports for reflection and Bukkit/Paper APIs look correct

The added Modifier import and the Bukkit / Paper / Platform imports align with the new helper and usage; no issues here.

@Tofaa2Tofaa2 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

LGTM!

@Tofaa2

Copy link
Copy Markdown
Owner

Thank you!

@TWME-TW

Copy link
Copy Markdown
ContributorAuthor

Please make sure to review this PR carefully, because I don't really know what I'm doing.

@Tofaa2
Tofaa2 merged commit b8ec880 into Tofaa2:masterDec 1, 2025
2 checks passed
Sign up for freeto 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.

2 participants

@TWME-TW@Tofaa2
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Refactor SpigotEntityIdProvider ID supplier logic - #45

Merged
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1
Dec 1, 2025
Merged

Refactor SpigotEntityIdProvider ID supplier logic#45
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1

Conversation

@TWME-TW

@TWME-TWTWME-TW commented Nov 19, 2025

Copy link
Copy Markdown
Contributor

Refactor entity ID supplier detection logic to improve maintainability and clarity.

This pull request was written by AI. It currently fixes an issue I encountered in Spigot 1.21.10.

However, since I am not very familiar with reflection, I am not entirely sure about the contents of this PR. Therefore, please make sure to review it carefully to ensure that this PR meets the requirements.

Summary by CodeRabbit

  • Refactor
    • Optimized entity ID generation logic with enhanced support across multiple server versions to improve stability and compatibility.

Refactor entity ID supplier detection logic to improve maintainability and clarity.
@coderabbitai

coderabbitaiBot commented Nov 19, 2025

Copy link
Copy Markdown

Walkthrough

Refactored SpigotEntityIdProvider to improve ID-generation robustness by replacing direct reflection logic with dedicated helper methods that handle multiple entity ID storage mechanisms across different Minecraft and Paper versions.

Changes

Cohort / File(s)Summary
ID-Generation Strategy Refactoring
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java
Replaced monolithic reflection logic with modular helper methods: resolveAtomicSupplier() for 1.14+ AtomicInteger fields, resolveLegacySupplier() for legacy int fields, and getStaticFieldOfType() for generic field location. Added version-specific branching with Paper 1.16+ path preservation via UnsafeValues.nextEntityId. Introduced Modifier import for reflection.

Sequence Diagram

sequenceDiagram
participant Client
participant detectIdSupplier
participant resolveAtomicSupplier
participant resolveLegacySupplier
participant getStaticFieldOfType
Client->>detectIdSupplier: Request ID supplier
alt Paper 1.16+
detectIdSupplier->>detectIdSupplier: Use UnsafeValues.nextEntityId
else Minecraft 1.14+
detectIdSupplier->>resolveAtomicSupplier: Resolve AtomicInteger field
resolveAtomicSupplier->>getStaticFieldOfType: Locate AtomicInteger field
getStaticFieldOfType-->>resolveAtomicSupplier: Field located
resolveAtomicSupplier-->>detectIdSupplier: Increment supplier ready
else Legacy versions
detectIdSupplier->>resolveLegacySupplier: Resolve int field
resolveLegacySupplier->>getStaticFieldOfType: Locate int field
getStaticFieldOfType-->>resolveLegacySupplier: Field located
resolveLegacySupplier-->>detectIdSupplier: Read/increment supplier ready
end
detectIdSupplier-->>Client: ID supplier
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

  • Reflection logic complexity: Review the field-location strategy in getStaticFieldOfType() for correctness across type matching and fallback scanning
  • Version-specific branching: Verify conditional logic for Paper 1.16+ detection and proper delegation between atomic and legacy paths
  • Type safety: Ensure AtomicInteger and int field resolution validates types correctly before wrapping in suppliers
  • Backward compatibility: Confirm all legacy version paths (field names, access patterns) remain intact

Poem

🐰 A rabbit hopped through reflection's maze,
With fields to find through many days,
Now atomic paths and legacy lanes,
Flow smoothly through version chains,
Each ID springs forth with graceful ease! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 40.00% which is insufficient. The required threshold is 80.00%.You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately describes the main change: refactoring the ID supplier logic in SpigotEntityIdProvider with improved maintainability.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

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 (2)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (2)

69-76: Version‑aware supplier selection and helper split look sound

The refactored detectIdSupplier() flow (Paper fast‑path → 1.14+ atomic path → legacy path) plus resolveAtomicSupplier/resolveLegacySupplier is logically consistent and keeps behavior centralized while preserving a clear failure mode via IllegalStateException. The atomic path cleanly falls back to legacy when no suitable AtomicInteger is found.

If you want easier diagnostics on odd future versions, consider (optionally) adding a debug log when:

  • resolveAtomicSupplier returns null despite a 1.14+ version, and/or
  • resolveLegacySupplier throws because no legacy counter field was found.

This would make it much easier to understand reflection breakage on new Spigot/Paper releases without changing current behavior.

Also applies to: 78-112


153-169: getStaticFieldOfType helper improves robustness; watch first‑match fallback semantics

Centralizing the reflection into getStaticFieldOfType with:

  • type checks (desiredType.isAssignableFrom(field.getType())), and
  • a static‑modifier check,

is a solid improvement and should catch most NMS name changes automatically.

One thing to be aware of: the second loop returns the first static field of the requested type. If a future Entity class ever gains multiple static AtomicInteger or int fields, this might pick the wrong one. That’s probably acceptable given current NMS layouts, but if this ever becomes an issue, you could tighten the heuristic (e.g., filter by final, by name prefix, or by requiring uniqueness before accepting a match).

Also, the Javadoc above detectIdSupplier() still mentions only "entityCount"/"d"/"c" and not the newer aliases ("counter", "nextEntityId", "b"); updating that comment would better reflect the actual lookup behavior.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between df6fe0f and 7ba8d1b.

📒 Files selected for processing (1)
  • platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (3 hunks)
🔇 Additional comments (1)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (1)

3-20: Imports for reflection and Bukkit/Paper APIs look correct

The added Modifier import and the Bukkit / Paper / Platform imports align with the new helper and usage; no issues here.

@Tofaa2Tofaa2 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

LGTM!

@Tofaa2

Copy link
Copy Markdown
Owner

Thank you!

@TWME-TW

Copy link
Copy Markdown
ContributorAuthor

Please make sure to review this PR carefully, because I don't really know what I'm doing.

@Tofaa2
Tofaa2 merged commit b8ec880 into Tofaa2:masterDec 1, 2025
2 checks passed
Sign up for freeto 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.

2 participants

@TWME-TW@Tofaa2
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Refactor SpigotEntityIdProvider ID supplier logic - #45

Merged
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1
Dec 1, 2025
Merged

Refactor SpigotEntityIdProvider ID supplier logic#45
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1

Conversation

@TWME-TW

@TWME-TWTWME-TW commented Nov 19, 2025

Copy link
Copy Markdown
Contributor

Refactor entity ID supplier detection logic to improve maintainability and clarity.

This pull request was written by AI. It currently fixes an issue I encountered in Spigot 1.21.10.

However, since I am not very familiar with reflection, I am not entirely sure about the contents of this PR. Therefore, please make sure to review it carefully to ensure that this PR meets the requirements.

Summary by CodeRabbit

  • Refactor
    • Optimized entity ID generation logic with enhanced support across multiple server versions to improve stability and compatibility.

Refactor entity ID supplier detection logic to improve maintainability and clarity.
@coderabbitai

coderabbitaiBot commented Nov 19, 2025

Copy link
Copy Markdown

Walkthrough

Refactored SpigotEntityIdProvider to improve ID-generation robustness by replacing direct reflection logic with dedicated helper methods that handle multiple entity ID storage mechanisms across different Minecraft and Paper versions.

Changes

Cohort / File(s)Summary
ID-Generation Strategy Refactoring
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java
Replaced monolithic reflection logic with modular helper methods: resolveAtomicSupplier() for 1.14+ AtomicInteger fields, resolveLegacySupplier() for legacy int fields, and getStaticFieldOfType() for generic field location. Added version-specific branching with Paper 1.16+ path preservation via UnsafeValues.nextEntityId. Introduced Modifier import for reflection.

Sequence Diagram

sequenceDiagram
participant Client
participant detectIdSupplier
participant resolveAtomicSupplier
participant resolveLegacySupplier
participant getStaticFieldOfType
Client->>detectIdSupplier: Request ID supplier
alt Paper 1.16+
detectIdSupplier->>detectIdSupplier: Use UnsafeValues.nextEntityId
else Minecraft 1.14+
detectIdSupplier->>resolveAtomicSupplier: Resolve AtomicInteger field
resolveAtomicSupplier->>getStaticFieldOfType: Locate AtomicInteger field
getStaticFieldOfType-->>resolveAtomicSupplier: Field located
resolveAtomicSupplier-->>detectIdSupplier: Increment supplier ready
else Legacy versions
detectIdSupplier->>resolveLegacySupplier: Resolve int field
resolveLegacySupplier->>getStaticFieldOfType: Locate int field
getStaticFieldOfType-->>resolveLegacySupplier: Field located
resolveLegacySupplier-->>detectIdSupplier: Read/increment supplier ready
end
detectIdSupplier-->>Client: ID supplier
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

  • Reflection logic complexity: Review the field-location strategy in getStaticFieldOfType() for correctness across type matching and fallback scanning
  • Version-specific branching: Verify conditional logic for Paper 1.16+ detection and proper delegation between atomic and legacy paths
  • Type safety: Ensure AtomicInteger and int field resolution validates types correctly before wrapping in suppliers
  • Backward compatibility: Confirm all legacy version paths (field names, access patterns) remain intact

Poem

🐰 A rabbit hopped through reflection's maze,
With fields to find through many days,
Now atomic paths and legacy lanes,
Flow smoothly through version chains,
Each ID springs forth with graceful ease! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 40.00% which is insufficient. The required threshold is 80.00%.You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately describes the main change: refactoring the ID supplier logic in SpigotEntityIdProvider with improved maintainability.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

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 (2)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (2)

69-76: Version‑aware supplier selection and helper split look sound

The refactored detectIdSupplier() flow (Paper fast‑path → 1.14+ atomic path → legacy path) plus resolveAtomicSupplier/resolveLegacySupplier is logically consistent and keeps behavior centralized while preserving a clear failure mode via IllegalStateException. The atomic path cleanly falls back to legacy when no suitable AtomicInteger is found.

If you want easier diagnostics on odd future versions, consider (optionally) adding a debug log when:

  • resolveAtomicSupplier returns null despite a 1.14+ version, and/or
  • resolveLegacySupplier throws because no legacy counter field was found.

This would make it much easier to understand reflection breakage on new Spigot/Paper releases without changing current behavior.

Also applies to: 78-112


153-169: getStaticFieldOfType helper improves robustness; watch first‑match fallback semantics

Centralizing the reflection into getStaticFieldOfType with:

  • type checks (desiredType.isAssignableFrom(field.getType())), and
  • a static‑modifier check,

is a solid improvement and should catch most NMS name changes automatically.

One thing to be aware of: the second loop returns the first static field of the requested type. If a future Entity class ever gains multiple static AtomicInteger or int fields, this might pick the wrong one. That’s probably acceptable given current NMS layouts, but if this ever becomes an issue, you could tighten the heuristic (e.g., filter by final, by name prefix, or by requiring uniqueness before accepting a match).

Also, the Javadoc above detectIdSupplier() still mentions only "entityCount"/"d"/"c" and not the newer aliases ("counter", "nextEntityId", "b"); updating that comment would better reflect the actual lookup behavior.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between df6fe0f and 7ba8d1b.

📒 Files selected for processing (1)
  • platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (3 hunks)
🔇 Additional comments (1)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (1)

3-20: Imports for reflection and Bukkit/Paper APIs look correct

The added Modifier import and the Bukkit / Paper / Platform imports align with the new helper and usage; no issues here.

@Tofaa2Tofaa2 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

LGTM!

@Tofaa2

Copy link
Copy Markdown
Owner

Thank you!

@TWME-TW

Copy link
Copy Markdown
ContributorAuthor

Please make sure to review this PR carefully, because I don't really know what I'm doing.

@Tofaa2
Tofaa2 merged commit b8ec880 into Tofaa2:masterDec 1, 2025
2 checks passed
Sign up for freeto 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.

2 participants

@TWME-TW@Tofaa2
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

Refactor SpigotEntityIdProvider ID supplier logic - #45

Merged
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1
Dec 1, 2025
Merged

Refactor SpigotEntityIdProvider ID supplier logic#45
Tofaa2 merged 1 commit into
Tofaa2:masterfrom
TWME-TW:patch-1

Conversation

@TWME-TW

@TWME-TWTWME-TW commented Nov 19, 2025

Copy link
Copy Markdown
Contributor

Refactor entity ID supplier detection logic to improve maintainability and clarity.

This pull request was written by AI. It currently fixes an issue I encountered in Spigot 1.21.10.

However, since I am not very familiar with reflection, I am not entirely sure about the contents of this PR. Therefore, please make sure to review it carefully to ensure that this PR meets the requirements.

Summary by CodeRabbit

  • Refactor
    • Optimized entity ID generation logic with enhanced support across multiple server versions to improve stability and compatibility.

Refactor entity ID supplier detection logic to improve maintainability and clarity.
@coderabbitai

coderabbitaiBot commented Nov 19, 2025

Copy link
Copy Markdown

Walkthrough

Refactored SpigotEntityIdProvider to improve ID-generation robustness by replacing direct reflection logic with dedicated helper methods that handle multiple entity ID storage mechanisms across different Minecraft and Paper versions.

Changes

Cohort / File(s)Summary
ID-Generation Strategy Refactoring
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java
Replaced monolithic reflection logic with modular helper methods: resolveAtomicSupplier() for 1.14+ AtomicInteger fields, resolveLegacySupplier() for legacy int fields, and getStaticFieldOfType() for generic field location. Added version-specific branching with Paper 1.16+ path preservation via UnsafeValues.nextEntityId. Introduced Modifier import for reflection.

Sequence Diagram

sequenceDiagram
participant Client
participant detectIdSupplier
participant resolveAtomicSupplier
participant resolveLegacySupplier
participant getStaticFieldOfType
Client->>detectIdSupplier: Request ID supplier
alt Paper 1.16+
detectIdSupplier->>detectIdSupplier: Use UnsafeValues.nextEntityId
else Minecraft 1.14+
detectIdSupplier->>resolveAtomicSupplier: Resolve AtomicInteger field
resolveAtomicSupplier->>getStaticFieldOfType: Locate AtomicInteger field
getStaticFieldOfType-->>resolveAtomicSupplier: Field located
resolveAtomicSupplier-->>detectIdSupplier: Increment supplier ready
else Legacy versions
detectIdSupplier->>resolveLegacySupplier: Resolve int field
resolveLegacySupplier->>getStaticFieldOfType: Locate int field
getStaticFieldOfType-->>resolveLegacySupplier: Field located
resolveLegacySupplier-->>detectIdSupplier: Read/increment supplier ready
end
detectIdSupplier-->>Client: ID supplier
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

  • Reflection logic complexity: Review the field-location strategy in getStaticFieldOfType() for correctness across type matching and fallback scanning
  • Version-specific branching: Verify conditional logic for Paper 1.16+ detection and proper delegation between atomic and legacy paths
  • Type safety: Ensure AtomicInteger and int field resolution validates types correctly before wrapping in suppliers
  • Backward compatibility: Confirm all legacy version paths (field names, access patterns) remain intact

Poem

🐰 A rabbit hopped through reflection's maze,
With fields to find through many days,
Now atomic paths and legacy lanes,
Flow smoothly through version chains,
Each ID springs forth with graceful ease! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 40.00% which is insufficient. The required threshold is 80.00%.You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately describes the main change: refactoring the ID supplier logic in SpigotEntityIdProvider with improved maintainability.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

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 (2)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (2)

69-76: Version‑aware supplier selection and helper split look sound

The refactored detectIdSupplier() flow (Paper fast‑path → 1.14+ atomic path → legacy path) plus resolveAtomicSupplier/resolveLegacySupplier is logically consistent and keeps behavior centralized while preserving a clear failure mode via IllegalStateException. The atomic path cleanly falls back to legacy when no suitable AtomicInteger is found.

If you want easier diagnostics on odd future versions, consider (optionally) adding a debug log when:

  • resolveAtomicSupplier returns null despite a 1.14+ version, and/or
  • resolveLegacySupplier throws because no legacy counter field was found.

This would make it much easier to understand reflection breakage on new Spigot/Paper releases without changing current behavior.

Also applies to: 78-112


153-169: getStaticFieldOfType helper improves robustness; watch first‑match fallback semantics

Centralizing the reflection into getStaticFieldOfType with:

  • type checks (desiredType.isAssignableFrom(field.getType())), and
  • a static‑modifier check,

is a solid improvement and should catch most NMS name changes automatically.

One thing to be aware of: the second loop returns the first static field of the requested type. If a future Entity class ever gains multiple static AtomicInteger or int fields, this might pick the wrong one. That’s probably acceptable given current NMS layouts, but if this ever becomes an issue, you could tighten the heuristic (e.g., filter by final, by name prefix, or by requiring uniqueness before accepting a match).

Also, the Javadoc above detectIdSupplier() still mentions only "entityCount"/"d"/"c" and not the newer aliases ("counter", "nextEntityId", "b"); updating that comment would better reflect the actual lookup behavior.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between df6fe0f and 7ba8d1b.

📒 Files selected for processing (1)
  • platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (3 hunks)
🔇 Additional comments (1)
platforms/spigot/src/main/java/me/tofaa/entitylib/spigot/SpigotEntityIdProvider.java (1)

3-20: Imports for reflection and Bukkit/Paper APIs look correct

The added Modifier import and the Bukkit / Paper / Platform imports align with the new helper and usage; no issues here.

@Tofaa2Tofaa2 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

LGTM!

@Tofaa2

Copy link
Copy Markdown
Owner

Thank you!

@TWME-TW

Copy link
Copy Markdown
ContributorAuthor

Please make sure to review this PR carefully, because I don't really know what I'm doing.

@Tofaa2
Tofaa2 merged commit b8ec880 into Tofaa2:masterDec 1, 2025
2 checks passed
Sign up for freeto 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.

2 participants

@TWME-TW@Tofaa2