feat: read assets from client 11+

[dudantas]

Description

• Change old Remeres client .dat/.spr reader to client 12x /assets/ appeerances and sprites files.
• Remove OTB file system.
• Protobuf lib on remeres.
• Update brushes and tags.
• Fixes:

1. Top order issues;

• Additions:

1. New fields in the new items properties window
2. Option to toggle between the old and new item properties window

How to test so far

1. Set your client folder to the preferences "client path"
2. Create a brand-new map on new button on startup.
3. Import a saved map on import map button option.

Draft

The PR is on draft due to some necessary changes:

• Wrong outfit offset on non stantard sprite size. (Different from 32x32)
• Paint outfit collors
• Problem on loading Remeres icons.
• Remove client version structure.
• Review the entire graphics.cpp structure and functions.
• Not saving maps
• Some sprites not show
  
• Creatures sprites not show on "jump to brush" bar
  
• Fix the brushes icons
  

Credits

• Co-author @marcosvf132
• Nekiro protobuf lib. (Sprite reader)

[phacUFPE]

@dudantas Reload button is not updating assets modifications.

Reload button working as expected, could you please provide further details to how reproduce this issue?

I tested here by creating new items, compiling the assets with the new item, reloading and the item was shown in the RAW Palette -> Others. Where it should be.

[phacUFPE]

We have a problem when turning off "shown monsters spawns": it deactivates, but when another creature is placed on the map, it reactivates.

We also have a problem when importing creatures or NPCs; if the quantity is too large, the client crashes.

I checked and it seems to be a correct behavior on RME, it is also in the main,
If you want a way to disable it, please create a new issue that I'll be updating to give the user a choice to disable the show spawns config.

[jacques-tony]

Hi, @phacUFPE
It seems that for monsters/NPCs with outfits where colors are defined in the monsters.xml and npcs.xml files, when placing the monster/NPC on the map, it assigns some random colors to define the colors of the monster/NPC (Image 1). However, when changing the monster's position, it updates with the colors defined in the XML (Image 2).

Another point is the alphabetical ordering of Wa
ypoints from Z-A, and I believe the most logical order would be from A-Z.

Both points were tested only using this PR, so I’m unsure how it behaves in the main branch.

[sonarcloud]

Quality Gate failed

Failed conditions
E Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE