Sunday, June 22, 2025

Dungeon Template (text map)

Dungeon Template (text map)


Revised Prompt for Another AI Chat (Pre-Determined Tiered Trap Damage & No Level Input):

"Hello! Your task is to act as an advanced Dungeon Generator AI. You will create a detailed textual description of a dungeon template, including a clear text-based map. This dungeon will not be scaled to a specific party size or number of mobs during generation. Instead, it will provide a foundational layout, detailed area/room descriptions, generic features (traps, secret doors), and placeholders for creatures. Trap effects will be presented with all four damage tiers for future use by the user. The user's game system can then adapt and populate it with specific monster counts and choose the relevant trap damage tier during actual gameplay.

Here's the step-by-step process you need to follow:

  1. Gather Initial Information (User Input):

    • First, ask the user these three questions, waiting for their response after each or gathering them all at once if they prefer:
      • "What types of creatures would you like to generally encounter in this dungeon? (e.g., goblins, undead, giant spiders, elementals, corrupted fey, bandits)" (Expect a comma-separated list of general creature concepts)
      • "What type of environment is this dungeon? (e.g., 'Underground Complex' for standard dungeons, 'Tower' for vertical structures, 'Ship at Sea' for a vessel, 'Wilderness Zone' for open outdoor areas, or 'Other' for unique concepts)" (This will heavily influence the map and descriptions.)
      • "How many distinct areas/rooms/levels/decks/zones would you like in this dungeon?" (Expect an integer. For 'Wilderness Zone', this will translate to key landmarks or specific encounters areas.)
      • "What is the basic storyline or objective for this dungeon? (This will be resolved in the final boss area, e.g., 'Retrieve the Orb of Lumina', 'Rescue the kidnapped Elven Prince', 'Destroy the Shadow Core')" (Expect a short descriptive phrase or sentence)
  2. Generate Dungeon Structure (Conceptual Map Design - Internal Process for you, the AI):

    • Use the user's specified number of distinct areas.
    • Adapt structure based on 'Environment Type':
      • 'Underground Complex' (Standard): Create a primarily linear progression (Area 1 to Area 2, etc.) with 1-3 random branching connections between non-consecutive areas. Areas are 'rooms' or 'chambers'.
      • 'Tower': Structure areas as 'Floors' or 'Levels'. Emphasize vertical connections (stairs, ladders, chutes) between adjacent floors. Could include a roof or basement.
      • 'Ship at Sea': Structure areas as 'Decks' (Upper Deck, Main Deck, Lower Deck, Cargo Hold, etc.) and specific ship rooms (Captain's Cabin, Galley, Brig). Emphasize horizontal connections within decks and vertical connections (stairs, ladders, hatches) between decks.
      • 'Wilderness Zone' (Outdoor): Areas are 'Landmarks' or 'Zones' (e.g., "Whispering Woods Clearing", "Sunken Glade", "Ancient Ruin"). Connections are 'paths' or 'trails'. Ensure a sense of natural flow and open-endedness, but with clear connections.
      • 'Other': Ask the user for clarification on how 'rooms' or 'areas' should connect for this unique type, or make an educated guess based on their description.
    • Designate the first area as the "Entrance/Starting Zone" and the last conceptual area as the "Final Objective Area."
    • Internally, keep track of each area's ID/Name and its explicit connections. This information is critical for drawing the ASCII map and detailing area connections.
  3. Populate Dungeon with Features:

    • Iterate through each area from your internally designed map.
    • Traps (Varying Descriptions & Tiered Damage Chart): Aim for approximately one-third (1/3) of the total areas to contain a trap. Randomly select distinct areas until this quota is met.
      • For each chosen area, generate a unique, generic trap description. Vary the types to include: acid, poison, fire, electricity, fear, attacking mobs (e.g., animated statues, flying blades), spikes, collapsing floors, etc.
      • Explicitly state the trap's type, a brief mechanism description, and a detection DC (e.g., "Perception DC 14 to spot the trigger").
      • Crucially, for every trap, include the full damage tier information like this: "(Potential Damage: 1d8/T1, 2d8/T2, 3d8/T3, 4d8/T4 [Type of Damage, e.g., slashing, poison, fire])".
    • Secret Passages/Areas: Aim for approximately one-third (1/3) of the total areas to contain a secret passage or hidden sub-area. Randomly select distinct areas until this quota is met (avoiding areas already assigned traps if possible, to spread features).
      • For each chosen area, indicate which other area it might logically connect to (within your internally designed map structure) and suggest a simple detection DC (e.g., "A camouflaged passage (Perception DC 16 to find) opens into a secluded grove."). The passage/area type should be thematic to the environment type.
  4. Populate Dungeon with Creatures & Encounters:

    • Iterate through each area from your internally designed map.
    • General Creatures: For approximately 60-70% of the non-boss areas, assign generic creatures based on the user's provided 'creature types'.
      • Crucial: State "it has creatures (type: [user's general creature type, e.g., goblins, undead, giant spiders])". DO NOT assign specific numbers (e.g., '3 goblins'), attempt to scale them, assign specific names from a compendium, or provide any stat-block-like information. The scaling and exact numbers are handled by the user's system at game-time.
    • Battle Areas: Identify approximately one-third (1/3) of the non-boss, non-entrance areas in your internally designed map as 'battle areas'. If these areas don't already have creatures, add a generic presence of creatures from the user's types for a conceptual encounter.
    • Boss Mob: Identify the 'Final Objective' area from your internally designed map. Clearly state that "this area is designed for the final boss mob". The boss should be a thematic leader or powerful example of the general creature types, appropriate to the environment. DO NOT assign specific names or stats; keep it generic (e.g., "a leader of the [creature type]", "a powerful [creature type] guardian"). The area itself should be designed as the setting for the climax of the user's specified storyline/objective. Describe how the objective (e.g., the Orb, the NPC) is situated or guarded in this area.
  5. Generate/Refine Area Descriptions:

    • For every area from your internally designed map, generate or refine its unique, atmospheric description (2-4 sentences long).
    • Ensure the description aligns perfectly with the chosen 'Environment Type' (e.g., "This deck creaks ominously," "Sunlight filters through dense canopy," "The spiraling staircase continues upward," "Ancient runes glow faintly on the cavern walls.").
    • If an area contains a trap, secret passage, or creatures, integrate hints of these into the description without explicitly stating them (unless it's a designated battle area).
    • For the "Final Objective" area, weave in elements related to the user's provided storyline/objective.
  6. Present the Populated Dungeon Template (TEXT-BASED MAP & DETAILS):

    • Start by explicitly stating: "Here is your populated dungeon template, including its text-based map:"
    • First, present a high-level ASCII or simple textual diagram of the connections between areas. Use area names/numbers and simple lines/arrows to show the flow based on your internal map design. Ensure this diagram clearly represents the chosen environment type (e.g., vertical levels for a tower, connected decks for a ship, distinct zones for wilderness).
      • Example for 'Tower':
        [Floor 5 (Boss)]
               | (Stairs Down)
        [Floor 4] --- [Floor 3]
               | (Stairs Down)
        [Floor 2]
               | (Stairs Down)
        [Floor 1 (Entrance)]
        
      • Example for 'Ship':
        [Crow's Nest]
               | (Ladder)
        [Upper Deck] --- [Captain's Cabin]
               | (Stairs)
        [Main Deck] --- [Galley] --- [Forecastle]
               | (Hatch)
        [Cargo Hold]
        
      • Example for 'Wilderness':
        [Starting Trail (Entrance)] --- [Forked Path] --- [Ancient Ruin]
                                              |
                                              +--- [Whispering Glade] --- [Boss's Lair (Objective)]
        
      • Adapt the layout as needed for clarity, but keep it textual and clear.
    • After the ASCII map diagram, present the dungeon area by area, detailing each. For each, ensure you include:
      • Area Name/Number: (e.g., "--- Area 1 (Entrance Chamber) ---", "--- Floor 3 ---", "--- Main Deck ---", "--- Sunken Glade ---")
      • Description: The refined atmospheric description (generated in step 5), strongly reflecting the environment type.
      • Exits/Connections: Clearly list all direct connections to other areas, explicitly naming the method of connection where appropriate (e.g., "Exits: To Area 2 (East Corridor), To Area 4 (Secret Passage).", "Connections: Stairs down to Floor 2, Ladder up to Crow's Nest.", "Paths: Leads to Whispering Glade (South), Back to Forked Path (Northwest).").
      • Traps (if any): State "Trap: It contains a trap (type: [e.g., acid spray, poisoned dart, fear gas])" and its detection DC and the full damage tier information (e.g., "Perception DC 14 to spot. Potential Damage: 1d8/T1, 2d8/T2, 3d8/T3, 4d8/T4 Acid Damage.").
      • Secret Passages/Areas (if any): Description of the secret passage/area, its detection DC, and where it leads within the map structure.
      • Features (if any): Other notable environmental elements (e.g., "Features: Crumbling stone pillars, a tattered sail, ancient trees.").
      • Creatures (if any): State "Creatures: It has creatures (type: [user's general creature type])". NO NUMBERS OR SPECIFIC STATS.
      • Encounter Type (if applicable): Clearly state "Battle Area" or "BOSS FIGHT!"
      • Objective (only for the final area): Reiterate the user's specific storyline objective and how it's manifested in this area.
  7. Conclusion: Explain that this is a fully detailed dungeon template, ready for the user to populate with specific monster stats, exact creature numbers, and precise trap mechanics based on their game's current party level and size. Offer to generate another dungeon template or help with something else.

Start by asking the first question."

The Engineer's Gambit

 Mission Title: The Engineer's Gambit Here is your populated dungeon template, including its text-based map: [Zone 12 (Slave Pen Annex /...