mirror of
https://github.com/Kelsidavis/WoWee.git
synced 2026-05-07 09:33:51 +00:00
c1c1f1b2a8
Visualizing quest chains in plain text rapidly becomes unreadable past ~10 quests. This emits a DOT file that renders to a labeled DAG you can paste into a wiki or PR description: wowee_editor --export-quest-graph custom_zones/MyZone dot -Tpng custom_zones/MyZone/quests.dot -o quests.png Node coloring conveys completion-readiness at a glance: - lightgreen: has objectives + reward (will complete in-game) - lightyellow: has objectives but no reward (uncommon) - lightgray: no objectives (won't complete — common authoring bug) - mistyrose dashed: synthetic node for a quest ID referenced by nextQuestId but missing from quests.json (broken chain) Edges: - solid black: valid chain link - dashed red labeled 'missing': dangling nextQuestId Labels include quest ID, title (DOT-escaped for safety), required level, and XP reward — enough context that the graph stands alone without needing to cross-reference quests.json. Verified on a 3-quest zone with chain 1->2->3->999 (last broken): DOT output has 3 colored nodes (lightgreen for the 2 quests with objectives, lightgray for the third), 2 solid edges, 1 dashed-red edge to a synthetic mistyrose <missing> node. |
||
|---|---|---|
| .. | ||
| asset_extract | ||
| auth_login_probe | ||
| auth_probe | ||
| blp_convert | ||
| dbc_to_csv | ||
| editor | ||
| asset_pipeline_gui.py | ||
| backup_assets.sh | ||
| diff_classic_turtle_opcodes.py | ||
| gen_opcode_registry.py | ||
| generate_ffx_sdk_vk_permutations.sh | ||
| m2_viewer.py | ||
| opcode_map_utils.py | ||
| validate_opcode_maps.py | ||