Jump to content

Forge 39.1 Minecraft 1.18.1


LexManos

Recommended Posts

Forge Version: 39.1.0
Minecraft Version: 1.18

Downloads:

However, as this is the start of a new version, it is recommended that you check the Downloads Page and use the latest version to receive any bug fixes.

Intro:

1.18 (38.0.x) is bundled in with this release because it was only out for a very short time.
It's been a long time coming - with 1.18.2 dangling over our heads for a while we prolonged the RB, but it's here, and it's stable. Not much API has been added, we spent a lot of time refactoring and slimming unused API.
Additionally, we used this time to transition to a new build server, so our capacity to make new builds of Forge has greatly increased.

Changelog:

New:

  • Add Client-sided Commands
  • Add renderable API to allow easier rendering of OBJ and other custom models
  • The vanilla Gametest framework is now integrated with Forge
  • The character "-" is no longer allowed in modids.
  • VanillaGameEvent was added to allow for globally listening to vanilla GameEvents
  • GameEvents for shears and elytras were added
  • Items can hide parts of their tooltips by default
  • StructureFeatures can be added to tags
  • MobEffects can be added to tags
  • Added the ability to get a Codec for a ForgeRegistry
  • Add ShieldBlockEvent
  • Add RenderArmEvent
  • Added server ping data compression - solves some situations where servers are wrongly marked as incompatible
  • Allow dimension JSONs to specify that the dimension should use the overworld's seed

Fixes:

  • Log4J security mitigations for every version released, past present and future
  • Fixed double registry injection when loading single player worlds
  • Fixed RegistryObject not working if created after registry events are fired
  • Missing or unsupported dependencies are now logged, in case they cause a crash before we can show a screen
  • Creating config files also creates parent directories if they do not already exist, as they used to
  • Fixed particles being fullbright for a few frames when first spawning
  • Fixed TerrainParticle rendering black under certain conditions
  • Fixed comparison of custom ParticleRenderTypes leading to broken particle effects
  • Fixed clients being unable to deserialize tags for custom registries
  • Fixed being unable to fetch blockstate in BucketPickup#getPickupSound (for multipley-logged blocks)
  • Fixed custom climbable blocks not sending a death message
  • Fixed modded tools not working on glow lichen
  • Fixed issues when multiple mods declare the same optional tag
  • Fixed `MinecraftLocator` not respecting non-`MOD` FML Mod Types
  • Fixed server side release of custom payload packet buffers
  • Fixed ScreenEvent accepting null screens
  • Fixed getPickupSound not being implemented on ForgeFlowingFluid
  • Fixed LivingExperienceDropEvent not firing, expecially for dragons
  • Fixed String.format calls not having a Locale parameter
  • Fixed LivingDropsEvent not having all drops for foxes
  • Fixed Mob Spawner logic with CustomSpawnRules
  • Fixed regressions for onAddedTo/RemovedFromWorld and related events

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

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Try deliting feur builder  It caused this issue in my modpack
    • I am not using hardcoded recipes, I'm using Vanilla's already existing code for leather armor dying. (via extending and implementing DyeableArmorItem / DyeableLeatherItem respectively) I have actually figured out that it's something to do with registering item colors to the ItemColors instance, but I'm trying to figure out where exactly in my mod's code I would be placing a call to the required event handler. Unfortunately the tutorial is criminally undescriptive. The most I've found is that it has to be done during client initialization. I'm currently trying to do the necessary setup via hijacking the item registry since trying to modify the item classes directly (via using SubscribeEvent in the item's constructor didn't work. Class so far: // mrrp mrow - mcmod item painter v1.0 - catzrule ch package catzadvitems.init; import net.minecraft.client.color.item.ItemColors; import net.minecraft.world.item.Item; import net.minecraftforge.registries.ObjectHolder; import net.minecraftforge.fml.event.lifecycle.FMLClientSetupEvent; import net.minecraftforge.fml.common.Mod; import net.minecraftforge.eventbus.api.SubscribeEvent; import net.minecraftforge.client.event.ColorHandlerEvent; import catzadvitems.item.DyeableWoolArmorItem; @Mod.EventBusSubscriber(bus = Mod.EventBusSubscriber.Bus.MOD) public class Painter { @ObjectHolder("cai:dyeable_wool_chestplate") public static final Item W_CHEST = null; @ObjectHolder("cai:dyeable_wool_leggings") public static final Item W_LEGS = null; @ObjectHolder("cai:dyeable_wool_boots") public static final Item W_SOCKS = null; public Painter() { // left blank, idk if forge throws a fit if constructors are missing, not taking the chance of it happening. } @SubscribeEvent public static void init(FMLClientSetupEvent event) { new Painter(); } @Mod.EventBusSubscriber private static class ForgeBusEvents { @SubscribeEvent public static void registerItemColors(ColorHandlerEvent.Item event) { ItemColors col = event.getItemColors(); col.register(DyeableUnderArmorItem::getItemDyedColor, W_CHEST, W_LEGS, W_SOCKS); //placeholder for other dye-able items here later.. } } } (for those wondering, i couldn't think of a creative wool helmet name)
    • nvm found out it was because i had create h and not f
    • Maybe there's something happening in the 'leather armor + dye' recipe itself that would be updating the held item texture?
    • @SubscribeEvent public static void onRenderPlayer(RenderPlayerEvent.Pre e) { e.setCanceled(true); model.renderToBuffer(e.getPoseStack(), pBuffer, e.getPackedLight(), 0f, 0f, 0f, 0f, 0f); //ToaPlayerRenderer.render(); } Since getting the render method from a separate class is proving to be bit of a brick wall for me (but seems to be the solution in older versions of minecraft/forge) I've decided to try and pursue using the renderToBuffer method directly from the model itself. I've tried this route before but can't figure out what variables to feed it for the vertexConsumer and still can't seem to figure it out; if this is even a path to pursue.  The vanilla model files do not include any form of render methods, and seem to be fully constructed from their layer definitions? Their renderer files seem to take their layers which are used by the render method in the vanilla MobRenderer class. But for modded entities we @Override this function and don't have to feed the method variables because of that? I assume that the render method in the extended renderer takes the layer definitions from the renderer classes which take those from the model files. Or maybe instead of trying to use a render method I should be calling the super from the renderer like   new ToaPlayerRenderer(context, false); Except I'm not sure what I would provide for context? There's a context method in the vanilla EntityRendererProvider class which doesn't look especially helpful. I've been trying something like <e.getEntity(), model<e.getEntity()>> since that generally seems to be what is provided to the renderers for context, but I don't know if it's THE context I'm looking for? Especially since the method being called doesn't want to take this or variations of this.   In short; I feel like I'm super super close but I have to be missing something obvious? Maybe this insane inane ramble post will provide some insight into this puzzle?
  • Topics

×
×
  • Create New...

Important Information

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