Conflicts Import and Packaging

Conflicts, import and packaging

All three workflows on this page are included in 0.2.0. Check the installed help before using them.

Review an ordered mod set

pxtk conflicts --json
pxtk conflicts --game ck3 --input <base-mod> --input <later-mod> --limit 50 --json

Inputs are first loaded first. Without --input, the list is configured parents followed by the editable mod. Explicit input lists require a selected game but not an editable workspace. Inputs need ordinary disjoint mod directories with the profile's descriptor metadata. Linked aliases, overlapping roots and game-folder inputs are refused.

The report contains contributors, proven winners, replacement paths, dependency issues, totals and a source fingerprint. Unknown precedence remains unknown. The profile must supply a verified composition policy; otherwise the report is incomplete. Cross-file ordinary-definition precedence and replace_path suppression are not certified. Vanilla is excluded. Binary inventory metadata is fingerprinted, not binary contents, so binary assets need external review.

Exit 1 means conflicts or composition issues require review, including identical overlaps. Increase --limit within 1 to 200 when a list is truncated. Source roots overlapping the Node executable directory are refused because core capture requires a separate host boundary. This command reports saved-file composition; it neither creates a compatibility patch nor certifies gameplay compatibility.

MCP pxtk_conflicts accepts optional inputs:[...] and limit.

Import one vanilla file or one directory path

pxtk import --source common/scripted_effects/<file>.txt --json
pxtk import --directory common/scripted_effects --json

Choose exactly one game-relative source file or directory. File import copies exact saved bytes to the matching mod-relative destination. Directory import creates the selected directory and missing parents only; it does not recursively copy contents. The game source stays read-only. Existing destinations, traversal and links are refused.

Review source, destination, kind, folders and the standard write result. Directory previews can have an empty files array because only paths are created. Repeat the reviewed request with --write --expect <previewToken>. Failed writes report completed files, partial files and created folders. Partial files are retained so cleanup cannot remove concurrent edits. Inspect reported paths before deciding recovery. MCP pxtk_import accepts either source or directory, plus optional write and expect.

Stage a local release directory

$packageArgs = @("package", "--output", "<new-release-folder>", "--json")
$preview = pxtk @packageArgs | ConvertFrom-Json
if ($LASTEXITCODE -ne 0) { throw "Package preview failed." }
$preview.data | ConvertTo-Json -Depth 10
# Review readiness, metadata findings, hashes, exclusions and totals first.
pxtk @packageArgs --write --expect $preview.data.previewToken

The output resolves from the process working directory. It must be absent, outside the mod, game and dependencies, and have an existing parent. The output also cannot contain a source root. Source files are unchanged.

The report shows included files with byte counts and SHA-256 hashes, excluded paths and reasons, descriptor findings and total size. ready:false and descriptor errors block staging; warnings remain visible. Source, ignore-policy or output-state changes invalidate the token. Inputs and created outputs are checked throughout staging. A failed write reports completed files, partial files and created folders. Partial files remain to preserve concurrent edits. Inspect every reported path before cleanup, and use an absent destination for a fresh attempt.

Ignore policy

Staging uses Toolkit .pxignore semantics. With no .pxignore, default patterns apply. An existing .pxignore replaces those defaults rather than extending them. Toolkit configuration is always excluded, and descriptor metadata is always retained. The command never creates or edits .pxignore.

Custom exclusions can therefore include files that defaults would omit. Inspect the complete proposal before applying. Bounded included, excluded and findings lists state their totals and truncation; use --limit where needed.

MCP pxtk_package accepts output, optional limit, write and expect. Staging produces a directory, not an archive. It does not upload to Steam or certify Workshop acceptance or game compatibility.