Jump to content

Recommended Posts

Posted

I looked through the changes for 1.13 for the first time today, and I saw they are reworking the way items and blocks are implemented, along with other changes and additions like data packs and removal of metadata.

 

Will this mean a lot for me as a forge modder? I can assume that things will break, but on what scale?

  • Like 1
Posted
21 minutes ago, That_Martin_Guy said:

I can assume that things will break, but on what scale?

hopefully not as much as 1.8 broke everything

About Me

Spoiler

My Discord - Cadiboo#8887

My WebsiteCadiboo.github.io

My ModsCadiboo.github.io/projects

My TutorialsCadiboo.github.io/tutorials

Versions below 1.14.4 are no longer supported on this forum. Use the latest version to receive support.

When asking support remember to include all relevant log files (logs are found in .minecraft/logs/), code if applicable and screenshots if possible.

Only download mods from trusted sites like CurseForge (minecraft.curseforge.com). A list of bad sites can be found here, with more information available at stopmodreposts.org

Edit your own signature at www.minecraftforge.net/forum/settings/signature/ (Make sure to check its compatibility with the Dark Theme)

Posted

Things are going to change. And people will complain about it. There isn't anything that can be done about it so threads like these are useless. 

 

  • Like 3

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Posted
On 3/12/2018 at 12:00 AM, LexManos said:

Things are going to change. And people will complain about it. There isn't anything that can be done about it so threads like these are useless. 

 

I have no doubt in my mind that things will change. I also don't doubt that it is for a good reason they (or you as a forge dev) make the changes. I simply would like to know the scale of it, so I can know  if minecraft gets a mountain of changes like in 1.8 or not.

  • Like 1
Posted
On 3/11/2018 at 4:00 PM, LexManos said:

Things are going to change. And people will complain about it. There isn't anything that can be done about it so threads like these are useless.

Personally I'm interested in knowing what will change: what will newly be possible and what will no longer be possible.

On 3/13/2018 at 9:24 AM, That_Martin_Guy said:

I have no doubt in my mind that things will change. I also don't doubt that it is for a good reason they (or you as a forge dev) make the changes. I simply would like to know the scale of it, so I can know  if minecraft gets a mountain of changes like in 1.8 or not.

It's going to be a mountain. Deal with it.

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

  • 2 weeks later...
  • 2 months later...
Posted

1.13 is going to be such a big jump that it will take years for there to be good mods again.

 

But boy, when all the mods do get updated, we're going to have some next-gen level stuff.

  • Haha 1
Posted

if someone made a mod that put 1.13 biomes and mobs into 1.12.2 That would be great. The best of both worlds. But that won't happen, 1.13 is just too different from 1.12.2, and while I'm having tons of fun with it I really miss my mods :(.

  • Like 2
Posted
On 6/16/2018 at 6:58 PM, OrangeVillager61 said:

Eh, the modding community is still bouncing back from the 1.8 debacle so I'm not so sure on that.

That's mostly because of the combat changes, not because of the changes to the codebase. That was only in the beginning when people were bitching about the model system.

Don't PM me with questions. They will be ignored! Make a thread on the appropriate board for support.

 

1.12 -> 1.13 primer by williewillus.

 

1.7.10 and older versions of Minecraft are no longer supported due to it's age! Update to the latest version for support.

 

http://www.howoldisminecraft1710.today/

  • 2 weeks later...
Posted

Being a first time developer for MC, should I just wait for 1.13 to drop to continue programming my idea since there is going to be a fundamental change to how items are handled? I've got about 3 years of Java under my belt already so it isn't a familiarity with coding that has me worried, but familiarity with the libraries and how things work with forge.

  • 4 weeks later...
Posted
On 6/26/2018 at 2:20 PM, pr0racing said:

Being a first time developer for MC, should I just wait for 1.13 to drop to continue programming my idea since there is going to be a fundamental change to how items are handled? I've got about 3 years of Java under my belt already so it isn't a familiarity with coding that has me worried, but familiarity with the libraries and how things work with forge.

100% wait. The fundamentals of the Minecraft codebase have changed quite a bit; as such, the Forge layer on top of it will need to change drastically. I'm almost certain that even those of us who have been using Forge for awhile will have to "re-learn" the 1.13 structure, as it were. So you may as well wait until then to start learning so you don't have to start all over :)

  • Like 3

Whatever Minecraft needs, it is most likely not yet another tool tier.

  • 2 weeks later...
Posted
Just now, KatherineFtw said:

All things considered, 1.14 was rumored to be almost a total overhaul. Expect worse for that than this. The biggest problem will be worldgen/resoucegen prob for 1.12 >1.13.

Did you hear that before or after 1.13 became the Aquatic Update (i.e. merged with what was planned for 1.14)? Because from what I heard, the devs are trying not to do any major code refactoring for a little while after 1.13.

  • Like 1

Whatever Minecraft needs, it is most likely not yet another tool tier.

Posted
Just now, IceMetalPunk said:

Did you hear that before or after 1.13 became the Aquatic Update (i.e. merged with what was planned for 1.14)? Because from what I heard, the devs are trying not to do any major code refactoring for a little while after 1.13.

 

Before.

Posted
On 7/28/2018 at 6:56 AM, IceMetalPunk said:

100% wait. The fundamentals of the Minecraft codebase have changed quite a bit; as such, the Forge layer on top of it will need to change drastically. I'm almost certain that even those of us who have been using Forge for awhile will have to "re-learn" the 1.13 structure, as it were. So you may as well wait until then to start learning so you don't have to start all over :)

Thanks for the honest opinion :) This could save a bunch of people who wanted to hurry in upgrading.

Posted
On 7/27/2018 at 7:26 PM, IceMetalPunk said:

100% wait. The fundamentals of the Minecraft codebase have changed quite a bit; as such, the Forge layer on top of it will need to change drastically. I'm almost certain that even those of us who have been using Forge for awhile will have to "re-learn" the 1.13 structure, as it were. So you may as well wait until then to start learning so you don't have to start all over :)

I'm not sure I agree 100%. I've been hearing that Forge will take several months to be ready. If your Java knowledge is solid, you could get a lot done in that time and learn a lot of concepts that will remain the same. However, if your mod has anything to do with world gen, I would definitely wait. And if you don't know Java very well, I would recommend spending a few months getting your Java knowledge solid while you wait.

Posted (edited)
3 minutes ago, Daeruin said:

I'm not sure I agree 100%. I've been hearing that Forge will take several months to be ready. If your Java knowledge is solid, you could get a lot done in that time and learn a lot of concepts that will remain the same. However, if your mod has anything to do with world gen, I would definitely wait. And if you don't know Java very well, I would recommend spending a few months getting your Java knowledge solid while you wait.

I don't know about that. World gen changed, but so did block handling, item handling, command handling, and tons more. And from what I've seen on Twitter, Forge itself is getting a huge refactoring in response as well. So I'm not sure if the amount that remains unchanged will be all that significant... For people who already know how to work with Forge for 1.12.2, there's definitely enough time to make another mod. But for people who have never used it... I don't think there's enough time to learn Forge*and* make a complete mod before having to re-learn Forge for 1.13.

Edited by IceMetalPunk

Whatever Minecraft needs, it is most likely not yet another tool tier.

Posted

From my experience with Java 9/10 they've really screwed up reflection. EnumHelper, to give an example, probably won't work in Java 10 because Oracle has decided they're going to be very much more strict about illegal reflective operations. (Changing final variables especially, but I imagine this will carry over into enums as a security 'feature'). And afaik there isn't any amount of elevated privilege that allows you to bypass this, but I could be wrong.

 

Is the plan to switch FML to Java 9/10? If not what's the plan to handle these sorts of things?

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

    • Version 1.19 - Forge 41.0.63 I want to create a wolf entity that I can ride, so far it seems to be working, but the problem is that when I get on the wolf, I can’t control it. I then discovered that the issue is that the server doesn’t detect that I’m riding the wolf, so I’m struggling with synchronization. However, it seems to not be working properly. As I understand it, the server receives the packet but doesn’t register it correctly. I’m a bit new to Java, and I’ll try to provide all the relevant code and prints *The comments and prints are translated by chatgpt since they were originally in Spanish* Thank you very much in advance No player is mounted, or the passenger is not a player. No player is mounted, or the passenger is not a player. No player is mounted, or the passenger is not a player. No player is mounted, or the passenger is not a player. No player is mounted, or the passenger is not a player. MountableWolfEntity package com.vals.valscraft.entity; import com.vals.valscraft.network.MountSyncPacket; import com.vals.valscraft.network.NetworkHandler; import net.minecraft.client.Minecraft; import net.minecraft.network.syncher.EntityDataAccessor; import net.minecraft.network.syncher.EntityDataSerializers; import net.minecraft.network.syncher.SynchedEntityData; import net.minecraft.server.MinecraftServer; import net.minecraft.server.level.ServerPlayer; import net.minecraft.world.entity.EntityType; import net.minecraft.world.entity.Mob; import net.minecraft.world.entity.ai.attributes.AttributeSupplier; import net.minecraft.world.entity.ai.attributes.Attributes; import net.minecraft.world.entity.animal.Wolf; import net.minecraft.world.entity.player.Player; import net.minecraft.world.entity.Entity; import net.minecraft.world.InteractionHand; import net.minecraft.world.InteractionResult; import net.minecraft.world.item.ItemStack; import net.minecraft.world.item.Items; import net.minecraft.world.level.Level; import net.minecraft.world.phys.Vec3; import net.minecraftforge.event.TickEvent; import net.minecraftforge.eventbus.api.SubscribeEvent; import net.minecraftforge.network.PacketDistributor; public class MountableWolfEntity extends Wolf { private boolean hasSaddle; private static final EntityDataAccessor<Byte> DATA_ID_FLAGS = SynchedEntityData.defineId(MountableWolfEntity.class, EntityDataSerializers.BYTE); public MountableWolfEntity(EntityType<? extends Wolf> type, Level level) { super(type, level); this.hasSaddle = false; } @Override protected void defineSynchedData() { super.defineSynchedData(); this.entityData.define(DATA_ID_FLAGS, (byte)0); } public static AttributeSupplier.Builder createAttributes() { return Wolf.createAttributes() .add(Attributes.MAX_HEALTH, 20.0) .add(Attributes.MOVEMENT_SPEED, 0.3); } @Override public InteractionResult mobInteract(Player player, InteractionHand hand) { ItemStack itemstack = player.getItemInHand(hand); if (itemstack.getItem() == Items.SADDLE && !this.hasSaddle()) { if (!player.isCreative()) { itemstack.shrink(1); } this.setSaddle(true); return InteractionResult.SUCCESS; } else if (!level.isClientSide && this.hasSaddle()) { player.startRiding(this); MountSyncPacket packet = new MountSyncPacket(true); // 'true' means the player is mounted NetworkHandler.CHANNEL.sendToServer(packet); // Ensure the server handles the packet return InteractionResult.SUCCESS; } return InteractionResult.PASS; } @Override public void travel(Vec3 travelVector) { if (this.isVehicle() && this.getControllingPassenger() instanceof Player) { System.out.println("The wolf has a passenger."); System.out.println("The passenger is a player."); Player player = (Player) this.getControllingPassenger(); // Ensure the player is the controller this.setYRot(player.getYRot()); this.yRotO = this.getYRot(); this.setXRot(player.getXRot() * 0.5F); this.setRot(this.getYRot(), this.getXRot()); this.yBodyRot = this.getYRot(); this.yHeadRot = this.yBodyRot; float forward = player.zza; float strafe = player.xxa; if (forward <= 0.0F) { forward *= 0.25F; } this.flyingSpeed = this.getSpeed() * 0.1F; this.setSpeed((float) this.getAttributeValue(Attributes.MOVEMENT_SPEED) * 1.5F); this.setDeltaMovement(new Vec3(strafe, travelVector.y, forward).scale(this.getSpeed())); this.calculateEntityAnimation(this, false); } else { // The wolf does not have a passenger or the passenger is not a player System.out.println("No player is mounted, or the passenger is not a player."); super.travel(travelVector); } } public boolean hasSaddle() { return this.hasSaddle; } public void setSaddle(boolean hasSaddle) { this.hasSaddle = hasSaddle; } @Override protected void dropEquipment() { super.dropEquipment(); if (this.hasSaddle()) { this.spawnAtLocation(Items.SADDLE); this.setSaddle(false); } } @SubscribeEvent public static void onServerTick(TickEvent.ServerTickEvent event) { if (event.phase == TickEvent.Phase.START) { MinecraftServer server = net.minecraftforge.server.ServerLifecycleHooks.getCurrentServer(); if (server != null) { for (ServerPlayer player : server.getPlayerList().getPlayers()) { if (player.isPassenger() && player.getVehicle() instanceof MountableWolfEntity) { MountableWolfEntity wolf = (MountableWolfEntity) player.getVehicle(); System.out.println("Tick: " + player.getName().getString() + " is correctly mounted on " + wolf); } } } } } private boolean lastMountedState = false; @Override public void tick() { super.tick(); if (!this.level.isClientSide) { // Only on the server boolean isMounted = this.isVehicle() && this.getControllingPassenger() instanceof Player; // Only print if the state changed if (isMounted != lastMountedState) { if (isMounted) { Player player = (Player) this.getControllingPassenger(); // Verify the passenger is a player System.out.println("Server: Player " + player.getName().getString() + " is now mounted."); } else { System.out.println("Server: The wolf no longer has a passenger."); } lastMountedState = isMounted; } } } @Override public void addPassenger(Entity passenger) { super.addPassenger(passenger); if (passenger instanceof Player) { Player player = (Player) passenger; if (!this.level.isClientSide && player instanceof ServerPlayer) { // Send the packet to the server to indicate the player is mounted NetworkHandler.CHANNEL.send(PacketDistributor.PLAYER.with(() -> (ServerPlayer) player), new MountSyncPacket(true)); } } } @Override public void removePassenger(Entity passenger) { super.removePassenger(passenger); if (passenger instanceof Player) { Player player = (Player) passenger; if (!this.level.isClientSide && player instanceof ServerPlayer) { // Send the packet to the server to indicate the player is no longer mounted NetworkHandler.CHANNEL.send(PacketDistributor.PLAYER.with(() -> (ServerPlayer) player), new MountSyncPacket(false)); } } } @Override public boolean isControlledByLocalInstance() { Entity entity = this.getControllingPassenger(); return entity instanceof Player; } @Override public void positionRider(Entity passenger) { if (this.hasPassenger(passenger)) { double xOffset = Math.cos(Math.toRadians(this.getYRot() + 90)) * 0.4; double zOffset = Math.sin(Math.toRadians(this.getYRot() + 90)) * 0.4; passenger.setPos(this.getX() + xOffset, this.getY() + this.getPassengersRidingOffset() + passenger.getMyRidingOffset(), this.getZ() + zOffset); } } } MountSyncPacket package com.vals.valscraft.network; import com.vals.valscraft.entity.MountableWolfEntity; import net.minecraft.network.FriendlyByteBuf; import net.minecraft.server.level.ServerLevel; import net.minecraft.server.level.ServerPlayer; import net.minecraft.world.entity.Entity; import net.minecraft.world.entity.player.Player; import net.minecraftforge.network.NetworkEvent; import java.util.function.Supplier; public class MountSyncPacket { private final boolean isMounted; public MountSyncPacket(boolean isMounted) { this.isMounted = isMounted; } public void encode(FriendlyByteBuf buffer) { buffer.writeBoolean(isMounted); } public static MountSyncPacket decode(FriendlyByteBuf buffer) { return new MountSyncPacket(buffer.readBoolean()); } public void handle(NetworkEvent.Context context) { context.enqueueWork(() -> { ServerPlayer player = context.getSender(); // Get the player from the context if (player != null) { // Verifies if the player has dismounted if (!isMounted) { Entity vehicle = player.getVehicle(); if (vehicle instanceof MountableWolfEntity wolf) { // Logic to remove the player as a passenger wolf.removePassenger(player); System.out.println("Server: Player " + player.getName().getString() + " is no longer mounted."); } } } }); context.setPacketHandled(true); // Marks the packet as handled } } networkHandler package com.vals.valscraft.network; import com.vals.valscraft.valscraft; import net.minecraft.resources.ResourceLocation; import net.minecraftforge.network.NetworkRegistry; import net.minecraftforge.network.simple.SimpleChannel; import net.minecraftforge.network.NetworkEvent; import java.util.function.Supplier; public class NetworkHandler { private static final String PROTOCOL_VERSION = "1"; public static final SimpleChannel CHANNEL = NetworkRegistry.newSimpleChannel( new ResourceLocation(valscraft.MODID, "main"), () -> PROTOCOL_VERSION, PROTOCOL_VERSION::equals, PROTOCOL_VERSION::equals ); public static void init() { int packetId = 0; // Register the mount synchronization packet CHANNEL.registerMessage( packetId++, MountSyncPacket.class, MountSyncPacket::encode, MountSyncPacket::decode, (msg, context) -> msg.handle(context.get()) // Get the context with context.get() ); } }  
    • Do you use features of inventory profiles next (ipnext) or is there a change without it?
    • Remove rubidium - you are already using embeddium, which is a fork of rubidium
  • Topics

×
×
  • Create New...

Important Information

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