You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

If you use Claude Code, it can significantly help your custom content work, as well as modernize your workflows past using legacy tools like Tileset Duplicator, Set Editor, GFFEdit to manage your palettes, and the like.  This assumes you have working knowledge of Claude Code and/or are willing to teach yourself.  Of course you need a subscription,too.

Having CLI tools are essential, and you should get them at https://github.com/niv/neverwinter.nim

Claude Code rules are markdown files that provide Claude with domain-specific knowledge when working in a project. They act as persistent reference material — whenever Claude encounters relevant files, the rules automatically load into context so it understands the conventions, file formats, and pitfalls specific to your work.

How to Use These Rules

  1. In your NWN project directory, create a .claude/rules/ folder
  2. Save each rule as a .md file in that folder (e.g., .claude/rules/nwn-set-file-format.md)
  3. When you start a Claude Code session in that project, the rules load automatically based on the files you're working with

Rules can optionally include a paths: frontmatter to scope when they load. For example, a rule with paths: ["**/*.set"] only activates when you're working with .set files.

Available Rules

The rules below cover NWN Enhanced Edition tileset development. 

RuleScopeDescription
SET File Format.set, .mdl, .wok filesStructure of the .set tileset definition, terrain/crosser types, tile entries, door sections, groups, and MDL/WOK internal references
ITP Palette Format.itp filesStructure of the .itp toolset palette, branch IDs, subfolder ID values, terrain paint layout, and JSON entry formats
Tileset Operations.set, .itp, .mdl, .wok filesProcedures for reordering tiles, duplicating terrain families, adding tiles, troubleshooting, and verification
  • No labels