[BUG]: MMRL confuses ReZygisk with ZygiskNext

[Keyaku]

Version

1.0.0-rc.1

Modules

ZygiskAssistant by snake-4 version 213

Description

The Magisk module manager MMRL is confusing ReZygisk with Zygisk Next. I'm guessing it's because MMRL uses the shoddy method of looking up its ID (and the module.prop's id value shows zygisksu) when no repo is available, but haven't checked.
It marks the module as updatable which, upon checking the changelog, it's clear it points to the latest Zygisk Next package.

Clearing MMRL's storage (since this app is prone to issues with its cache) only unmarked the module from blacklist; not sure if this is relevant.

Steps to reproduce

1. Have root with Apatch.
2. Have MMRL installed (and obviously ReZygisk).
3. In Modules tab, check if ReZygisk presents an enabled "Update" button.
4. Go to Zygisk Next's package page from Googler's repo.
5. Check if the buttons show "Remove" and "Update".

Logs

No response

Confirmations

• My environment meets the minimum requirements.
• I have verified that this is not a duplicate issue.

Code of Conduct

• I agree to follow this project's Code of Conduct

[Keyaku]

By the way, the Modules section of your GitHub issue report lacks clarity; is it Zygisk-specific modules, or any and all Magisk modules?

[ThePedroo]

Can depend from the case but unless all modules information might be relevant, only Zygisk ones.

As part of that issue, we plan to eventually change the module id to avoid conflicts like that one, but in the meanwhile, while we fix other more important things, nothing can be done.

[Keyaku]

No worries, it is indeed a rather minor issue, and very easy to avoid.

[DerGoogler]

That is not a bug. That is because the modules using the same module ID.

[Keyaku]

That is not a bug. That is because the modules using the same module ID.

Yep, that is what I mentioned. The "bug" (issue, more like) is on this module.