sven-n / mumain Goto Github PK

did you know where is the source of ItemTooltip ? your answer is import for me and thanks.

For text rendering, see CUIRenderTextOriginal::RenderText.
Currently, emojis are only rendered in one color.

To draw colored emojis we'd need to draw a group of them on a texture bitmap (e.g. 16x16 emojis each 32x32 pixels) using direct2d, or by providing an already rendered bitmap.
It would be great to have some on-demand mechanism to create new textures if previously unrendered emojis are requested, so the first option might be more suitable.

As we have .NET available, it could also be possible to manage emojis in the .NET world. There are some nice libraries which could help us there, e.g. SixLabors/ImageSharp.Drawing#268

When starting a chat with a friend of the friend list in the MUssenger, the first click on "Chat" doesn't open the chat window, but only creates the connection to the chat server. When clicking on "Shat" again, the window opens.

For the player which initiated the chat, the chat window should open, once the connection is done and the client entered the chat room. For the other player, the currently working notification is enough.

If an other account created an guild on the same client instance the guld info name and image are not reset.

The project has many environment variables but haven't any .env file, for an example.

I try to run projects on Linux using dotnet cli and receive many errors.

There would be a good thing if repo had a .env.example and a table on README.md with variables description.

Please give me instructions to run it

There is not yet all logic for Mu Helper implemented.
Just making that issue for starting some sort of backlog xD

When moving the mouse over a pet (Dark Horse, Dark Raven) in the inventory, the client requests the current pet information (level, etc.). Unfortunately, this request is sent repeatedly for each frame.

It would be beneficial if the amount of requests could be minimized to a reasonable level - ideally, once per hover operation, with a timeout of about a second for the next request.