1. Reasons for not being able to open the door:
a. The "server1name=ktest" in the client's ftp.ini has been modified. Please restore this section or change it to match the name on the server side (mir200/!setup.txt). Note: This is actually the server name you enter after opening the game.
b. The server's IP is not set correctly. The IPs in all five files are 127.0.0.1. If debugging locally, leave it as is; if debugging over a network, change it to your machine's IP address (in Win9x, run winipcfg to see the IP address).
2. Unable to register an account:
a. This issue is complex and could be due to the server's IP not being set correctly or an issue with DBC. First, try registering again. If it still doesn't work, delete the HeroDB field and recreate it. If that still fails, uninstall all server-side software and reinstall it. It’s a bit clumsy, but it's the only way I know.
b. When creating an ID or character, illegal characters are prompted. All registration information must be in English, though Korean can also be attempted. Be sure not to use spaces or illegal characters, fill in all fields, and try several times.
3. Black screen after entering:
a. Version issues with mir.exe and mir.dat. Use the client files provided in the private server package whenever possible.
b. After pressing the prompt window, black screen appears: Reinstall the client. You probably installed too many cheats. :)
c. DirectX version issue.
d. Machine configuration problem. Some machines cannot simultaneously act as both client and server (even a Leiniu 1200XP+ with 512MB DDR memory struggles).
e. Map issue (copy the map from server\Mir200\Map to the client).
4. Cannot find BDEadministrator in the Control Panel:
a. A method recently discovered by zigzag from Uprising Community, thank you for your efforts. Find BDEADMIN.EXE in C:\Program Files\Common Files\Borland Shared\BDE and run it directly. If you can't find it, search for BDEADMIN.EXE on drive C.
b. The reason is that you installed Office, which includes something like DB data source that conflicts with this. Uninstall Office. It's said that some charting or image software also conflicts, so please uninstall those as well. Also, note that after installing database software, you must use a crack tool to activate it, otherwise it won't work. The crack tool can be downloaded from the relevant thread. If none of the above methods work, you may need to reinstall the operating system.
c. DB2000 seems to have two versions. One is about 3MB, the other is about 7MB. The 3MB one is version 3.5, and the 7MB one is version 5+. Download the 7MB one, the 3MB one is not recommended.
5. Screen flashes and exits after entering:
a. Have you replaced the mir.dat in c:\mirserver\mir200? Just switch it back. Remember to use the one that is around 700k.
6. Cannot create a character:
a. Definitely a client issue. Replace the client's mir.dat with the one from c:\mirserver\mir200 that is around 700k. Check the IP addresses carefully in mir.ini and mirsetup.ini. If it still doesn't work, find a clean Legend client v1.0 and reinstall it. As for why the UNKOWN error occurs, it is suggested to change the name to English.
b. The RUN30 file hasn't run properly, causing this error. Restart your computer.
7. Issues running private servers under XP:
a. Cannot run M2Server.exe. Solution: Stop the SSDP Discovery Service in Administrative Tools > Services.
b. After using the above method to run M2Server.exe, it keeps showing "Not ready 127.0.0.1". Solution: Unknown, please help.
c. Black screen after creating a character and entering the game. Solution: This might be caused by M2Server.exe failing to read game information properly, i.e., the previous issue. Please help resolve this. Currently, everyone seems to be encountering these problems. If the above solutions don't work, try the methods used for Win98.
Problems after entering the game:
1. GM operation issues:
a. First, enter GM mode by typing @gamemaster. Clone items with @make, e.g., clone Dragon Slayer with @make dragonslayer. Clone monsters with @mob, e.g., clone Evil Snake with @mob evilsnake. Teleport someone with @recall, e.g., teleport a player named king to you by typing @recall king. These are the commonly used commands.
b. The names of GMs are recorded in C:\mirserver\Mir200\Envir\AdminList. You can modify them yourself! Then log in with the modified name and type @GameMaster to enter GM mode. The GM commands are located in C:\mirserver\Documents\COMMANDS. We should study them together. I still have a lot of questions. Please help!
c. The reason for not being able to enter GM mode is that the AdminList.txt in Mir200\Envir contains the character names, not login IDs.
2. No monsters spawn, or they don't attack:
a. Place the monster refresh file Mongen.txt in c:\mirserver\mir200\envir. Is Mongen.txt empty? Use the content from mongen******.txt instead of the empty one.
b. Even after replacing the file, monsters still don't spawn or move: This is likely due to poor machine performance. Using MongenHighlevel.txt doesn't spawn monsters, while MongenOriginal.txt spawns them but they don't move. I edited the file, deleted unnecessary spawn locations, and now only Pig Cave, Zuma, Wuma, and Bai*men have monsters. This is the limit of my P3 733 machine. Adding more would result in unresponsive monsters.
c. New solution for monsters not attacking or spawning: Cover the private server's mir.dat file with the latest Legend mir.dat file. Enter the game, and if the monsters don't attack you, exit and re-enter the game. The monsters will automatically respawn! I tested this on a computer with average configuration, and it worked fine.
d. The reason monsters disappear after a few minutes in single-player mode is insufficient memory. The solution is to increase the memory to 256MB.
3. Unable to input Chinese or switch input methods. Using paste results in Korean text. However, my machine works perfectly. It's likely a Windows language code issue. Even when my friend copied my entire Legend client, the same issue occurred.
4. Solutions for lagging private servers:
a. Open and modify the !setup file in mirserver\Mir200. Change the TestServerUserLimit= item, which limits the number of users on the server. If there are too many users, the server will lag. The default value is around 5600, which is very laggy.
b. Delete small monsters such as chickens, sheep, dogs, deer, orcs, cats, snakes, spiders, and horn flies. Close areas like the Half-Orc Tomb, Centipede Cave, Mine Cave (two of them), and Connection Tunnel. This should significantly improve performance. Ground items also consume resources. For details on how to modify, check the forum.
Methods for Chinese localization of private servers:
1. Use DB Commander 2000 PRO to modify the three .db data files in mud2. Change the English names to Chinese ones and adjust item properties.
2. Copy the files in markit_def/other/chinese to markit_def. This will make NPC dialogues appear in Chinese (not all).
3. In Mir200\Envir\MapInfo.txt, change the English map names to Chinese. You can also modify the paths to Pig Seven and Zuma Seven here. For example, D71601 37,35 -> D716 36,17 `````````` Stone Tomb Entrance Pig Six. Entering the Stone Tomb at 37, 35 will take you directly to Pig Six.
4. Modify the monster names in Mongen.txt to Chinese (uncertain, haven't tried yet, but it should work).
5. Use a Chinese client. I have the Half-Moon Through People version with jump checks, but the server isn't great, so it might not be downloadable. Common issues include bundles of medicine or random items disappearing when opened... Super monsters not dropping loot. The text files in mir200\Envir\MonItems correspond to the drop rates of each monster. Since you've changed the monster names but haven't updated these text files, the drops definitely won't occur. There might be a text file related to medicine packs that takes away the pack and gives you six medicines when opened. The reason is probably that not all changes were made. Change the item names in the MonItems directory to Chinese.
IP Addresses Found Online Cannot Be Accessed
Due to the illegality of private servers, most private server IPs are frequently changed. Therefore, it's generally not advisable to join personal servers that change locations frequently. Instead, try to find one or a few large-scale private server providers and remember their stable IPs for long-term use.