Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OptiFine CIT Doesn't support enchantments #34

Open
Cxrrlos opened this issue Jun 28, 2021 · 19 comments
Open

OptiFine CIT Doesn't support enchantments #34

Cxrrlos opened this issue Jun 28, 2021 · 19 comments
Labels
Feature Feature Request
Milestone

Comments

@Cxrrlos
Copy link

Cxrrlos commented Jun 28, 2021

It has converted everything nicely, though my custom textures do not work after the conversion.

The mcpatcher --> cit has changed and become optifine --> cit, though the textures do not work.

(more info on these textures: I had some of when armour was at a certain hp, it changed to look more broken, I also had different textures for sharpness 5 swords)

This was a 1.8 to 1.16.5 conversion, though these textures also worked on 1.12.2 before.

@CoryBorek
Copy link
Member

Can you give me one of your CIT .properties files so I can take a look and see if I need to make any changes?

@Cxrrlos
Copy link
Author

Cxrrlos commented Jun 28, 2021

This is for a diamond sword, when its sharpness 5 it should normally change the texture (Im not sure why the # date and # are there, I didnt put them)

Also, the name of this file is: opsword.properties
(I couldnt just drag it here because it says it doesnt support the .properties file type)

#Mon Jun 28 00:21:28 CEST 2021
items=276
enchantmentLevels=5
type=item
enchantmentIDs=16
texture=opsword.png

@CoryBorek
Copy link
Member

And where is opsword.png located? in the same folder as opsword.properties?

@Cxrrlos
Copy link
Author

Cxrrlos commented Jun 30, 2021

Yes, I believe its all in the same folder.
The mcpatcher --> cit is now optifine --> cit, but all the pngs and .properties are in the same cit folder like they used to be.

@CoryBorek
Copy link
Member

so the pngs and properties are in mcpatcher --> cit and not optifine --> cit?

@Cxrrlos
Copy link
Author

Cxrrlos commented Jul 1, 2021

now there is no folder called mcpatcher, to get to the cit folder, I do assets --> minecraft --> optifine --> cit

@CoryBorek
Copy link
Member

oh okay. there may have been changes to optifine then. I know this system used to work in 1.13

@Cxrrlos
Copy link
Author

Cxrrlos commented Jul 1, 2021

So, is there any way to get it to work? Even if its manually?

@CoryBorek
Copy link
Member

I'd have to look into the changelogs for optifine. If it's something fixable, I can implement changes relatively easily

@CoryBorek
Copy link
Member

Quick question, Try removing the .png from the image replacement text and see what happens?

@Cxrrlos
Copy link
Author

Cxrrlos commented Jul 2, 2021

Im not sure what you mean by: "image replacement text". Do you mean changing the file name to not be a .png?

I have removed the .png and edited the .properties document to look for the new file name.
(So, in the .properties I have changed it to texture=opsword)

It still doesnt seem to be working.

@CoryBorek
Copy link
Member

Don't remove the .png from the file itself, just the reference in the .properties file

@Cxrrlos
Copy link
Author

Cxrrlos commented Jul 2, 2021

It still is not working

@CoryBorek
Copy link
Member

I'll have to look at the optifine changelog then.

@CoryBorek
Copy link
Member

Update: The software doesn't currently change enchantment ids. That will probably have to be fixed

@CoryBorek CoryBorek changed the title custom textures not working on converted version OptiFine CIT Doesn't support enchantments Jul 2, 2021
@Cxrrlos
Copy link
Author

Cxrrlos commented Jul 2, 2021

Though, I think this is not only enchantments because none of the others change. ( I have one for when armour was at a certain hp, it changed to look more broken )

@CoryBorek
Copy link
Member

This will not be worked on until #68 is finished. I'd like all the OptiFine and other mod changes to be moved over to Extensions, as that will make it easier for other mods to be worked on. Will only fix any major issues of stuff currently implemented.

@CoryBorek
Copy link
Member

Most likely will move away from supporting CIT in the future. Will leave open until a final decision is made.

@CoryBorek CoryBorek added the Feature Feature Request label Jun 19, 2024
@lowercasebtw
Copy link
Contributor

I hope not, a lot of 1.8 packs use CIT and this converter would be huge for the 1.8 community, already shared it to a lot of people I know, including 1.8 pack makers

@CoryBorek CoryBorek added this to the older-parity milestone Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Feature Request
Projects
None yet
Development

No branches or pull requests

3 participants