Verzeltainne 1 Posted March 2, 2018 Does anyone bothered or already "Fixed" the "SMALL FONT" when using the newer clients? (2018-02-13aRagexeRE) kinda frustrated how it hurts my eyes so much just looking at it. /heh Share this post Link to post Share on other sites
WhiteEagle 6 Posted March 2, 2018 Does anyone know how to translate this? Share this post Link to post Share on other sites
4144 366 Posted March 2, 2018 @WhiteEagle This green message from msgstringtable. If you using hercules, you can disable information about players on server. Share this post Link to post Share on other sites
4144 366 Posted March 2, 2018 11 hours ago, melv0 said: sir, do you play RO in Linux ?? yes Share this post Link to post Share on other sites
WhiteEagle 6 Posted March 3, 2018 15 hours ago, 4144 said: @WhiteEagle This green message from msgstringtable. If you using hercules, you can disable information about players on server. Thanks sir. I am using herc and rathena. Good to know that can be disabled at herc. If I found the right line to translate, I'll share it here. Share this post Link to post Share on other sites
DevilcrossIT 0 Posted March 3, 2018 (edited) 22 hours ago, DevilcrossIT said: I only tested with 2017-12-13bRagexeRE up to 2018-02-13aRagexeRE and it force has stopped working. for [Ragexe] 2017-12-13bRagexe, 2018-01-31Ragexe it crash and show up Error Handler. UPDATE : "2017-12-06aRagexeRE" look fine but after "2017-12-13bRagexeRE" it crash (still used old UI) New UI started from "2018-01-24bRagexeRE" onwards. PS: can't patches Remove Hourly Announce since 2017-11-08bRagexeRE. Edited March 3, 2018 by DevilcrossIT Share this post Link to post Share on other sites
Verzeltainne 1 Posted March 3, 2018 (edited) Everyone is not having the same issue like mine. but I use the updated clean KRO. and I'm using Secrets NEMO and 4144's recommended NEMO. I revert back to 2017 client still on very small fonts. Also did KRO removes the Booking button on RO Menu? Additional Bug Encountered: OptionData is not Saving when you open a new client session. Sharing these problems I encountered. In some aspects. 2018 runs perfectly but still has a lot of bugs that I didn't encounter yet. Thanks for the heads up everyone especially @4144, @Ridley Patch Used: Quote 3 Chat Flood Remove Limit 8 Custom Window Title 9 Disable 1rag1 type parameters (Recommended) 13 Disable Ragexe Filename Check (Recommended) 16 Disable Swear Filter 19 Enable Title Bar Menu 20 Extend Chat Box 21 Extend Chat Room Box 22 Extend PM Box 23 Enable /who command (Recommended) 24 Fix Camera Angles (Recommended) 33 Always Call SelectKoreaClientInfo() (Recommended) 34 Enable /showname (Recommended) 35 Read Data Folder First 36 Read msgstringtable.txt (Recommended) 37 Read questid2display.txt (Recommended) 38 Remove Gravity Ads (Recommended) 39 Remove Gravity Logo (Recommended) 40 Restore Login Window (Recommended) 41 Disable Nagle Algorithm (Recommended) 44 Translate Client (Recommended) 46 Use Normal Guild Brackets (Recommended) 47 Use Ragnarok Icon 48 Use Plain Text Descriptions (Recommended) 49 Enable Multiple GRFs (Recommended) 50 Skip License Screen 53 Use Ascii on All LangTypes (Recommended) 64 @ Bug Fix (Recommended) 65 Load Custom lua file instead of iteminfo*.lub (Recommended) 69 Extend Npc Dialog Box 75 Enable Flag Emoticons 84 Remove Serial Display (Recommended) 88 Allow space in guild name 90 Enable DNS Support (Recommended) 91 Disconnect to Login Window 96 Remove GM Sprites 97 Cancel to Login Window (Recommended) 98 Disable dc_scream.txt 99 Disable ba_frostjoke.txt 204 Increase Attack Display 208 Restore Cash Shop Icon 213 Disable Help Message on Login (Recommended) Edited March 3, 2018 by Archetype Saber Lack of Info Share this post Link to post Share on other sites
Verzeltainne 1 Posted March 3, 2018 1 hour ago, DevilcrossIT said: UPDATE : "2017-12-06aRagexeRE" look fine but after "2017-12-13bRagexeRE" it crash (still used old UI) New UI started from "2018-01-24bRagexeRE" onwards. PS: can't patches Remove Hourly Announce since 2017-11-08bRagexeRE. Remove Hourly Announce can't be used from Client Dates 2017-11-08 and Up. on 2017-05-17 everything works fine. Share this post Link to post Share on other sites
Keru 3 Posted March 4, 2018 Is there any clean client version from the 2013-08-07 exe? It should been one of the most popular and stable versions, but i could only find pre-diffed versions and there seems no way to enable packet obfuscation again. Share this post Link to post Share on other sites
tiagofm94 1 Posted March 4, 2018 Sorry but someone could help me with this error Share this post Link to post Share on other sites
Maple 6 Posted March 5, 2018 (edited) @Asheraf By any chance, why are these numbers appearing? He changes numbers every time he relogs... Obs: I've already looked at msgstringtable. I tried to change again for what you use Git, and also tried to use Zack's Edited March 5, 2018 by Dream Catcher Share this post Link to post Share on other sites
Verzeltainne 1 Posted March 5, 2018 2 hours ago, Dream Catcher said: @Asheraf By any chance, why are these numbers appearing? He changes numbers every time he relogs... Obs: I've already looked at msgstringtable. I tried to change again for what you use Git, and also tried to use Zack's msgstring maybe? bwt, what client date did you use? your fonts seems no problem. Share this post Link to post Share on other sites
Maple 6 Posted March 5, 2018 9 minutes ago, Archetype Saber said: msgstring maybe? bwt, what client date did you use? your fonts seems no problem. data (https://github.com/Asheraf/Translation) client 2018-02-13 Share this post Link to post Share on other sites
Verzeltainne 1 Posted March 5, 2018 48 minutes ago, Dream Catcher said: data (https://github.com/Asheraf/Translation) client 2018-02-13 try to use the msgstring from secretdataz. Share this post Link to post Share on other sites
Maple 6 Posted March 5, 2018 2 hours ago, Archetype Saber said: try to use the msgstring from secretdataz. already tried Share this post Link to post Share on other sites
4144 366 Posted March 5, 2018 @Dream Catcher can you show whole string under cursor? I cant find it in msgstringtable. Probably issue in this string. Share this post Link to post Share on other sites
Maple 6 Posted March 5, 2018 2 minutes ago, 4144 said: @Dream Catcher can you show whole string under cursor? I cant find it in msgstringtable. Probably issue in this string. Line: 3305 msgstringtable Ash... https://github.com/Asheraf/Translation/blob/master/data/msgstringtable.txt#L3305 msgstringtable Zack... https://github.com/zackdreaver/ROenglishRE/blob/master/data/msgstringtable.txt#L3305 Share this post Link to post Share on other sites
4144 366 Posted March 5, 2018 In screenshot i see "ar ROP'". I mean this string. Share this post Link to post Share on other sites
Maple 6 Posted March 5, 2018 (edited) 17 minutes ago, 4144 said: In screenshot i see "ar ROP'". I mean this string. I translated into Portuguese, "Use Free points" = "Usar ROP's" Edited March 5, 2018 by Dream Catcher Share this post Link to post Share on other sites
Asheraf 123 Posted March 5, 2018 8 hours ago, Dream Catcher said: @Asheraf By any chance, why are these numbers appearing? He changes numbers every time he relogs... Obs: I've already looked at msgstringtable. I tried to change again for what you use Git, and also tried to use Zack's You need to make sure the msgstringtable is saved in the correct encoding of whatever language used in there, for example if you're using the one from my repository you have to save it as EUC-KR unless you translated everything. (ps: im keeping it UTF-8 in the repo so its readable in the github diffs) Share this post Link to post Share on other sites
Maple 6 Posted March 5, 2018 1 minute ago, Asheraf said: You need to make sure the msgstringtable is saved in the correct encoding of whatever language used in there, for example if you're using the one from my repository you have to save it as EUC-KR unless you translated everything. (ps: im keeping it UTF-8 in the repo so its readable in the github diffs) I use ANSI, so the text accents work in langtype 12 (brazil) Share this post Link to post Share on other sites
Asheraf 123 Posted March 5, 2018 8 minutes ago, Dream Catcher said: I use ANSI, so the text accents work in langtype 12 (brazil) for Brazil i believe you need to use ISO-8859-1, not sure tho. Share this post Link to post Share on other sites
Maple 6 Posted March 5, 2018 2 minutes ago, Asheraf said: for Brazil i believe you need to use ISO-8859-1, not sure tho. even using ISO-8859-1, that number still appears Share this post Link to post Share on other sites
Verzeltainne 1 Posted March 6, 2018 On 3/3/2018 at 9:17 PM, Archetype Saber said: Everyone is not having the same issue like mine. but I use the updated clean KRO. and I'm using Secrets NEMO and 4144's recommended NEMO. I revert back to 2017 client still on very small fonts. Also did KRO removes the Booking button on RO Menu? Additional Bug Encountered: OptionData is not Saving when you open a new client session. Sharing these problems I encountered. In some aspects. 2018 runs perfectly but still has a lot of bugs that I didn't encounter yet. Thanks for the heads up everyone especially @4144, @Ridley Patch Used: Regarding to these/this Matter. I already found out the problem it seems the langtype 2018 clients only accepts is 0. coz' if I tried to use Langtype 1 on a Patched 2018 Client and error occurs ("nil val something") and it seems the custom clientinfo.xml patch on NEMO doesn't work on 2018 Client. too much bug and errors on the new clients. if you're planning to release this on public it wont be an advisable decision. if you want stability use client dates under 2016. as of now I currently tinkering on 2017-05-17 seems less buggy. Thanks for the Info everyone. Share this post Link to post Share on other sites
kevingunadi 0 Posted March 6, 2018 4 hours ago, Archetype Saber said: Regarding to these/this Matter. I already found out the problem it seems the langtype 2018 clients only accepts is 0. coz' if I tried to use Langtype 1 on a Patched 2018 Client and error occurs ("nil val something") and it seems the custom clientinfo.xml patch on NEMO doesn't work on 2018 Client. too much bug and errors on the new clients. if you're planning to release this on public it wont be an advisable decision. if you want stability use client dates under 2016. as of now I currently tinkering on 2017-05-17 seems less buggy. Thanks for the Info everyone. langtype 1 Spoiler Spoiler Spoiler Share this post Link to post Share on other sites