Mappings for Beta 1.9 Pre-3?

[aasdsjakdask]

I really want mappings for beta 1.9 pre-3, any plan for those?
If not, any way to add a custom version?

[PhoenixVX]

See the following tutorials:
What is matching?
Creating mappings
How to create a new version

Start from the first tutorial and match b1.9 to b1.9-pre3. That will give you a basic set of mappings which then can be filled out by the creating mappings tutorial. After that, you will need to setup the rest of the exceptor files to properly decompile. The exceptor files from b1.9 should work OOTB for b1.9-pre3.

Much of mapping development has stalled. I do have a previous attempt from genericpnpmonitor of pre-1 through pre-3. Not sure how complete or how usable it is.
b1.9-pre-mappings.zip

These mappings look to be made for RetroMCP versions before v1.0. Most likely v1.0-pre3. To use them in modern RMCP, you can use the "Merge mappings" task after putting client.tiny/server.tiny in the same folder as the RetroMCP JAR. Delete patches_client and patches_server as they should not be needed if mappings / exceptor files are correct. You can also delete start folder as start patches are no longer needed in RetroMCP. Make sure to combine these files with b1.9 files available at https://mcphackers.org/versionsv3.html#b1.9-pre5 (save for mappings.tiny after being merged)

[aasdsjakdask]

wdym? theres no b1.9 pre1 mappings in the retromcp, only b1.9 pre 5
by matching b1.9 with b1.9 pre 3 u mean matching that zip to b1.9 pre3?
Edit: also i have no idea how to use matcher cuz theres no tutorial/guide, can u help me with that

[PhoenixVX]

Try the Beta 1.9-pre3 mappings in b1.9-pre-mappings.zip. You will need to use the "Merge mappings" task to use them in modern RetroMCP. If it's not complete, you may need to use Enigma to complete the mappings. If those mappings have already been decently matched, there should be no reason to do that work again.

If you do need to use Matcher, press on File -> New project. Side A should have the beta 1.9-pre5 JAR and side B should have b1.9-pre3 JAR. After that, you can use File -> Load mappings to load the mappings on Side A (not Side B). Press Match -> Auto match all, then sort the classes by unmatched status. Unmatched is red, partially matched is yellow, and green is fully matched. Auto match should get between 85 - 95% automatically and the rest is mostly going to be partially matched. From there, match what you can and use File -> Export mappings and make sure to export mappings for Side B, not Side A.

Side A is the version you are porting FROM, side B is the version you are porting TO.

[aasdsjakdask]

but where are the exceptions file in the mappings zip

[PhoenixVX]

There is none made for the beta 1.9-pre3 mappings. Download the b1.9-pre5 mappings and take the exceptions file from there. It should be most, if not all of the exceptions needed.