I think i might have....overestimated myself.....getting this freshly setup on my secondary PC...is much harder for me than i thought LOL.
Time to fight it through today and see where it gets me xD
I think i might have....overestimated myself.....getting this freshly setup on my secondary PC...is much harder for me than i thought LOL.
Time to fight it through today and see where it gets me xD
someone testing a party maching group is not created for some reason
Yes, I did but the error didn't go away.
- - - Updated - - -
![]()
pls reupload client with Google Drive
About missing translation strings. The problem is that the strings are in different files of TW and EUR DCs for some elements.
Spoiler:
The xml-translator needs to be updated so that it supports the function of manipulating strings from different files (for certain elements, like QuestDialog). This shouldn't be a problem, as we use the zone/npc/dialog id as the signature.
I have a working server 2022 VM in english. It's hosted in vSphere, so I'd have to export as an OVA/OVF if that would work for you?
- - - Updated - - -
I managed to get it done up on a fresh machine. I ran into so many tiny gotchas (because dumb) I cant even remember em all. Feel free to ping me if you get stuck!
- - - Updated - - -
So I managed to migrate the PlanetDB to MySQL with this:
https://www.mysql.com/products/workbench/migrate/
I haven’t gotten a chance to test how the server responds to the change yet though. The db definitions might be an issue as @hsdn mentioned. Stored procedure/trigger creation syntax is different between the server types
This would actually be cool! I only started working with the server files today (starting with the distributed VM first). After adding/changing the display language + switching regional settings, there's still a lot of Chinese language only stuff still deeply embedded in various places (I ran into that when double checking roles & features in IIS). Got it working quickly but didn't think it was a good base to start off from and so was planning to try from scratch (which I know is a landmine of "tiny little cuts" of those small things that you overlook, and block you from proceeding as you try to resolve the thing that you missed).
I updated xml-dc-translator utility: https://github.com/justkeepquiet/xml-dc-translator
Double text issue have been fixed, and the search algorithm is completely reworked.
I think now the utility translates of all DC strings (I did not find the Chinese word in the translated DC).
Of course, missing item names will need to be added manually.
Last edited by hsdn; 24-05-22 at 07:07 PM.
CN strings not deleted. It have all been completely replaced.
But if in the EUR DC strings are empty, then in the translated DC is will also replaced to empty.
Of course, you can leave the original text for such lines (prevent replacing lines with empty ones).
UPD: Fixed.
Last edited by hsdn; 24-05-22 at 07:06 PM.
lol. I had way too many of those sort of moments when I was working fulltime in tech (Murphy's Law); so I ended up with this habit of documenting everything (and still ran into networking scenarios where undoing what I did step-by-step didn't fix it and I'd be like this ->)
But thanks in advance for the export; really appreciate it! (I'm going to import into regular VMWare Workstation but have no idea if they updated the import facility in Workstation 16; I know with Workstation 15, you could only import version 1 OVA/OVF's and well, VMWare's knowledge base is the typical IT landmine of non-specific answers).
I know the feeling, spent the whole day trying to set this up on a secondary PC i have and still got nowhere near..... ;/ wish someone could jsut remote to it and set it up explaining to me what and where or guiding me. Would make it so much better lol