[All] KAMI
- Skydrite
- Wisp
- Posts: 11
- Joined: Mon 2016.06.27, 00:58
- Honor: 0
- Points: 89.10
- BDO: Plum
- Gender: Male
- :
- Medals: 1
Re: [JP] KAMI JP
So, now the same thing that happens at kr, now is on at JP, what you will do to force read the HUD strings?
- KAMIKADzE
- KAMIKADzE
- Blood Mage
- Posts: 3911
- Joined: Thu 1998.01.01, 00:00
- Honor: 3104
- Points: 2423437203.90
- BDO: Blader
- Cabal: BL
- Vindictus: Lann
- C9: Blade Dancer
- Gender: Male
- Karma: 神風
- :
- Medals: 17
- Contact:
Re: [JP] KAMI JP
Updated to v2.12.
Launcher v0.7 will have it all sorted out I guess. Meanwhile, if you've used KAMI JP with Launcher - use JP v2.12 instead. Before patching your client read the text in first post regarding this issue.
You can still use KAMI JP for merging and stuff, then simply replace JP v2.12 files with the resulted files in the corresponding folder. If you'll have any troubles - let me know. Of course you can use some other translation instead.
Skydrite wrote:So, now the same thing that happens at kr, now is on at JP, what you will do to force read the HUD strings?
Launcher v0.7 will have it all sorted out I guess. Meanwhile, if you've used KAMI JP with Launcher - use JP v2.12 instead. Before patching your client read the text in first post regarding this issue.
You can still use KAMI JP for merging and stuff, then simply replace JP v2.12 files with the resulted files in the corresponding folder. If you'll have any troubles - let me know. Of course you can use some other translation instead.
- Margo
- Acolyte
- Posts: 46
- Joined: Thu 2016.10.06, 09:43
- Honor: 5
- Points: 164.60
- BDO: Tamer
- :
- Medals: 1
Re: [JP] KAMI JP
Works fine, but I hope to see the updated launcher. 

- Skydrite
- Wisp
- Posts: 11
- Joined: Mon 2016.06.27, 00:58
- Honor: 0
- Points: 89.10
- BDO: Plum
- Gender: Male
- :
- Medals: 1
Re: [JP] KAMI JP
KAMIKADzE wrote:Updated to v2.12.Skydrite wrote:So, now the same thing that happens at kr, now is on at JP, what you will do to force read the HUD strings?
Launcher v0.7 will have it all sorted out I guess. Meanwhile, if you've used KAMI JP with Launcher - use JP v2.12 instead. Before patching your client read the text in first post regarding this issue.
You can still use KAMI JP for merging and stuff, then simply replace JP v2.12 files with the resulted files in the corresponding folder. If you'll have any troubles - let me know. Of course you can use some other translation instead.
The new launcher so we can edit the pad meta and the font? or do you use another software to change font format?
- KAMIKADzE
- KAMIKADzE
- Blood Mage
- Posts: 3911
- Joined: Thu 1998.01.01, 00:00
- Honor: 3104
- Points: 2423437203.90
- BDO: Blader
- Cabal: BL
- Vindictus: Lann
- C9: Blade Dancer
- Gender: Male
- Karma: 神風
- :
- Medals: 17
- Contact:
Re: [JP] KAMI JP
Skydrite wrote:KAMIKADzE wrote:Updated to v2.12.Skydrite wrote:So, now the same thing that happens at kr, now is on at JP, what you will do to force read the HUD strings?
Launcher v0.7 will have it all sorted out I guess. Meanwhile, if you've used KAMI JP with Launcher - use JP v2.12 instead. Before patching your client read the text in first post regarding this issue.
You can still use KAMI JP for merging and stuff, then simply replace JP v2.12 files with the resulted files in the corresponding folder. If you'll have any troubles - let me know. Of course you can use some other translation instead.
The new launcher so we can edit the pad meta and the font? or do you use another software to change font format?
Yes to both meta and font. You don't need any programs to change font you can simply replace the font that comes in my package with any other ".ttf" font.
Re: [JP] KAMI JP
KAMIKADzE wrote:Updated to v2.12.Skydrite wrote:So, now the same thing that happens at kr, now is on at JP, what you will do to force read the HUD strings?
Launcher v0.7 will have it all sorted out I guess. Meanwhile, if you've used KAMI JP with Launcher - use JP v2.12 instead. Before patching your client read the text in first post regarding this issue.
You can still use KAMI JP for merging and stuff, then simply replace JP v2.12 files with the resulted files in the corresponding folder. If you'll have any troubles - let me know. Of course you can use some other translation instead.
It is possible to make this program separately from bdo patcher?
This update has come for Russia. Then, this update will come to Europe and Taiwan. Sooner or later.
http://black-desert.com/forums/index.ph ... #post86262
- KAMIKADzE
- KAMIKADzE
- Blood Mage
- Posts: 3911
- Joined: Thu 1998.01.01, 00:00
- Honor: 3104
- Points: 2423437203.90
- BDO: Blader
- Cabal: BL
- Vindictus: Lann
- C9: Blade Dancer
- Gender: Male
- Karma: 神風
- :
- Medals: 17
- Contact:
Re: [JP] KAMI JP
buzarini wrote:KAMIKADzE wrote:Updated to v2.12.Skydrite wrote:So, now the same thing that happens at kr, now is on at JP, what you will do to force read the HUD strings?
Launcher v0.7 will have it all sorted out I guess. Meanwhile, if you've used KAMI JP with Launcher - use JP v2.12 instead. Before patching your client read the text in first post regarding this issue.
You can still use KAMI JP for merging and stuff, then simply replace JP v2.12 files with the resulted files in the corresponding folder. If you'll have any troubles - let me know. Of course you can use some other translation instead.
It is possible to make this program separately from bdo patcher?
This update has come for Russia. Then, this update will come to Europe and Taiwan. Sooner or later.
http://black-desert.com/forums/index.ph ... #post86262
Of course it is possible, but why to? I even can't find the time to finally update the Launcher with that.
By the way I see that you've written there that RU updater checks both meta and PAZs before the start, if that is so then it might be tricky. As far as I know RU launcher/updater is their own "steam" version with proprietary anti-hacking stuff and spyware (if I'm correctly aware then there is almost 0% chance that I'll ever try to make "custom updater/launcher" for RU version, since it would require replicating their crapware and what it sends to the server). Have you tried to replace meta before the game starts but after the updater checks it?
Currently I know about 2 ways in which full translation can be done:
1) External. Requires changing meta file. (will be added in v0.7)
2) Internal. Requires changing meta and PAZs files. (will be added in some future release)
So if it rechecks files before start, and you can't change meta on the fly, then you can forget about the language patching, other than the languageadata.
Re: [JP] KAMI JP
KAMIKADzE wrote:buzarini wrote:KAMIKADzE wrote:Updated to v2.12.Skydrite wrote:So, now the same thing that happens at kr, now is on at JP, what you will do to force read the HUD strings?
Launcher v0.7 will have it all sorted out I guess. Meanwhile, if you've used KAMI JP with Launcher - use JP v2.12 instead. Before patching your client read the text in first post regarding this issue.
You can still use KAMI JP for merging and stuff, then simply replace JP v2.12 files with the resulted files in the corresponding folder. If you'll have any troubles - let me know. Of course you can use some other translation instead.
It is possible to make this program separately from bdo patcher?
This update has come for Russia. Then, this update will come to Europe and Taiwan. Sooner or later.
http://black-desert.com/forums/index.ph ... #post86262
Of course it is possible, but why to? I even can't find the time to finally update the Launcher with that.
By the way I see that you've written there that RU updater checks both meta and PAZs before the start, if that is so then it might be tricky. As far as I know RU launcher/updater is their own "steam" version with proprietary anti-hacking stuff and spyware (if I'm correctly aware then there is almost 0% chance that I'll ever try to make "custom updater/launcher" for RU version, since it would require replicating their crapware and what it sends to the server). Have you tried to replace meta before the game starts but after the updater checks it?
Currently I know about 2 ways in which full translation can be done:
1) External. Requires changing meta file. (will be added in v0.7)
2) Internal. Requires changing meta and PAZs files. (will be added in some future release)
So if it rechecks files before start, and you can't change meta on the fly, then you can forget about the language patching, other than the languageadata.
I would like to give the user a choice. As for the week go a lot of small updates. It is necessary each time to re-patch the meta file. The user himself must decide, and to follow this.
I know that is possible to use "meta injector" during start-up, but this option is not the best.
Who is online
Users browsing this forum: No registered users and 3 guests