kayito MuEmu 0.97k: the source package, built step by step
One real package, read from its own files: folder structure, how the four servers and the client fit together, prerequisites, build and rebuild, configuration files, testing and common errors. Only the C# tool was built so far; every C++ step is marked.
Covers: kayito MuEmu 0.97k Full Package (MuEmu-0.97k-kayito-master.zip), README changelog up to Update 27, main base 0.97k (0.97.11) KOR.
1. What is confirmed and what is not
This lesson is about one real package, read from its own files. Each fact names the file that shows it, so you can open the file and check. Here is what was really done:
- Built and started for real: the C# tool
kayitoTools. It was built from source on a Windows 11 test PC on 12 November 2026 and ended with "Build succeeded, 0 Warning(s), 0 Error(s)". It started, showed a main window titled "kayito Tools" and closed normally. - Not built yet: the C++ programs
ConnectServer,JoinServer,DataServer,GameServer,InfoEncoderand the client DLLMain.dll. The test PC had an unfinished Visual Studio install, with no C++ compiler and no Windows SDK. Every C++ step below is marked To confirm with a real build. - Not started: no server, no client and no database was run, and nothing from the package was executed except
kayitoTools. - Not built:
kayitoEditor(the account and character editor). It needs more than the other tool, see part 5.
A step marked "To confirm" is the plan taken from the project files. Check it against your own files before you rely on it.
2. What the package is
- The file is
MuEmu-0.97k-kayito-master.zip(about 161 MB). Its top folder isMuEmu-0.97k-kayito-master\. - The first line of
README.mdreads "kayito MuEmu 0.97k Full Package". It names the emulator MuEmu and the main base 0.97k (0.97.11) KOR. - The README lists what is inside: the original client version 0.97, an encoder that generates the Main Info, a full MuEmu 0.97 server (ConnectServer, JoinServer, DataServer, GameServer), a tool to edit BMD and TXT files, a tool to edit accounts, characters and items, and the source code of all of it.
- "kayito" is the name on the package (README title, the batch file window titles,
LauncherName=Launcher - kayitoinEncoder\MainInfo.ini). It is not one program: the package holds a client DLL, an encoder, four servers and two tools. - The README is written in Spanish. It has a changelog from Update 1 to Update 27 and a "Fixes post-update" list. Update 19 says the project moved to GitHub. Update 23 says MySQL support was added in a parallel branch for JoinServer and DataServer.
- This lesson covers the package as it is described up to Update 27. A newer or older copy may differ.
- A different download,
MuEmu-0.97k-kayito CUSTOM by Siniestro.zip, holds onlyEncoder.zipandMuServer.zip. It has noSource\folder and is not covered here. - The zip has no licence file and the README names no licence. Ask the author before you share or sell anything made from it.
3. Folder structure
| Path in the package | What it holds |
|---|---|
Source\Client\Client.sln | Solution with the projects Main (the client DLL) and InfoEncoder |
Source\MuServer\MuServer_Ex097.sln | Solution with ConnectServer, JoinServer, DataServer, GameServer |
Source\MuServer\Dependencies\mysql-connector-8.0.33\ | MySQL Connector/C++ 8.0.33 headers and libraries, used by the MySQL configurations |
Source\Tools\kayitoTools\kayitoTools.sln | C# tool for the BMD and TXT files (README) |
Source\Tools\kayitoEditor\kayitoEditor.sln | C# tool for accounts, characters and items (README) |
MuServer\ | Ready server folders: ConnectServer\, GameServer\, MSSQL\, MySQL\, Data\, 1-STARTUP.bat, 2-SHUTDOWN.bat |
Client\ | The client Data\ folder (Local, Item, Player, Sound, World1 to World12 and more) |
Encoder\ | InfoEncoder.exe, MainInfo.ini, the Custom*.txt files, and a Client\ folder with main.exe, Main.dll and Data\Local\ClientInfo.bmd |
Main\ | main.exe and main.exe.idb |
Dependencies\C++ Redistributables 2017\ | VC_redist.x86.exe |
README.md | Contents and the changelog |
How big the C++ projects are (files without bin and obj): Main 51 cpp and 56 h, InfoEncoder 13 and 14, ConnectServer 16 and 18, JoinServer 18 and 21, DataServer 22 and 24, GameServer 98 and 100. ConnectServer is the smallest, so it is the natural first project to build.
The package also ships ready-made .exe files (for example MuServer\ConnectServer\ConnectServer.exe and MuServer\GameServer\GameServer.exe) and two .reg files. To learn how the source builds you do not need them. Never run or merge a file you have not checked.
4. How the modules fit together
| Module | What it does | Ports and links in the sample files |
|---|---|---|
ConnectServer | Reads ServerList.dat. Answers the client with the server list and with the address and port of the server the player picks (ConnectServerProtocol.cpp, lines 88 and 124 to 126). Logs "JoinServer offline" or "GameServer offline" when it does not hear from them (ServerList.cpp, lines 104 and 115). | TCP 44405 and UDP 55601 (ConnectServer.ini) |
JoinServer | Account login against the database. Keys in JoinServer.ini: CaseSensitive, MD5Encryption, GlobalPassword. Connects to ConnectServer over UDP. | TCP 55990 (JS_TCP_Port) |
DataServer | Database access for the game server. The source has a CharacterManager, a GuildManager, a Warehouse and a GoldenArcher module. | TCP 55980 (DS_TCP_Port) |
GameServer | The game itself. Reads Data\GameServerInfo - *.dat next to it and ..\Data\ for the game data. | TCP 55901 (ServerPort in GameServerInfo - StartUp.dat); connects to DataServer, JoinServer and the ConnectServer UDP port |
InfoEncoder | Offline tool. Reads MainInfo.ini and the Custom*.txt files and writes Client\Data\Local\ClientInfo.bmd (InfoEncoder.cpp, line 164). | none |
Main.dll | The client side. Exports EntryProc, reads Data\Local\ClientInfo.bmd, Data\Enc1.dat and Data\Dec2.dat (Main.cpp, lines 35 to 58). | dials the address in MainInfo.ini |
kayitoTools | Edits the BMD and TXT files (README, Forms\ folders: Dialog, Filters, Gate, Item, Monster, Quest, Skill, Text) | none |
1-STARTUP.bat starts the servers in this order, with a 2 second pause after each: ConnectServer, JoinServer, DataServer, GameServer. 2-SHUTDOWN.bat stops them in the same order with taskkill.
Settings that must agree in two files
| Setting | One file | The other file |
|---|---|---|
| Server code | ConnectServer\ServerList.dat, first column | GameServer\DATA\GameServerInfo - StartUp.dat, ServerCode |
| Game port | ServerList.dat, fourth column | GameServerInfo - StartUp.dat, ServerPort |
| Address the player's client is sent to | ServerList.dat, third column | It must be an address the client can reach |
| ConnectServer UDP port | ConnectServer.ini, ConnectServerPortUDP | JoinServer.ini, ConnectServerUDPPort, and ConnectServerPort in GameServerInfo - StartUp.dat |
| JoinServer port | JoinServer.ini, JS_TCP_Port | GameServerInfo - StartUp.dat, JoinServerPort |
| DataServer port | DataServer.ini, DS_TCP_Port | GameServerInfo - StartUp.dat, DataServerPort |
| Client version | Encoder\MainInfo.ini, ClientVersion | GameServerInfo - StartUp.dat, ServerVersion |
| Client serial | Encoder\MainInfo.ini, ClientSerial | GameServerInfo - StartUp.dat, ServerSerial |
| Address and port the client dials | Encoder\MainInfo.ini, IpAddress and IpAddressPort | ConnectServer.ini, ConnectServerPortTCP |
The comments in GameServerInfo - StartUp.dat say the same: server code and port "Sync with ConnectServer/ServerList", version and serial "Sync with Encoder/MainInfo". In the sample files the sample server code is 0 and the game port is 55901 in both places, and the client and server serial are the same 16 characters.
5. Prerequisites and dependencies
This is what the project files ask for. They name the build tools the projects request, not the Visual Studio the author used (the README has no build notes).
| Item | What the files say |
|---|---|
| Solution format | # Visual Studio 15 and VisualStudioVersion = 15.0.33919.361 at the top of Client.sln and MuServer_Ex097.sln |
| Platform toolset | <PlatformToolset>v141</PlatformToolset> in all six .vcxproj files (v141 is the Visual Studio 2017 toolset in Microsoft's naming) |
| Windows SDK | <WindowsTargetPlatformVersion>10.0.22621.0</WindowsTargetPlatformVersion> in all six |
| Platform | Win32 only. In MuServer_Ex097.sln the solution platform is called x86 and maps to Win32; in Client.sln it is Win32. There is no x64 configuration. |
| Configurations | Debug and Release. JoinServer and DataServer also have Debug_MySQL and Release_MySQL, which add the MYSQL define and the MySQL Connector paths. |
| Character set | MultiByte in all six |
| ATL | GameServer\stdafx.h, line 23, has #include <atltime.h> and BloodCastle.cpp line 817 uses CTime. ATL comes with Visual Studio, not with the Windows SDK. |
| C++ runtime | ConnectServer, GameServer and InfoEncoder use the static runtime (MultiThreaded). Main, JoinServer and DataServer use the DLL runtime (MultiThreadedDLL). |
| System libraries | User32, Gdi32, Shell32, Advapi32, Ole32, odbc32 (project files); ws2_32, dbghelp, iphlpapi, version, Rpcrt4, Opengl32, glu32, strmiids (#pragma comment(lib, ...) in stdafx.h and MP3.h) |
| MySQL | mysqlcppconn.lib (QueryManager.cpp, line 331), from Source\MuServer\Dependencies\mysql-connector-8.0.33\, only for the MySQL configurations |
| Build events | None. No PreBuildEvent, PostBuildEvent or CustomBuild in any .vcxproj or .csproj of the package. |
kayitoTools.csproj | TargetFrameworkVersion v4.0, WinExe, only framework references. The code uses C# 6 features, so the old C# 5 compiler of the .NET Framework fails (see part 9). |
kayitoEditor.csproj | TargetFrameworkVersion v4.8, LangVersion 7.3, 16 package references (MySql.Data 9.1.0 and more). The packages\ folder is not in the zip. |
What to install, to confirm with a real build: Visual Studio with the "Desktop development with C++" workload, and either the v141 tools plus the 10.0.22621.0 SDK that the files name, or a newer toolset after retargeting (part 6). For GameServer also ATL. The component names below come from the Visual Studio 2026 Community installer; other versions word them differently:
- "Desktop development with C++"
- "MSVC v141 - VS 2017 C++ x64/x86 build tools (v14.16)"
- "Windows 11 SDK (10.0.22621.0)"
- "C++ ATL for v141 build tools (x86 & x64)" (or "C++ ATL for x64/x86 (Latest MSVC)" when you build with the latest toolset)
- ".NET Framework 4.8 targeting pack" for
kayitoEditor
VC_redist.x86.exe in Dependencies\ is a runtime installer for running programs, not for building them. Its version info reads "Microsoft Visual C++ v14 Redistributable (x86) - 14.51.36247". Since three projects use the DLL runtime, a PC that runs those builds probably needs it (to confirm with a real run).
6. Build and rebuild
Unpack the zip into its own new, empty folder. In the commands, <PKG> means that folder plus MuEmu-0.97k-kayito-master.
The servers (C++), to confirm with a real build
- Open
<PKG>\Source\MuServer\MuServer_Ex097.slnin Visual Studio. - If Visual Studio offers to retarget the projects because v141 or the SDK is missing, either install them (part 5) or retarget and write down what you changed.
- Choose the configuration
Releaseand the platformx86. - Choose the database variant. The configurations
ReleaseandDebugbuildJoinServerandDataServerfor SQL Server through ODBC.Release_MySQLandDebug_MySQLbuild them for MySQL. - Build the solution. All four projects have a build entry for every solution configuration.
- Rebuild after a change in the same way. "Clean Solution" before it removes the old results. You can delete the
bin\folders to start clean, because there are no build events and the source files are not changed by a build.
Where the files are planned to land, read from OutDir in the project files:
| Project | Output folder under <PKG>\Source\MuServer\ |
|---|---|
| ConnectServer, GameServer | bin\Release\<ProjectName>\ |
| JoinServer, DataServer | bin\Release\MSSQL\<ProjectName>\ or bin\Release\MYSQL\<ProjectName>\ |
The intermediate files go to a second bin\... folder inside each project folder (IntDir).
The client DLL and the encoder (C++), to confirm with a real build
Open <PKG>\Source\Client\Client.sln, choose Release and Win32 and build. Main is a DynamicLibrary (a Main.dll) and InfoEncoder is a console Application. The output folders follow the same pattern: <PKG>\Source\Client\bin\Release\Main\ and ...\InfoEncoder\. Main.dll uses fixed memory addresses of the game client (Offsets.h, for example line 301), so it is written for one specific main.exe. The package carries one in Main\main.exe and Encoder\Client\main.exe (the same size and checksum in the zip). Use the client of the package, and do not assume another client works (to confirm).
kayitoTools (C#), built for real
This command built the tool on the test PC (the .NET Framework MSBuild with the C# compiler of a recent .NET SDK; replace 10.0.303 with the SDK version on your PC):
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe "<PKG>\Source\Tools\kayitoTools\kayitoTools\kayitoTools.csproj" /m:1 /p:Configuration=Release /p:Platform=AnyCPU "/p:CscToolPath=C:\Program Files\dotnet\sdk\10.0.303\Roslyn\bincore" /p:CscToolExe=csc.exeThe result was kayitoTools -> <PKG>\Source\Tools\kayitoTools\kayitoTools\bin\Release\kayitoTools.exe (1,636,864 bytes), "Build succeeded", 0 warnings, 0 errors, in about 1.4 seconds. Building from the Visual Studio window was not tried.
Retargeting on the command line, to confirm: the switches /p:PlatformToolset=v145 /p:WindowsTargetPlatformVersion=10.0 were accepted by MSBuild on the test PC, but no C++ build finished there. Whether this 2017-era code compiles with a newer toolset is not known.
7. Configuration files and source locations
| File in the package | Keys and what the code does with them |
|---|---|
MuServer\ConnectServer\ConnectServer.ini | [ConnectServerInfo] ConnectServerPortTCP (44405), ConnectServerPortUDP (55601), MaxIpConnection (10); [Log] LOG. Read in ConnectServer.cpp, lines 49 to 53. If a key is missing the code uses its own default (for example 55557 for the UDP port), so keep the key names exact. |
MuServer\ConnectServer\ServerList.dat | One line per server: code, name, address, port, type. A type other than "SHOW" hides the server (ServerList.cpp, line 69 and ConnectServerProtocol.cpp, line 115). The sample has one entry, "Server 1", on a private LAN address. |
MuServer\MSSQL\JoinServer\JoinServer.ini and MuServer\MySQL\JoinServer\JoinServer.ini | DataBaseODBC (MSSQL) or DataBaseHost, DataBasePort, DataBaseUser, DataBasePass, DataBaseName (MySQL); JS_TCP_Port, ConnectServerAddress, ConnectServerUDPPort; CaseSensitive, MD5Encryption (the file comment: 0 none, 1 Webzen, 2 default), GlobalPassword. |
MuServer\MSSQL\DataServer\DataServer.ini and the MySQL one | The same database keys, DS_TCP_Port, EnableSpecialCharacters, LOG. |
...\JoinServer\AllowableIpList.txt and ...\DataServer\AllowableIpList.txt | The addresses allowed to connect. The sample lists only 127.0.0.1. A connection from any other address is rejected without a message (SocketManager.cpp, line 647). Add the address of a GameServer that runs on another machine. |
MuServer\GameServer\DATA\GameServerInfo - StartUp.dat | ServerName, WindowName, ServerCode, ServerLock, ServerPort, ServerVersion, ServerSerial, ServerMaxUserNumber, the DataServer, JoinServer and ConnectServer address and port, and the log switches. The code takes characters 1, 3, 4, 6 and 7 of ServerVersion (ServerInfo.cpp, lines 387 to 391), so keep the form 0.97.11. |
MuServer\GameServer\DATA\GameServerInfo - Common.dat and the ChaosMix, Character, Command, Event, Skill files | Game rules, read in ServerInfo.cpp (lines 132 to 324). |
MuServer\Data\ | The game data the GameServer reads from ..\Data\ (Path.h): Item\, Monster\, Move\, Quest\, Shop\, Skill\, Event\, EventItemBag\, Util\ and more. The README names several of these files in its changelog, for example Item\ItemDrop.txt, Item\ItemStack.txt, Item\ItemValue.txt and Event\BonusManager.dat. |
Encoder\MainInfo.ini | [Connection] IpAddress, IpAddressPort, ClientSerial, ClientVersion; [ClientInfo] WindowName, DisableResets, DisableGrandResets; [CheckCRC] ClientName, PluginName; [Systems] ReconnectTime, HealthBarType, EnableMoveList, EnableSpecialCharacters. Read by InfoEncoder.cpp (lines 60 to 87). |
Encoder\*.txt | MapManager.txt, CustomGlow.txt, CustomItem.txt, CustomBow.txt, CustomWing.txt, ItemOption.txt, CustomMonster.txt, ItemPosition.txt, MapFog.txt, loaded by InfoEncoder.cpp (lines 93 to 109). |
MuServer\MSSQL\DB\CreateDatabase.sql, PoblateDatabase.sql and the MySQL pair | CreateDatabase.sql creates the database MuOnline97 with 16 tables (for example MEMB_INFO, Character, Guild, warehouse). PoblateDatabase.sql adds sample rows, including five sample accounts. |
MuServer\MSSQL\DB\MuOnline.reg and MuOnline64.reg | A registry file that defines the ODBC data source MuOnline97 (driver SQLSRV32.dll, server (local), database MuOnline97, trusted connection). MuOnline64.reg writes it under Wow6432Node, where 32-bit programs look on 64-bit Windows (to confirm). Read it first; a .reg file changes your registry. |
The sample files carry a sample database password and a sample GlobalPassword, and PoblateDatabase.sql adds sample accounts. Change or remove them before any server can be reached from outside.
Where the source for each setting lives: the .ini readers are in each project's *.cpp main file (ConnectServer.cpp, JoinServer.cpp, DataServer.cpp) and in GameServer\ServerInfo.cpp. The client's Protect.cpp loads a plugin DLL only when PluginName is filled in (CheckPluginFile returns at once when its stored checksum is 0, line 165).
The README (Update 27, Golden Archer) says that a table must be added and another changed, and that, if possible, you should create the database again from the scripts. Check the README changelog of your copy before you reuse an old database.
8. Testing the result
Test one program at a time, in this order. Everything except step 1 is to confirm with a real run.
- kayitoTools (done once). Start
kayitoTools.exefrom its ownbin\Releasefolder. On the test PC it showed the window "kayito Tools" and closed normally. Opening and saving real server files with it was not tested. - ConnectServer alone. It needs no database. Start it, then check the ports with
netstat -ano | findstr 44405(TCP) andnetstat -ano | findstr 55601(UDP). Close it afterwards. Note:SocketManager.cpp(line 152) andSocketManagerUdp.cpp(line 33) bind to all network cards (htonl(0)), so Windows will probably ask about the firewall. Use a PC where that is acceptable. - JoinServer and DataServer. They need the database first. For SQL Server: create the database with
CreateDatabase.sql, define the ODBC data source for 32-bit programs, then start them. They print "Could not connect to database" when the connection fails. For MySQL: buildRelease_MySQL, copy the three DLLs fromMuServer\MySQL\DataServer\(mysqlcppconn-9-vs14.dll,libssl-1_1.dll,libcrypto-1_1.dll) next to the programs, and fill in theDataBase*keys. - GameServer last. Watch its window for errors. Then look at the ConnectServer window: the "JoinServer offline" and "GameServer offline" lines should stop.
- The client. Edit
Encoder\MainInfo.iniso thatIpAddress,ClientVersionandClientSerialmatch your server. Put the client program intoEncoder\Client\under the name written inClientName(the sample saysMain.exe):InfoEncodertakes the checksum of.\Client\<ClientName>(InfoEncoder.cpp, lines 137 to 144) and stores it in the file it writes. RunInfoEncoder.exefrom theEncoder\folder and copyEncoder\Client\Data\Local\ClientInfo.bmdinto the client'sData\Local\folder. At start the client checks that its own file name equalsClientNameand that its checksum equals the stored one (Protect.cpp, lines 121 to 160), so run the encoder again after every change of the client program. Then start the client.
1-STARTUP.bat runs start /min /d ".\ConnectServer" ConnectServer.exe and the same for the other three, so each program must sit in MuServer\ConnectServer\, MuServer\JoinServer\, MuServer\DataServer\ and MuServer\GameServer\. In the zip, JoinServer and DataServer sit under MuServer\MSSQL\ or MuServer\MySQL\, so copy the variant you use up one level first. Keep the original programs as a backup before you replace them with your own build.
9. Common errors
Errors seen for real on 12 November 2026 (copied from the build logs):
| Message | When | What it means and the fix that worked |
|---|---|---|
error MSB3823: Non-string resources require the property GenerateResourceUsePreserializedResources to be set to true. (and MSB3822) | Building kayitoTools with dotnet msbuild | A classic .NET Framework WinForms project. Tested fix: use C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe. |
error CS1041: Identifier expected; 'static' is a keyword and error CS1518 | Building kayitoTools with the .NET Framework compiler alone | The code uses using static (C# 6) and that compiler is C# 5. Tested fix: /p:CscToolPath=...\Roslyn\bincore /p:CscToolExe=csc.exe. |
error CS1056: Unexpected character '$' | The same build | String interpolation (C# 6), same cause, same fix. |
warning MSB3088 about GenerateResource.Cache | A second build after a failed one | A cache left by the failed build. Tested fix: delete the project's obj\ folder and build again. |
Messages seen when a C++ project was built with dotnet msbuild on a PC with an unfinished Visual Studio. This is not the normal route, so treat them as pointers, not as proof of what happens in Visual Studio:
| Message | What it means |
|---|---|
error MSB4278: The imported file "$(VCTargetsPath)\Microsoft.Cpp.Default.props" does not exist | The C++ build files are not found. Build in Visual Studio or its Developer Command Prompt instead. |
error MSB8036: The Windows SDK version 10.0.22621.0 was not found. | That SDK is not installed. Install it or set Windows SDK Version to an installed one. |
error MSB8020: The build tools for Visual Studio 2017 (Platform Toolset = 'v141') cannot be found. | The v141 tools are not installed. Install them or retarget. |
warning MSB8003: The VCToolsInstallDir property is not defined | Check whether the compiler and the SDK folders exist at all. If not, install the C++ workload first. |
Messages written by the package's own programs (source lines given), with the first thing to check:
| Message | Where | First thing to check |
|---|---|---|
| "Read file incorrect or not exists" (message box) | Main.cpp, line 41 | Data\Local\ClientInfo.bmd is missing or not made by the InfoEncoder of this package |
| "Failed reading encoder and decoder files." | Main.cpp, line 58 | Data\Enc1.dat or Data\Dec2.dat missing in the client Data\ folder |
| "Failed on convert module file name!" | Protect.cpp, line 139 | The client program has another file name than ClientName in MainInfo.ini (the compare ignores upper and lower case) |
| "Client file CRC doesn't match!" | Protect.cpp, line 157 | The client program is not the one the encoder took the checksum of: put it in Encoder\Client\ and run InfoEncoder.exe again |
| "Could not connect to database" | JoinServer.cpp line 100, DataServer.cpp line 83 | The ODBC data source name or the DataBase* keys; the database exists |
WSAStartup() failed with error: ... | the main file of each server | A Windows networking problem, not a package problem |
| "[ServerList] JoinServer offline", "[ServerList] GameServer offline (name) (code)" | ServerList.cpp, lines 104 and 115 | The other program is not running, or its ports and addresses do not match (part 4) |
| A server connects but nothing happens | SocketManager.cpp, line 647 | The connecting address is not in AllowableIpList.txt; it is dropped silently |
| The server does not show in the client | ConnectServerProtocol.cpp, line 115 | The ServerList.dat type is not "SHOW", or the server is not alive |
Not seen yet, expected from the files: building GameServer without ATL should fail on atltime.h (to confirm).
10. What is still to confirm
- Install the C++ workload, then build
ConnectServerfirst and write down the exact toolset, SDK and result. - Build the other three servers,
Main.dllandInfoEncoder, with and without the MySQL configurations. - Run ConnectServer alone and check both ports. Then add the database and the other servers, one at a time.
- Build
kayitoEditor(it needs the .NET Framework 4.8 targeting pack and a NuGet restore). - Record screenshots of Solution Explorer, the retarget window and each server window. Until then this lesson has none.
Found something that does not match your copy of the package? Use the correction button below the lesson.
Related video tutorials
Found a mistake or a missing step?
Send a correction. A moderator checks it first; an approved correction earns Community Points under the rules on the Contribute page.



