Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"No SRG name found" when using "Copy / Paste Special... > AT Entry" #2371

Open
octylFractal opened this issue Sep 11, 2024 · 1 comment · May be fixed by #2365
Open

"No SRG name found" when using "Copy / Paste Special... > AT Entry" #2371

octylFractal opened this issue Sep 11, 2024 · 1 comment · May be fixed by #2365
Labels
platform: neoforge status: accepted This is a high-priority feature or a reproduced bug type: bug

Comments

@octylFractal
Copy link

Minecraft Development for IntelliJ plugin version

2024.2-1.8.1

IntelliJ version

2024.2.1 / 242.21829.142

Operating System

Linux 6.10.9-arch1-1

Target platform

No response

Description of the bug

Target platform: NeoForge, it wasn't in the drop down.

When I use the "Copy / Paste Special... > AT Entry" context action on any MC code from NeoForge, nothing is copied and "No SRG name found" is shown. NeoForge 1.21 does not use SRG names at all in ATs, so this makes sense. The entry should be entirely based off of the Mojang mappings.

This can be reproduced easily using any NeoForge project, adding:

        ChunkHolder holder = null;
        holder.changedBlocksPerSection[0] = null;

and trying to copy an AT entry for changedBlocksPerSection.

@RedNesto
Copy link
Member

This is implemented in #2365

@RedNesto RedNesto added platform: neoforge status: accepted This is a high-priority feature or a reproduced bug and removed status: unverified Needs triage labels Sep 11, 2024
@RedNesto RedNesto linked a pull request Sep 30, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform: neoforge status: accepted This is a high-priority feature or a reproduced bug type: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants