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

[Bug Report]: FTB Ultimine cannot mine Oh The Biomes We've Gone Rocky Stone when shaped consistently #441

Open
GreatestFool opened this issue Mar 6, 2025 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@GreatestFool
Copy link

GreatestFool commented Mar 6, 2025

Modpack Version

1.17.1

Describe your issue.

Vein mining Rocky Stone from the mod Oh The Biomes We've Gone with FTB Ultimine only works if the starting block is a Rocky Stone, from what I've gathered. Testing by mining a Small Tunnel by starting on any block that isn't Rocky Stone, leads to them being left behind. It might be that any Oh The Biomes We've Gone can be the starting block, but I have not tested this.

It worked fairly consistently when I was testing, but I vaguely remember it not working a few times in actual practical play. Should probably be tested further. This was tested on a clean install of 1.15.2 and 1.17.1 without any world set up. It shouldn't be affected by anything from a prior world like old configuration files, etc., etc.

I'm assuming this is some sort of mod incompatibility or bug in some way. I could not find anything being blacklisted in the defaultconfigs nor the world/serverconfig for FTB Ultimine. Also checked in-game, via /ftbultimine serverconfig, which matches the server configuration.

The block has an ID of biomeswevegone:rocky_stone. Additionally, it has these tags:

  • '#actuallyadditions:mineable/drill'
  • '#artifacts:mineable/digging_claws'
  • '#c:mineable/paxel'
  • '#minecraft:overworld_carver_replaceables'
  • '#twilightforest:druid_projectile_replaceable'
  • '#twilightforest:carver_replaceables'
  • '#actuallyadditions:mineable/aio'
  • '#minecraft:mineable/pickaxe'
  • '#twilightforest:mineable_with_block_and_chain'

Shapeless does have everything selected, but I've tested by adding the block, and restarting in-between. I cannot see any errors in the server logs, and the blocks are selected perfectly fine.

I haven't really kept on top of Minecraft's modding scene for a long while, and may be missing something otherwise obvious.

Have you modified the modpack?

No

Did the issue happen in singleplayer or on a server?

Server

@GreatestFool GreatestFool added the bug Something isn't working label Mar 6, 2025
@Linguardium
Copy link

Linguardium commented Mar 6, 2025

FTB Ultimine is not configured to merge this into the stone mining

"minecraft:base_stone_overworld"

You could add it to this tag but be aware that it will cause ores to spawn within Rocky Stone which i believe is not the intent of BWG

@GreatestFool
Copy link
Author

I appreciate the help, but that is incorrect, as far as I understand. The issue is not that the block cannot be targeted by FTB Ultimine, it's that it isn't being applied consistently. Additionally, the mod treats shaped and shapeless mining mode different, and has different filters for the two. The configuration file you're referencing is for the shapeless mining mode, not the shaped one, which is what this issue is about. Though I wouldn't be surprised if shapeless has the same problem as shaped. The shapeless filter is literally accepting everything using a wildcard operator, which means it should work, yet it only does so when starting from a Rocky Stone.

This is, ironically, pretty normal behavior. If not for a little something. FTB Ultimine's server configuration is only meant to apply when "[...], any blocks in these tags which share a block tag with the original block are valid targets for Ultimining." Since it's using a wildcard operator, it means that so long as the blocks being vein mined share a tag, they are valid targets—the way I understand it, at least—And, lo and behold, both Rocky Stone and regular vanilla Stone (and Andesite since it's in the area) share #minecraft:mineable/pickaxe, yet it still only works when the starting block is a Rocky Stone, not the other way around. Even though this should, according to FTB Ultimine's own documentation, should be valid targets and should be "ultimined."

This is why I suspect it's an incompatibility or bug. Yet I cannot say for certain, since I do not know of, nor intend to know of all parts that make up the configuration of this modpack; I'm just a player, after all. But I'm willing to try to be detailed, if it means others will benefit from changes in either the modpack or mod(s) too.

Here's an example of the generated server configuration file, btw.

# These tags will be considered the same block when checking for blocks to Ultimine in shapeless mining mode
# Default: ["minecraft:base_stone_overworld", "c:*_ores", "forge:ores/*"]
merge_tags: [
	"minecraft:base_stone_overworld"
	"c:ores/*"
]

# These tags will be considered the same block when checking for blocks to Ultimine in shaped mining modes
# Default: ["*"]
merge_tags_shaped: ["*"]

I hope this helps explain what I meant in the first issue post, if I was unclear.

@Linguardium
Copy link

Linguardium commented Mar 8, 2025

oh, you are correct, i misread "shaped" as "shapeless". i appreciate the correction!

Have you reported this to the FTB team?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants