OpenTibia OTB Editor for TFS 1.3 Nekiro downgrade 7.72

[Azakelis]

So like a year ago i was frustrated because I couldn't find working item editor with the nekiro 7.72 downgrade, even if i found it would be missing some features so I did this simple editor in like a hour or so (trash quality).

features:

• loads specific otb from nekiro 7.72 downgrade into database so you can edit it via sql also
• cloning items in gui
• deleting items in gui
• editing items in gui
• creating items in gui
• editing otb metadata
• strips off unused data ex. sprite hex, names
• includes only attributes used by nekiro downgrade (so no useless stuff like names, descriptions)

last tested on php 7.4, loading/saving may be slow on hdd, tested on ssd

how to use:
1. unpackage in xampp htdocs directory (windows) / www folder (linux)
2. edit config.php and provide your database credentials
3. create database otbe
4. import otbe.sql into database otbe
5. put your items.otb in /in/ folder
6. load otb
7. edit items
8. save otb
9. result is in /out/ folder

screens:

 

[Pittyalv]

Nice

 

[reginaldofilhog]

I was doing exactly that lol, how cool! I'm confused in TFS 1.5 Nekiro 7.72.. Let's see if this Editor item works...

 

[Pedrook]

hey, I made some modifications;

Item Editor - OTB Management System

GitHub - pedrogiampietro/item-editor: Try demo!

Try demo! Contribute to pedrogiampietro/item-editor development by creating an account on GitHub.

github.com

local works well, the demo due to the db load, is not 100%

 

[Azakelis]

it's weird to see that this topic is still alive

obviously you can do whatever you want with this but I just wouldn't recommend extending it cuz it's trash
you would get much better result in the long run if you just started from scratch

if i did this today and spent more than 1-2 hours total on this and if that was for general use (possibly as a service you host from the demo I see) I would do it much differently
1. php is not the best for this case either do all of the work on frontend (js) or golang backend with js front
2. I wouldn't use the load into db approach, probably just keep in memory of backend or frontend
3. I'd probably make it support every single otb version
4. static sprites as separate images isn't the best approach like the minimum would be creating an atlas out of this or loading it from .dat and .spr directly for much better general use
5. i would also consider support of editing the .dat and .spr here to have it all in one tool additionally items.xml also (obviously via gui)

and probably some other things that I forgot about

but anyway this otb format should have been dropped like 15 years ago at least by the ot community going at least for xml (obviously should consider json or something at this point) cuz this trash doesn't have that much worthwhile data inside of it anyway