N3ME improvement to do list - suggestions

[jwreaper]

Search before asking

• [x] I searched the issues and found no similar issues.

Description

List made based on my experience with this repository's N3ME and recently leaked N3ME's "new version", from a general view, for general usage (beyond project).

_-DX9 support helped a lot compared to previous versions, however when increasing far plane and ground view range it gets a bit slow.

-Make whole colormap is buggy sometimes, N3ME will close and colormap may appear with colored big pixels, this doesn't always happen but once colormap gets buggy, there's no way back.

-Resources loading time can be long depending of the amount of resources (happened w all versions, could be faster if you can).

-Adding support for USKO dxt could be useful, some objects can be seen like multipixeled (unsupported texture).

-Adding support for client format opening is needed (considering you work with 1098-1299 it can be useful, "new version" of N3ME can't open those versions).

-Some tags of N3ME still need to be translated for optimal usage (all versions still show some ???? instead of text)._

The following are the ones i consider the hardest but absolutely needed:

_-OPDSUB creation, placing FXB over an existing object according to output list order. If you need a deep explaination of OPDSUB structure you can DM me anytime.

-Flag edition, already created by Tahsin, adding graphic support similar to object placement could be the goal.

-GTT composition, loading many GTT to be used as terrain with proper blending between different textures, when selecting something beyond "ys_freezone" program may crash.

-Exploring proper use of EVENT function, which is unknown to (99% sure) everyone.

-1299 or superior exporting compatibility, for 1299 some header hexing is needed and for newer versions (mostly 2383) a gtd patcher is needed ("new version" exports 22xx only).

-River - Pond functions to be deeply tested and fixed if needed, 2383 shows nothing after a pond is placed (may discuss this maybe, original old maps work properly, this may be something missing).

-Minimap creation, taking a screenshot from above is not the best of choices._

There's maybe some stuff i have forgot to list here but i have tried to mention almost everything i know. Some people may also have experienced and found different things.

Thank you in advance for your work.

Use case

Fixing and upgrading N3ME will help not just the project but the KO development community itself.

Are you willing to work on and submit a PR to address the issue?

• [ ] Yes I am willing to submit a PR!