Jump to content

[1.15.2] Why is my Common config being read from the physical client over the physical server?


squidlex

Recommended Posts

I'm trying to setup a common config that is read from the physical server over the physical client, however the physical client is taking presedence over it.

Why is this happening and how can I fix it?

 

Config:

@EventBusSubscriber(modid = Dodge.MODID, bus = EventBusSubscriber.Bus.MOD)
public final class ConfigHandler {

	public static class Common {

		public final ForgeConfigSpec.DoubleValue dodgePower;
		public final ForgeConfigSpec.IntValue hungerRequirement;
		public final ForgeConfigSpec.BooleanValue allowDodgeWhileAirborne;

		public final ForgeConfigSpec.BooleanValue enableCooldown;
		public final ForgeConfigSpec.IntValue cooldownLength;

		public final ForgeConfigSpec.BooleanValue displayParticles;
		public final ForgeConfigSpec.BooleanValue fancyParticles;

		public Common(ForgeConfigSpec.Builder builder) {

			// BALANCE
			dodgePower = builder
					.comment("How powerful each player's dodge is. Defaults at 1 which is just under 3 blocks.")
					.defineInRange("balance.power", 1, 0, Double.MAX_VALUE);
			hungerRequirement = builder.comment(
					"How many half drumsticks the player needs to dodge. Set this to -1 to disable this feature. By default it's the same as sprinting, 6.")
					.defineInRange("balance.hungerRequirement", 6, -1, 20);
			allowDodgeWhileAirborne = builder.comment(
					"Set this to true to allow the player to dodge whilst in midair. Note the player always has this ability in creative mode.")
					.define("balance.allowDodgeWhileAirborne", false);

			// COOLDOWN
			enableCooldown = builder.comment("Set this to false to disable the cooldown bar completely.")
					.define("cooldown.enabled", true);
			cooldownLength = builder
					.comment("How long the dodge takes to cooldown in (roughly) seconds. This defaults to 4.")
					.defineInRange("cooldown.duration", 3, 1, Integer.MAX_VALUE);

			// PARTICLES
			displayParticles = builder
					.comment("Set this to false to disable the particles emitted when a player dodges")
					.define("particles.enableParticles", true);
			fancyParticles = builder.comment(
					"Set this to true to enable fancy particles, many prefer the old particles so that is now the default.")
					.define("particles.fancy", false);
		}
	}

	public static final Common COMMON;
	public static final ForgeConfigSpec COMMON_SPEC;
	static {
		final Pair<Common, ForgeConfigSpec> specPair = new ForgeConfigSpec.Builder().configure(Common::new);
		COMMON_SPEC = specPair.getRight();
		COMMON = specPair.getLeft();
	}

	// Bakers
	@SubscribeEvent
	public static void onModConfigEvent(final ModConfig.ModConfigEvent configEvent) {
		if (configEvent.getConfig().getSpec() == ConfigHandler.COMMON_SPEC) {
			bakeCommonConfig();
		}
	}

	// Common
	public static double dodgePower;
	public static int hungerRequirement, cooldownLength;
	public static boolean allowDodgeWhileAirborne, enableCooldown, displayParticles, fancyParticles;

	public static void bakeCommonConfig() {
		dodgePower = COMMON.dodgePower.get();
		hungerRequirement = COMMON.hungerRequirement.get();
		cooldownLength = COMMON.cooldownLength.get() * 20;
		allowDodgeWhileAirborne = COMMON.allowDodgeWhileAirborne.get();
		enableCooldown = COMMON.enableCooldown.get();
		displayParticles = COMMON.displayParticles.get();
		fancyParticles = COMMON.fancyParticles.get();
	}
}

 

Where it is used:

public class DodgeEvents {
	
	@SubscribeEvent
	public void onKeyPressed(InputEvent.KeyInputEvent event) {

		if (Dodge.DodgeClient.DODGE_KEY.isKeyDown() && DodgeGui.len <= 0 && spamPreventer >= 12) {
			if (player.isCreative() || player.isSpectator() || player.onGround
					|| ConfigHandler.allowDodgeWhileAirborne) {
          	//DO STUFF
          }
        }
      }

 

How it is called in my main class:

public Dodge() {
		
		ModLoadingContext.get().registerConfig(ModConfig.Type.COMMON, ConfigHandler.COMMON_SPEC);
		
		DistExecutor.runWhenOn(Dist.CLIENT, () -> () -> {
			MinecraftForge.EVENT_BUS.register(new DodgeEvents());
}

 

I think it has something to do with my DistExecutor, is there any workaround for this?

Link to comment
Share on other sites

3 minutes ago, ChampionAsh5357 said:

Note: InputEvent is client side only. So, your client config takes precedent. Use a packet to send over the server value and store it in a variable.

Oh I see, thank you! Would I send over my server values straight from my config or from the event itself?

Link to comment
Share on other sites

20 minutes ago, ChampionAsh5357 said:

From an event since they could be subject to change whenever the config is reloaded.

Ah, thank you, do you have any example source code of this? I've got a PacketHandler setup but I'm not sure how I'd send a message from the server, rather than from the client.

Link to comment
Share on other sites

3 hours ago, ChampionAsh5357 said:

NETWORK_INSTANCE.send(PacketDistributor.ALL.noArg(), NEW_PACKET_INSTANCE);

 

Thanks for all your help, when I use that in my KeyInputEvent I get a crash. I don't want to bother you any more as it's unrelated to the OT so I've started a new topic asking for more information on how Networks work, thank you for explaining where I was going wrong!

Link to comment
Share on other sites

3 minutes ago, ChampionAsh5357 said:

Ok then. For quick reference though, KeyInputEvent is client side, so calling a packet to be sent to the client side from the server side on the client side doesn't actually make sense.

Oh I see thanks for explaining that one, what event should I call it in?

Link to comment
Share on other sites

Assuming that the values are loaded when you call bakeCommonConfig, call it directly afterwards. Make sure to check that you are on the logical server and not the client.

 

If you cannot check if its the logical server, use one of the FMLServerStarting events to do it instead.

Edited by ChampionAsh5357
Link to comment
Share on other sites

20 hours ago, ChampionAsh5357 said:

Assuming that the values are loaded when you call bakeCommonConfig, call it directly afterwards. Make sure to check that you are on the logical server and not the client.

 

If you cannot check if its the logical server, use one of the FMLServerStarting events to do it instead.

Thank you so much for all your help, I finally got it to work and I really appreciate the help given.

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

    • I'm working in the forge mdk for 1.20.2 and using Terrablender (version 3.2.0.11) to create a custom biome. The biome itself works and generates just fine, but I need to create a custom tag for it in order to have a very specific structures generate in that biome and ONLY that biome. That's when the problem comes in: I've created a ModBiomeTagGenerator class that extends BiomeTagGenerator from the vanilla code, and the same way the vanilla BiomeTagGenerator assigns tags to biomes, I'm trying to assign my custom tag to my custom biome so I can use it in a has_structure json. However, when I do this and try to runData, an error pops up: "Couldn't define tag decayingplanetmod:is_abandoned_city as it is missing following references: decayingplanetmod:abandoned_city." After experimenting, I found that I can add my tag "is_abandoned_city" to other vanilla biomes, but I can't add vanilla tags or ANY tags to my custom biome, abandoned_city, so it's definitely a problem with the custom biome itself, despite the fact that the biome generates in-game just fine. I've included the code that defines my biome, my biome tags, and assigns my tag to my biome. I've scoured online for similar problems and found very few-- the ones I did find had no concrete solutions, just "it suddenly started working" or "I updated to another version and it works now," which is very vague, as they don't specify what they're updating or how. Nothing seems to work so far. Faulty code: https://paste.ee/p/79my3 Any input is appreciated.
    • ASIABET adalah pilihan terbaik bagi Anda yang mencari slot gacor hari ini dengan server Rusia dan jackpot menggiurkan. Berikut adalah beberapa alasan mengapa Anda harus memilih ASIABET: Slot Gacor Hari Ini Kami menyajikan koleksi slot gacor terbaik yang diperbarui setiap hari. Dengan fitur-fitur unggulan dan peluang kemenangan yang tinggi, Anda akan merasakan pengalaman bermain yang tak terlupakan setiap kali Anda memutar gulungan. Server Rusia yang Handal Kami menggunakan server Rusia yang handal dan stabil untuk memastikan kelancaran dan keadilan dalam setiap putaran permainan. Anda dapat bermain dengan nyaman tanpa khawatir tentang gangguan atau lag. Jackpot Menggiurkan Nikmati kesempatan untuk memenangkan jackpot menggiurkan yang dapat mengubah hidup Anda secara instan. Dengan hadiah-hadiah besar yang ditawarkan, setiap putaran permainan bisa menjadi peluang untuk meraih keberuntungan besar.
    • Sonic77 adalah pilihan tepat bagi Anda yang menginginkan pengalaman bermain slot yang unggul dengan akun pro Swiss terbaik. Berikut adalah beberapa alasan mengapa Anda harus memilih Sonic77: Slot Gacor Terbaik Kami menyajikan koleksi slot gacor terbaik dari provider terkemuka. Dengan fitur-fitur unggulan dan peluang kemenangan yang tinggi, Anda akan merasakan pengalaman bermain yang tak terlupakan. Akun Pro Swiss Berkualitas Kami menawarkan akun pro Swiss yang berkualitas dan terpercaya. Dengan akun ini, Anda dapat menikmati berbagai keuntungan eksklusif dan fasilitas premium yang tidak tersedia untuk akun reguler.
    • SV388 SITUS RESMI SABUNG AYAM 2024   Temukan situs resmi untuk sabung ayam terpercaya di tahun 2024 dengan SV388! Dengan layanan terbaik dan pengalaman bertaruh yang tak tertandingi, SV388 adalah tempat terbaik untuk pecinta sabung ayam. Daftar sekarang untuk mengakses arena sabung ayam yang menarik dan nikmati kesempatan besar untuk meraih kemenangan. Jelajahi sensasi taruhan yang tak terlupakan di tahun ini dengan SV388! [[jumpuri:❱❱❱❱❱ DAFTAR DI SINI ❰❰❰❰❰ > https://w303.pink/orochimaru]] [[jumpuri:❱❱❱❱❱ DAFTAR DI SINI ❰❰❰❰❰ > https://w303.pink/orochimaru]]   JURAGANSLOT88 SITUS JUDI SLOT ONLINE TERPERCAYA 2024 Jelajahi pengalaman judi slot online terpercaya di tahun 2024 dengan JuraganSlot88! Sebagai salah satu situs terkemuka, JuraganSlot88 menawarkan berbagai pilihan permainan slot yang menarik dengan layanan terbaik dan keamanan yang terjamin. Daftar sekarang untuk mengakses sensasi taruhan yang tak terlupakan dan raih kesempatan besar untuk meraih kemenangan di tahun ini dengan JuraganSlot88 [[jumpuri:❱❱❱❱❱ DAFTAR DI SINI ❰❰❰❰❰ > https://w303.pink/orochimaru]] [[jumpuri:❱❱❱❱❱ DAFTAR DI SINI ❰❰❰❰❰ > https://w303.pink/orochimaru]]
  • Topics

×
×
  • Create New...

Important Information

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