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

doesnt work with mcmmo #25

Open
dev-Blaze opened this issue Apr 21, 2020 · 1 comment
Open

doesnt work with mcmmo #25

dev-Blaze opened this issue Apr 21, 2020 · 1 comment

Comments

@dev-Blaze
Copy link

in mcmmo the gold block is used as a salvage anvil, i think it messes with this datapack, is there anyway for this to work with a separate block instead?

@isaaclepes
Copy link

isaaclepes commented Oct 6, 2020

As far as I can tell, this datapack does not really do anything that should conflict with the gold block. It has a check in it that just looks at the 2 blocks below the item entity, but it makes no changes to Gold Block behavior
it looks like this:

execute as @e[type=item] at @s if block ~ ~-1 ~ minecraft:lapis_block if block ~ ~-2 ~ minecraft:gold_block run function mss:sort

Execute if block below entity is lapis but only if block 2 spaces below is gold.

Usually conflicts happen when datapacks:
Edit the same thing as another datapack
Use the same namespace / tags / functions / scoreboards

Everything that is changed/added by this pack has "mss" in it's name, except the tick function. It uses scoreboard values which were borrowed from Xisumavoid. If these scoreboard names are verbatim and the other datapack uses the same, it could mess with timing for both datapacks.

For the most part, this data pack is just a collection of execute commands, the only part that isn't would be within main:init and main:tick

To work with a separate block, just edit the second.mcfunction file and change gold_block for whatever you desire.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants