Jump to content

Ore Won't Generate


Noxxous

Recommended Posts

Hello, I am currently trying to get custom ore generation to work and I have tried to imitate every last bit of code from the tutorials, I've edited and I have even tried using an older version of Forge but it still isn't working. I have spent hours working on this for nothing

 

	public Lightsaber_Main() {
		IEventBus bus = FMLJavaModLoadingContext.get().getModEventBus();
		
		itemInit.Items.register(bus);
		BlockInit.Blocks.register(bus);
		
		ModSounds.register(bus);

		configuredFeatureInit.CONFIGURED_FEATURES.register(bus);
		
		PlacedFeaturesInit.Placed_Feature.register(bus);
		
		MinecraftForge.EVENT_BUS.register(this);
		
	}
public class configuredFeatureInit {

	private static final RuleTest END_STONE = new BlockMatchTest(Blocks.STONE);
	   
	public static final DeferredRegister<ConfiguredFeature<?, ?>> CONFIGURED_FEATURES 
		= DeferredRegister.create(Registry.CONFIGURED_FEATURE_REGISTRY, Lightsaber_Main.MOD_ID);

	public static final Supplier<List<OreConfiguration.TargetBlockState>> END_KYBER_CRYSTAL_ORE 
		= Suppliers.memoize(() -> List.of(
				OreConfiguration.target(OreFeatures.STONE_ORE_REPLACEABLES,
				BlockInit.kyber_crystal_ore.get().defaultBlockState()),
				
				OreConfiguration.target(OreFeatures.DEEPSLATE_ORE_REPLACEABLES,
						BlockInit.kyber_crystal_ore.get().defaultBlockState())
				));
	
	public static final RegistryObject<ConfiguredFeature<?, ?>> END_ORE_GENERATION 
		= CONFIGURED_FEATURES.register("kyber_crystal_ore", 
				() -> new ConfiguredFeature<>(Feature.ORE, 
						new OreConfiguration(END_KYBER_CRYSTAL_ORE.get(), 14)));
	
}
public class PlacedFeaturesInit {

	public static final DeferredRegister<PlacedFeature> Placed_Feature = DeferredRegister.create(Registry.PLACED_FEATURE_REGISTRY, Lightsaber_Main.MOD_ID);

	public static final RegistryObject<PlacedFeature> END_ORE = Placed_Feature.register("kyber_crystal_ore_placed",
		() -> new PlacedFeature(configuredFeatureInit.END_ORE_GENERATION.getHolder().get(), 
			commonOrePlacement(50,
				HeightRangePlacement.uniform(
					VerticalAnchor.aboveBottom(-64),
					VerticalAnchor.belowTop(319)
				)
			)
		)
	);
	
	
	public static List<PlacementModifier> commonOrePlacement(int countPerChunk, PlacementModifier height) {
		return orePlacement(CountPlacement.of(countPerChunk), height);
		
	}

	public static List<PlacementModifier> orePlacement(PlacementModifier count, PlacementModifier height) {
		return List.of(count, InSquarePlacement.spread(), BiomeFilter.biome());
	}
	
	public static List<PlacementModifier> rareOrePlacement(int count, PlacementModifier height) {
		return orePlacement(RarityFilter.onAverageOnceEvery(count), height);
	}
}

 

add_kyber_crystal_ore.json:

{
	"type": "forge:add_features",
	"biomes": "#minecraft:is_overworld",
	"features": "lightsabermod:kyber_crystal_ore_placed",
	"step": "underground_ores"
}

 

Link to comment
Share on other sites

Show the full path of your add_kyber_crystal_ore.json

It should be something like src/main/resources/data/lightsabermod/forge/biome_modifier/add_kyber_crystal_ore.json

https://forge.gemwire.uk/wiki/Biome_Modifiers#Biome_Modifier_JSONs

 

Also by setting the maximum height to 319 most of the generation attempts will fail. 

Sea level is at 64 so you will be trying to generate in the "air" which doesn't match your TargetBlockStates.

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Link to comment
Share on other sites

I just copied and pasted from a tutorial and it worked. It was probably because of the rule test variable, the spawn rate being too high and the height difference. I think that the spawn rate's maximum is 50 but I'm not going to do anything else so that I don't become burnt out

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Done, it still crashed. New log https://paste.ee/p/kYv6e
    • I am migrating a mod from 1.16.5 to 1.20.2 The version for 1.16.5 can be found here https://github.com/beothorn/automataCraft For the block called automata_start, it uses TileEntities and has blockstates, model/block and textures on json files. This is currently working fine on 1.16.5 https://github.com/beothorn/automataCraft/tree/master/src/main/resources/assets/automata For 1.20.2 I migrated the logic from TileEntities to BlockEntity. The mod is working fine. All blocks and Items are working with the correct textures except for the textures for each state of the automata_start block. No changes where made to the json files. This is the branch I am working on (there were some refactorings, but all is basically the same): https://github.com/beothorn/automataCraft/tree/1_20/src/main/resources/assets/automata The only difference I can think that may be related is that i had to implement createBlockStateDefinition on the BaseEntityBlock: https://github.com/beothorn/automataCraft/blob/1_20/src/main/java/br/com/isageek/automata/automata/AutomataStartBlock.java#L43 This is driving me crazy. I know the jsons are being loaded as I put a breakpoint at `net.minecraft.client.resources.model.ModelBakery#loadModel` and I can see BlockModelDefinition.fromJsonElement being called with automata_start. I also printed the state from the arguments of the tick function call and they look correct (https://github.com/beothorn/automataCraft/blob/1_20/src/main/java/br/com/isageek/automata/automata/Ticker.java#L32 ): blockState Block{automata:automata_start}[state=loadreplaceables] In game, all I see is the no textures. I think it is weird it is not the "missing texture" texture so I think it may be related to the material, but I had no success tweaking it (https://github.com/beothorn/automataCraft/blob/1_20/src/main/java/br/com/isageek/automata/automata/AutomataStartBlock.java#L37).   public static final Property<AutomataStartState> state = EnumProperty.create("state", AutomataStartState.class); private final AtomicReference<RegistryObject<BlockEntityType<?>>> blockEntityType; private final Map<String, RegistryObject<Block>> registeredBlocks; public AutomataStartBlock( final AtomicReference<RegistryObject<BlockEntityType<?>>> blockEntityType, final Map<String, RegistryObject<Block>> registeredBlocks ) { super(BlockBehaviour.Properties.of().mapColor(MapColor.STONE).strength(1.5F, 6.0F)); this.blockEntityType = blockEntityType; this.registeredBlocks = registeredBlocks; this.registerDefaultState(this.getStateDefinition().any().setValue(state, AutomataStartState.LOAD_REPLACEABLES)); } @Override protected void createBlockStateDefinition(StateDefinition.Builder<Block, BlockState> stateBuilder) { stateBuilder.add(state); }     So my cry for help is, anyone has any ideas? Is there a way to easily debug this, for example somewhere where I can list the textures for a given state, or make sure this is loaded?   Thanks in advance for the hints
    • FAILURE: Build failed with an exception. * What went wrong: A problem occurred configuring root project 'forge-1.8.9-11.15.1.2318-1.8.9-mdk'. > Could not resolve all dependencies for configuration ':classpath'. > Could not resolve net.minecraftforge.gradle:ForgeGradle:2.1-SNAPSHOT. Required by: :forge-1.8.9-11.15.1.2318-1.8.9-mdk:unspecified > Could not resolve net.minecraftforge.gradle:ForgeGradle:2.1-SNAPSHOT. > Unable to load Maven meta-data from https://jcenter.bintray.com/net/minecraftforge/gradle/ForgeGradle/2.1-SNAPSHOT/maven-metadata.xml. > Could not GET 'https://jcenter.bintray.com/net/minecraftforge/gradle/ForgeGradle/2.1-SNAPSHOT/maven-metadata.xml'. > peer not authenticated > Could not resolve net.minecraftforge.gradle:ForgeGradle:2.1-SNAPSHOT. > Unable to load Maven meta-data from http://files.minecraftforge.net/maven/net/minecraftforge/gradle/ForgeGradle/2.1-SNAPSHOT/maven-metadata.xml. > Could not GET 'http://files.minecraftforge.net/maven/net/minecraftforge/gradle/ForgeGradle/2.1-SNAPSHOT/maven-metadata.xml'. > peer not authenticated * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. BUILD FAILED Total time: 2.78 secs This is the error I got. Any help would be appreciated!
    • Greetings, ladies and gentlemen. I know firsthand how distressing it can be to lose Bitcoin (BTC) to a phony online trading site. Thank God, when I became a victim of internet scammers, I came across genuine reviews of Captain WebGenesis. The Experts reviews on google were generally positive and reliable. Captain WebGenesis, a licensed cryptocurrency expert, helps persons who have fallen prey to investment scams recover their stolen funds. Captain WebGenesis miraculously recovered my wallet and all of my Bitcoins in roughly 48 hours. Captain WebGenesis is tried, trusted, and accessible to all victims of Bitcoin fraud. The service charge was pricey, but it was well worth it. If you need his help, get in touch with the Expert. SMS / Call; +1 (701)314-2729 Email; (captainwebgenesis(@)hackermail.com) Homepage; captainwebgenesis.com Salutations, Captain WebGenesis.
    • The mod causing the problem was (supplementaries-1.20-2.8.10). The solution I found is deleting it.
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.