-
Notifications
You must be signed in to change notification settings - Fork 11
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
Export to 8.60 version #9
Comments
Unfortunately not with the current code. My original idea was to make it possible to export for different versions, but I have since abandoned that idea due to a lack of time. There is a small amount of separation between otb versions in the code, but you would need many changes to the code to make it work for 8.60. If you want to try to fix it yourself, here's some information:
I can't remember whether I've tested the loading of .dat files in this repository (Backend/Tibia7/DatIO.cs). It is possible that there are problems there as well. You will have to modify LapisItemEditor/ViewModels/Main/ItemPropertiesViewModel.cs and Backend/Appearance.cs so that they don't make use of code from the You also need to modify the OtbData::WriteItemTypes function so that it doesn't write otb properties that didn't exist in 8.60: LapisItemEditor/Backend/OtbData.cs Line 499 in 036a849
These are the main things I can think of, but there will doubtlessly be additional smaller changes required in other places in the code base as well. Sorry I can't be of more help, good luck! |
I have been working on the support for .dat and .spr files. So far the .dat and .spr files are loaded successfully, but I'm coming across some obstacles that might be silly for someone with a better understanding of how the design of an Item Editor is supposed to be. If you could reach out to me that would be great! Edit: |
Glad to hear @Aniiiko! Aplogoies for not answering, I've been absent from all things coding during my vacation 😄 |
Would it be possible to export to a version of otb 8.60?
The text was updated successfully, but these errors were encountered: