2DA Editor NWN

The tool provides a back-end workflow to edit Neverwinter Nights 2DA data files without manual text editing. It accepts a 2DA text block and a user-defined set of edits, organized as row and column targets, and applies changes in a controlled, repeatable way. It validates column types, enforces required fields, and preserves table structure. By operating on a formal input model, it reduces syntax errors and inconsistent formatting when multiple contributors work on the same 2DA data. Target users include NWN modders, developers, and pipeline integrators who need reliable batch edits.
Core Logic & Features: Inputs are recognized as 2DA_text, target_rows, column_edits, export_format. The engine parses the 2DA into a structured matrix, validates column kinds, applies edits, and re-serializes to a 2DA-compatible text with tab separators. Required features include parse, type validation, per-row edits, order preservation, and precise error reporting. Optional/advanced features include conditional edits, partial row updates, and multi-format export. Error handling is designed to fail safely with actionable messages for further edits.
Inputs & Outputs: Inputs include 2DA_text (string, required), target_rows (array of integers, optional), column_edits (array of objects with column_name string, row_index integer optional, new_value string, required), and export_format (string, optional; values: 2DA or CSV). Outputs include result_text (string; 2DA formatted with tab delimiters), status (string; ok or error), and error_details (string, optional).
Algorithms & Calculations: The backend parses the source into header and rows, normalizes data types, applies edits to specified rows/columns, and re-serializes preserving original order and delimiters. Advanced usage supports conditional edits based on row predicates. Edge Cases & Localization: Handles missing columns, invalid types, out-of-range row indices, and conflicting edits with clear position references. Encoding is UTF-8; line endings follow the source convention but can be normalized during export. Localization considerations are limited to text data in 2DA files and do not affect core numeric semantics. Assumptions & Exclusions: Assumes input 2DA is valid text-based data with a header row. Excludes UI concerns, real-time collaborative editing visuals, and any game engine execution semantics beyond data integrity and formatting.