Most visitors online was 12542 , on 28 Apr 2024
Join our community of MMO enthusiasts and game developers! By registering, you'll gain access to discussions on the latest developments in MMO server files and collaborate with like-minded individuals. Join us today and unlock the potential of MMO server development!
Join Today!Build='Debug'. Besides, there are Release, FinalRelease, and so on. For now, only Debug works.In the *.xml settings of each of the servers that launched what is indicated in the value build="???" and what is the access level of your account?
Yes, I have already fixed the issue and so much appreciate it. But exactly, there are two reasons.To access the server in debug mode, you need at least master access level
Do you by any chance have the contents of the BaseLock.pack file in the unpacked form of client 4.0? I would be very grateful to youYes, I have already fixed the issue and so much appreciate it. But exactly, there are two reasons.
1st, as mentioned above, you must have an account with Master Level for Debug build.
2nd, The files in Client/data/Packs must be consistent with files in Server/data/Packs. And the [Bin.pak] you may get from somewhere else.
Hoping this will help more people.
I did not find the BaseLock.pack in client 4.0, could you give me the straight path of this file. Or just tell me how to find this file.Do you by any chance have the contents of the BaseLock.pack file in the unpacked form of client 4.0? I would be very grateful to you
Yes, the picture shows the correct file. I accidentally misspelled the name in the post above.I did not find the BaseLock.pack in client 4.0, could you give me the straight path of this file. Or just tell me how to find this file.
View attachment 240284
Here you are. Only available in 7 days.Yes, the picture shows the correct file. I accidentally misspelled the name in the post above.
I apologize, apparently, either I wrote it incorrectly or the translator translated it that way. Thank you very much, but I meant the result of processing by the unpacker. But anyway, thank you for your time.
It doesn't matter.I apologize, apparently, either I wrote it incorrectly or the translator translated it that way. Thank you very much, but I meant the result of processing by the unpacker. But anyway, thank you for your time.
There are *.bin files and, unfortunately, they cannot be opened by the archiver. It uses a special unpacker.It doesn't matter.
As far as I know, you can just use 7z to unpack it. As the snapshot shows below.
View attachment 240402
Yes, they are *.bin files. I didn't have the unpack tools. Maybe you can search it by google. All my tools are acquired by this community. Maybe someone else has the tool.There are *.bin files and, unfortunately, they cannot be opened by the archiver. It uses a special unpacker.
I would be very happy if someone found an unpacker for 4.0. But this is fantasy and it doesn't happen.Yes, they are *.bin files. I didn't have the unpack tools. Maybe you can search it by google. All my tools are acquired by this community. Maybe someone else has the tool.
I think so. But we can change the *.xdb files.I would be very happy if someone found an unpacker for 4.0. But this is fantasy and it doesn't happen.
What has changed since you created the first account and the second?I think so. But we can change the *.xdb files.
Now I meet a problem. I change the server build to Release/Final Release. Account with User level still can't see the server and only Master account can access the server. Tried so many times and can't fix it.
I changed the xdb settings of Release, FinalRelease, Release.prototype, FinalRelease.prototype. Because the original setting can't start the server normally.What has changed since you created the first account and the second?
This is just a hypothesis, but it seems to me that in the process of editing you may have corrected something wrong. And why didn't they immediately take a working 7.0? Why all these difficulties?I changed the xdb settings of Release, FinalRelease, Release.prototype, FinalRelease.prototype. Because the original setting can't start the server normally.
About the shared.xml, I change the IP to 127.0.0.1 and refine the ports.
About the database of master, I created the shared config in shared table.
I think all my changes are not the root cause.
Do you download or use the 7.0 server?