---

Overview

Npcgen2CoordData is a small Windows Forms utility that imports mob and resource spawn coordinates from a Perfect World style npcgen.data binary file and merges them into a tab-separated coord_data.txt file used by related server tooling.

The tool provides three main actions through a single form:

• Load coord_data — read an existing coord_data.txt into memory.
• Import npcgen.data — select a server maps root folder using FolderBrowserDialog. The tool scans every immediate subfolder for an npcgen.data file, parses each one, and merges mob NpcMobList and resource ResourcesList spawn positions into the loaded coord data, keyed by entity ID.
• Save coord_data — write the merged result back out as coord_data.txt.

The map or location name is taken from the subfolder name, for example:


Empty files, truncated files, and parse errors are skipped and listed in the final status text.

Long-running file I/O runs on background threads, while progress is reported through the form progress bar and status label.

---

Stack

• Language: C# 7.3
• Framework: .NET Framework 3.5, WinForms
• Output type: WinExe, AnyCPU
• Project format: Legacy non-SDK MSBuild .csproj, ToolsVersion="15.0"
• UI: Windows Forms Classic
• Package manager: None, only GAC / framework references
• Solution: Npcgen2CoordData.sln

---

Requirements

• Windows with .NET Framework 3.5 SP1 targeting pack installed.
• Windows feature required: .NET Framework 3.5 includes .NET 2.0 and 3.0.
• MSBuild shipped with Visual Studio 2017+ or JetBrains Rider.

[WARNING]
Do not build with the legacy compiler:


It only supports C# 3.0 and will fail on string interpolation or null-conditional syntax used in the codebase.
[/WARNING]

[NOTE]
Microsoft.VisualBasic is still listed in the project file but is currently unused. It was kept to avoid unnecessary changes to the legacy project file.
[/NOTE]

---

Build

From the repository root in PowerShell:


Replace <edition> with your installed Visual Studio edition, for example:


Rider users can open:


Then build directly from the IDE.

Build output:

---

Run

Launch the built executable directly:


Typical workflow:

1. Click Load coord_data and pick an existing coord_data.txt. This is optional, you can start empty.
2. Click Import npcgen.data and select the maps root folder.
3. The tool scans immediate subfolders, for example:
   
   Code:

   ...\maps\world\npcgen.data
   ...\maps\a78\npcgen.data

4. Each subfolder is processed in one pass. The subfolder name becomes the map name in coord_data.txt.
5. Click Save coord_data to write the merged output.

---

Entry Point


Main UI files:

---

Scripts

This repository ships with:

• No build scripts
• No run scripts
• No package.json
• No CI configuration

The PowerShell command shown in the Build section is the canonical way to compile from the command line.

---

Environment Variables

None are read by the application.

---

Tests

There is currently:

• No test project
• No test framework reference
• No CI

Ad-hoc tests are written as standalone console programs that compile against the production .cs files directly.

High-level test steps:

1. Create a .cs file at the repo root with static int Main() inside namespace Npcgen2CoordData.
2. Re-declare the four progress delegates:
   
   C#:

   SetProgressMax
   SetProgressNext
   SetProgressValue
   SetProgressText

3. Compile with Roslyn csc.exe from the Visual Studio or Rider MSBuild folder.
4. Use:
   
   Code:

   /langversion:7.3
   /target:exe

5. Include the production source files you want to test, for example:
   
   Code:

   Npcgen2CoordData\CoordData.cs

6. Run the produced executable and check $LASTEXITCODE.
7. Delete the test source and binary afterwards.

[WARNING]
At least ProgressMax and, for CoordData.Read, ProgressText are invoked unconditionally without ?..

Tests must subscribe to those events or they will throw NullReferenceException.
[/WARNING]

---

Project Structure

---

Known Gotchas

• Culture-sensitive parsing
  
  CoordData.Read and CoordData.Save assume the current thread culture uses comma as the decimal separator.
  
  On en-US machines this can throw FormatException.
  
  Recommended fix:
  
  
  C#:

  CultureInfo.InvariantCulture

• Threading
  
  Form1 sets:
  
  
  C#:

  CheckForIllegalCrossThreadCalls = false;

  
  The app updates UI from worker threads directly. Do not introduce Invoke or async/await without auditing the whole flow.
• Binary format versioning
  
  NpcGen.ReadNpcgen branches on:
  
  
  Code:

  Version > 6
  Version > 9
  Version >= 11

  
  Any additions must also be mirrored in the corresponding write paths, or saved files may become unreadable.
• Public fields in data-carrier classes
  
  npcgen.cs reads and writes fields in declaration order. Do not auto-refactor to properties or reorder fields.

---

License

GNU General Public License v3.0.

See:

---

TODO

• Document the exact npcgen.data binary layout per version.
• Clarify expected text encoding for fixed-length name fields in npcgen.cs.
• Add a real automated test project.
• Confirm minimum supported Windows version.
• Confirm localization assumptions for coord_data.txt decimal separator.
• Add screenshots of the main form.
• Decide whether to remove the unused Microsoft.VisualBasic reference.