Fix race condition in Purifier enchantment blacklist game tests

[Copilot]

• Add enchantmentIdBlacklist config to BlockEntityPurifierConfig using @ConfigurableProperty
• Modify DisenchantPurifyAction to filter blacklisted enchantments
• Modify ToolBadEnchantPurifyAction to skip blacklisted curses
• Add GameTestsPurifier with 3 game tests:
  • testPurifierDisenchant: normal disenchanting works
  • testPurifierCurseRemoval: normal curse removal works
  • testPurifierEnchantmentBlacklist: both blacklist scenarios run in isolated batch = "purifier_blacklist_0" to avoid concurrent interference with other tests that use the same enchantments

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Enchantment ID Blacklist for the Purifier</issue_title>
<issue_description>

Issue type:

• ➕ Feature request

---

Short description:

The Purifier can disenchant tools and remove curses as well.
This is pretty powerful, depending on the modpack.
I think it would be nice to have a blacklist for enchantments that the purifier can effect or not.
Proposed format:

[machine]

	[machine.purifier]
		#Item that can not be disenchanted. Regular expressions are allowed.
		disenchantBlacklist = ["tetra:.*"]
		#Enchantments to be disqualified from disenchantment, or curses disallowed from purification.
		enchantmentIdBlacklist = ["minecraft:vanishing_curse","evilcraft:vengeance"]

Potentially disenchantBlacklist could be renamed to disambiguate.
Might be some work, but if it happens, I'd suggest "itemBlacklist"

</issue_description>

<agent_instructions>Please implement this, the proposed format suggestion looks good.
Config properties can be added in BlockEntityPurifierConfig using @ConfigurableProperty.
Add game tests to validate the functionality.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@rubensworks

Thanks for the suggestion!

• Fixes Enchantment ID Blacklist for the Purifier #855

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[coveralls]

Pull Request Test Coverage Report for Build 23374137913

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 7 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+1.0%) to 28.511%

---

Files with Coverage Reduction	New Missed Lines	%
org/cyclops/evilcraft/blockentity/tickaction/purifier/ToolBadEnchantPurifyAction.java	2	81.82%
org/cyclops/evilcraft/blockentity/tickaction/purifier/DisenchantPurifyAction.java	5	75.27%

Totals
Change from base Build 22867788481:	1.0%
Covered Lines:	5018
Relevant Lines:	15065

---

💛 - Coveralls

[rubensworks]

@copilot one gametest fails. Please fix, and run it yourself after fixing to ensure it works.

[Copilot]

@copilot one gametest fails. Please fix, and run it yourself after fixing to ensure it works.

Fixed in fb59962. The root cause was testPurifierEnchantmentBlacklist running concurrently (same default batch) with testPurifierDisenchant. The blacklist test set BlockPurifierConfig.enchantmentIdBlacklist = ["minecraft:sharpness", ...] globally, which prevented the purifier in testPurifierDisenchant from ever removing sharpness — causing that test to time out and fail.

The fix adds batch = "purifier_blacklist_0" to testPurifierEnchantmentBlacklist, following the same pattern used in GameTestsVengeanceSpirits. Tests in different batches run sequentially, so the blacklist test now runs in complete isolation from the other purifier tests.