Jump to content

[1.16.1] Newer mappings file?


Thorgeig

Recommended Posts

The 1.16.1 modder download comes with a build.gradle that references 

mappings channel: 'snapshot', version: '20200514-1.16'

which is quite old and missing a lot of mappings, for example most of the mappings in Screen are gone.

 

Is there a newer version of the mappings? And if so, how do I find out without asking forum questions?

 

Link to comment
Share on other sites

16 minutes ago, Thorgeig said:

The 1.16.1 modder download comes with a build.gradle that references 


mappings channel: 'snapshot', version: '20200514-1.16'

which is quite old and missing a lot of mappings, for example most of the mappings in Screen are gone.

 

Is there a newer version of the mappings? And if so, how do I find out without asking forum questions?

 

Why don't you just try to set the date on the mappings to today?

It's sad how much time mods spend saying "x is no longer supported on this forum. Please update to a modern version of Minecraft to receive support".

Link to comment
Share on other sites

9 minutes ago, Novârch said:

Why don't you just try to set the date on the mappings to today?

That's not how that works.

  • Like 1

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.

Link to comment
Share on other sites

So that means there's no newer mapping at the moment. Fine with me, I'll wait a bit to update my mod.

Still, is there a way to get a list of currently available mappings? I've use https://files.minecraftforge.net/maven/de/oceanlabs/mcp/mcp_snapshot/, but that one only lists 1.15 files (I guess because it's a html file that's updated automatically but not when someone publishes a mapping manually) ?

 

Link to comment
Share on other sites

5 hours ago, Draco18s said:

That's not how that works.

Of course it isn't, I meant that he should at least test it.

It's sad how much time mods spend saying "x is no longer supported on this forum. Please update to a modern version of Minecraft to receive support".

Link to comment
Share on other sites

51 minutes ago, Novârch said:

Of course it isn't, I meant that he should at least test it.

Ok, but what if:

There isn't a mapping for today?
There isn't a new mapping every day, or even most days?

 

Shoving new dates in to "try" makes no sense. At least supply a location where the current mappings can be found.

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.

Link to comment
Share on other sites

On 6/27/2020 at 12:10 AM, Curle said:

MCP is outdated and isn't used any more. We have a newer system in place.

See the Discord/IRC.

But now, the newest mappings are from mcpbot, right? And when mcpbot has 1.16 mappings I should prefer them, if I want newer mappings, right?

Link to comment
Share on other sites

On 7/4/2020 at 9:41 AM, Maxi07 said:

But now, the newest mappings are from mcpbot, right? And when mcpbot has 1.16 mappings I should prefer them, if I want newer mappings, right?

MCPBot will not be getting 1.16 mappings. We are moving to a new system. Like I said. 

Edited by Curle
Link to comment
Share on other sites

  • 1 month later...
On 7/6/2020 at 6:00 PM, Curle said:

MCPBot will not be getting 1.16 mappings. We are moving to a new system. Like I said. 

Which new system? Where can I see the mapping builds? I started porting to 1.16.2 today, where 20200514-1.16 is still used. It is a bit frustrating not to know where to get new mappings.

Link to comment
Share on other sites

Mod Mappings Management System, MMMS.

AFAIK its not done yet.

  • Like 1

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.

Link to comment
Share on other sites

32 minutes ago, MSandro said:

Which new system? Where can I see the mapping builds? I started porting to 1.16.2 today, where 20200514-1.16 is still used. It is a bit frustrating not to know where to get new mappings.

Yes, thats weird. I figured out I can message the forge bot (forge-bot#9014) on discord with !mcpv and get the newest mappings I can use which is right now 20200723-1.16.1, but it seems like this is a non stable mapping and it is recommended to use the default mapping 20200514-1.16. But I use this mapping anyway and I have no problems.

 

It seems like this is not a normal mcp mapping from mcpbot but instead a modified version which I think is called mcpconfig (but I am not sure)

 

And the upcomming system is called MMMS / MMS (but I dont know what will be happening to mcp)

I want to hear more about the progress too

Edited by Maxi07
Link to comment
Share on other sites

You're misunderstanding the system. MCP itself is dead, we took the mappings and tweaked the format to make MCPConfig, which provides Forge's SRG->MCP names.

mcpbot's purpose was to allow users to contribute to these MCPConfig mappings.

Unfortunately, mcpbot is unmaintained, and with the huge amounts of technical debt acquired, plus the maintainer/creator going dark for a while, we're making a new system to replace it.

 

That's what the Mod Mapping Management System is. It replaces mcpbot, which was designed to allow you to contribute to MCPConfig mappings.

 

The 20200723 release is official. It is recommended. It is not from mcpbot, it was made manually, by a Forge team member.

 

Hopefully this clears up some of your misconceptions of the system :)

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

19 minutes ago, Curle said:

The 20200723 release is official. It is recommended. It is not from mcpbot, it was made manually, by a Forge team member.

Then why 20200723 is not the default in build.gradle?

And will there be another way to check for newer mapping besides discord?

Link to comment
Share on other sites

Because we haven't updated the mdk yet.

 

Once MMMS lands, you can use that. It will export periodically automatically.

We may implement a system in ForgeGradle that tries to pull down new mappings every refresh, so that you don't have to worry about manually updating.

We'll see how it turns out.

 

For now, keep an eye on our Discord server.

Link to comment
Share on other sites

  • 2 months later...
On 8/14/2020 at 3:16 PM, Curle said:

You can see the latest mappings in our Discord server, where updates on the system are posted regularly: https://discord.gg/UvedJ9m

In respect to your answer, but I'm unable to get required info, the link point just to a forest of information and not to a single info from where the mappings come from.

I forced an wrong mappings to see what's the target artifact

 

Error getting artifact: net.minecraftforge:forge:1.16.1-32.0.108_mapped_snapshot_20200515-1.16:null@jar from  MinecraftUserRepo

 

Is there a table of contents ?

net.minecraftforge:forge

eg, this works net.minecraftforge:forge:1.16.1-32.0.108_mapped_snapshot_20200515-1.16

 

 

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

    • They were already updated, and just to double check I even did a cleanup and fresh update from that same page. I'm quite sure drivers are not the problem here. 
    • i tried downloading the drivers but it says no AMD graphics hardware has been detected    
    • Update your AMD/ATI drivers - get the drivers from their website - do not update via system  
    • As the title says i keep on crashing on forge 1.20.1 even without any mods downloaded, i have the latest drivers (nvidia) and vanilla minecraft works perfectly fine for me logs: https://pastebin.com/5UR01yG9
    • Hello everyone, I'm making this post to seek help for my modded block, It's a special block called FrozenBlock supposed to take the place of an old block, then after a set amount of ticks, it's supposed to revert its Block State, Entity, data... to the old block like this :  The problem I have is that the system breaks when handling multi blocks (I tried some fix but none of them worked) :  The bug I have identified is that the function "setOldBlockFields" in the item's "setFrozenBlock" function gets called once for the 1st block of multiblock getting frozen (as it should), but gets called a second time BEFORE creating the first FrozenBlock with the data of the 1st block, hence giving the same data to the two FrozenBlock :   Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=head] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@73681674 BlockEntityData : id:"minecraft:bed",x:3,y:-60,z:-6} Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=3, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=2, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} here is the code inside my custom "freeze" item :    @Override     public @NotNull InteractionResult useOn(@NotNull UseOnContext pContext) {         if (!pContext.getLevel().isClientSide() && pContext.getHand() == InteractionHand.MAIN_HAND) {             BlockPos blockPos = pContext.getClickedPos();             BlockPos secondBlockPos = getMultiblockPos(blockPos, pContext.getLevel().getBlockState(blockPos));             if (secondBlockPos != null) {                 createFrozenBlock(pContext, secondBlockPos);             }             createFrozenBlock(pContext, blockPos);             return InteractionResult.SUCCESS;         }         return super.useOn(pContext);     }     public static void createFrozenBlock(UseOnContext pContext, BlockPos blockPos) {         BlockState oldState = pContext.getLevel().getBlockState(blockPos);         BlockEntity oldBlockEntity = oldState.hasBlockEntity() ? pContext.getLevel().getBlockEntity(blockPos) : null;         CompoundTag oldBlockEntityData = oldState.hasBlockEntity() ? oldBlockEntity.serializeNBT() : null;         if (oldBlockEntity != null) {             pContext.getLevel().removeBlockEntity(blockPos);         }         BlockState FrozenBlock = setFrozenBlock(oldState, oldBlockEntity, oldBlockEntityData);         pContext.getLevel().setBlockAndUpdate(blockPos, FrozenBlock);     }     public static BlockState setFrozenBlock(BlockState blockState, @Nullable BlockEntity blockEntity, @Nullable CompoundTag blockEntityData) {         BlockState FrozenBlock = BlockRegister.FROZEN_BLOCK.get().defaultBlockState();         ((FrozenBlock) FrozenBlock.getBlock()).setOldBlockFields(blockState, blockEntity, blockEntityData);         return FrozenBlock;     }  
  • Topics

×
×
  • Create New...

Important Information

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