TipBox feature - misaligned link text

[ckx_]

Question

I have a problem that I simply can't figure out.

Occasionally when I start up the client, the "TipBox" feature renders misaligned links. Sometimes a client restart fixes this. My client version is 2020-07-15bRagexe.

Client restarts don't always fix this. Just sometimes. It's frustrating to have to restart the client sometimes 4 or 5 times to get the feature to work. It feels like a 50-50 chance but I didn't measure a precise probability.

Does anyone know any workarounds for this (system configuration or otherwise), or why it occurs?

Extra info

The tip boxes are read from System\tipbox_EN.lub. Note that this path is configurable with a WARP client hex ("Customize Tipbox lub"). The original Korean file is at System\tipbox.lub. I've tried a client without that hex applied, just loading up that original Korean file, and it has the same problem. This leads me to believe that the official game may have the same issue too. I've tested on both Windows and Linux (proton).

 TipBoxes are lua tables, with each tipbox's page content being one big string:

[1] = {
	Title = "Tutorials",
	Search = 1,
	Image = "",
	Imgcoord = { Position = 5, Size = 100 },
	Page = {
		"With the Tipbox you might find answers to your questions.\n\rTips \rthat \nare not on the list can also be found by searching, and new tips are continuously updated.\n? <TIPBOX>Character<INFO>1001</INFO></TIPBOX>\n? <TIPBOX>Gameplay<INFO>1002</INFO></TIPBOX>\n? <TIPBOX>Communication<INFO>1003</INFO></TIPBOX>\n? <TIPBOX>The World of Ragnarok<INFO>4000</INFO></TIPBOX>",
	},
}

I've tried messing with stuff like the tip formatting, line breaks, tipbox internal links, number of pages, number of tips, lua functions that populate the actual tipbox table, and a bunch of other stuff, but I can't figure this out.

Edited January 9 by ckx_

[b1rbert]

Hey, I'm sorry if this might not be the solution you're looking for but I recently had the same problem when I went to langtype 0. for whatever reason having only one \n before a linked word caused it to look off. I fixed it by using \n\n to skip lines twice. it made it look really weird though since you had a lot of space between words with a link. I also realized that it has somehow to do with the tipbox file you are using. Re-downloading the file provided by Chris might just fix the problem.

I recently went back to langtype 1 and redownloaded the file and it looks fine again even with only one \n being used. couldnt figure out how to fully fix your problem either.

Another thing you could try which I didnt do yet is backup your current tipbox.lub and try changing the charset in notepad++ 

Option for that can be found in the bottom right corner. 

If you ever find the real solution to this problem I'd love to know.

[ckx_]

Thanks for the reply. I messed with langtypes but I couldn't get the results to change. Maybe it's a difference in our lua files or our clients. However, starting over with a new tipbox lub file seemed to help me, even when the file contents were nearly identical to my old one and both were set to EUC-KR encoding. Strange.

While it isn't a real solution, I did figure out the condition for which the misaligned text triggers, at least for me. When a tipbox's Page content has a link in it after a line that gets automatically wrapped by the tipbox, the text becomes misaligned.

For example:

So the best """solution""" I've found so far is adding explicit line breaks ( \n ) before any links that would get automatically wrapped.

Of course this doesn't cover cases like the one in my original post, which I think was fixed by replacing my tipbox file. These black box client issues really drive me crazy...

Edited January 13 by ckx_

[b1rbert]

Thank you for showing your "solutions"! The thing that fixed the tipbox for me was either using langtype 1 or funnily enough changing the font when using langtype 0. Do you also happen to have the problem where giving color to the words puts a spacebar in front of it? thats one of the problems I'm still facing.
Whats also weird is that before going to langtype 0 the ASCII256 symbols in the lub worked perfectly fine but going to langtype 0 and back to 1 just broke the entire thing. Like you wrote literally downloading a new one fixed that again for me even though the encoding never changed in the file. its all super scuffed for apperantly no real reason.