# Wizard's Castle Owner's Manual
## Section 4: Summoning Circle Assembly
### Before You Begin
**Estimated Assembly Time:** 2-3 hours
**Difficulty Level:** Intermediate
**Required Skill Level:** Apprentice Mage or higher
**DANGER:** Improperly assembled summoning circles may result in dimensional rifts, uncontrolled entity manifestation, or permanent soul displacement. Always follow instructions precisely.
---
### What's In The Box
Verify all components are present before beginning assembly:
- (1) Primary summoning circle (copper inlay, 6 ft diameter)
- (5) Runic anchor posts (obsidian, 18 inches each)
- (1) Central focus crystal (amethyst, approximately 3 lbs)
- (1) Containment ward scroll
- (12) Silver binding pins
- (1) Chalk (enchanted, phosphorescent blue)
- (1) Small vial of sanctified salt
**Note:** If any components are missing or damaged, contact Castle Support immediately. Do not attempt to substitute materials.
---
### Required Tools (Not Included)
- Spirit level (mundane or enchanted)
- Measuring tape (minimum 10 ft)
- Mallet (non-metallic preferred)
- Athame or ritual blade
- Basic protective ward (personal)
---
### Safety Precautions
⚠️ **WARNING:** Do not assemble summoning circle during the following conditions:
- New moon or full moon (±2 days)
- Planetary retrograde periods
- Within 48 hours of a dimensional convergence
- During thunderstorms or high magical flux events
⚠️ **CAUTION:** Wear protective equipment including:
- Grounding talisman
- Reflective ward amulet
- Eye protection rated for Class III ethereal discharge
---
### Step 1: Site Preparation
1. Select a location at least 15 feet from exterior walls and 20 feet from other magical installations.
2. Clear the area of all furniture, carpets, and mundane objects within a 10-foot radius.
3. Sweep the floor thoroughly. Even small debris can disrupt runic patterns.
4. Use the spirit level to verify the floor is level within 2 degrees. If floor is not level, proceed to Appendix C: Leveling Procedures.
**Note:** Basements and ground-floor rooms are recommended. Upper-floor installations require additional structural reinforcement (see Section 4.7: Load-Bearing Considerations for Summoning).
---
### Step 2: Circle Placement
1. Locate the center point of your chosen area. Mark with chalk.
2. Unroll the primary summoning circle carefully. The copper inlay is delicate and kinking will compromise its function.
3. Center the circle on your chalk mark. The outermost edge should have a 6-foot diameter.
4. Verify the circle is perfectly round using your measuring tape. Measure the diameter at three different angles. All measurements should be within 1/4 inch of each other.
**IMPORTANT:** Do not step inside the circle during assembly. Always work from the perimeter.
---
### Step 3: Anchor Post Installation
1. Identify the five anchor points marked on the circle's perimeter. They form a perfect pentagon.
2. Place one obsidian anchor post at each marked position. The rune-carved side should face inward toward the circle's center.
3. Using your mallet, gently tap each post until it sits flush with the floor.
4. Secure each post with two silver binding pins driven at 45-degree angles through the pre-drilled holes.
**CAUTION:** Do not strike the anchor posts directly on their runed surfaces. This may crack the obsidian and void your warranty.
---
### Step 4: Central Crystal Installation
1. Remove the focus crystal from its protective case.
2. Wipe the crystal with a clean, dry cloth to remove any oils or debris.
3. Place the crystal in the exact center of the circle. The natural point of the crystal should face upward.
4. The crystal should rest stable without rocking. If it rocks, rotate it slightly until it settles.
**Note:** The crystal may emit a faint hum when properly positioned. This is normal.
---
### Step 5: Containment Ward Application
1. Unroll the containment ward scroll completely. Do not crease or fold.
2. Read the activation phrase aloud three times clearly: *"Claustra firma, limina tuta, nihil transit."*
3. You should observe a faint shimmer around the circle's perimeter. If no shimmer appears, repeat step 2.
4. Once activated, place the scroll in your castle's ward repository. The ward remains active as long as the scroll is intact and stored within 100 feet of the circle.
---
### Step 6: Salt Barrier
1. Pour the sanctified salt in an unbroken line around the outside of the circle, approximately 6 inches from the copper inlay.
2. The salt line must be continuous with no gaps. Even small breaks compromise the containment field.
3. Smooth the salt line so it is approximately 1/4 inch thick and uniform in width.
**WARNING:** Never allow the salt line to be broken while a summoning is in progress. Maintain a 3-foot clearance around the salt line at all times.
---
### Step 7: Final Verification
Before first use, verify the following:
- [ ] All five anchor posts are secure and facing inward
- [ ] Central crystal is centered and stable
- [ ] Containment ward shimmer is visible
- [ ] Salt line is unbroken and uniform
- [ ] No cracks or gaps in the copper inlay
- [ ] Area within 10 feet is clear of objects and debris
---
### Testing Your Installation
1. Stand outside the circle and cast a basic light cantrip at the center.
2. The light should bounce off the containment ward and dissipate. If the light passes through, your ward is not properly activated. Return to Step 5.
3. Sprinkle a pinch of mundane salt on the central crystal. If the salt sparks briefly before falling away, your circle is properly grounded.
**IMPORTANT:** Do not attempt to summon entities until you have successfully completed both tests above.
---
### Maintenance
- Inspect the copper inlay monthly for tarnish or damage
- Replace the salt barrier after every use
- Recharge the focus crystal quarterly during new moon phases
- Re-apply containment ward annually or after 100 summonings, whichever comes first
---
### Troubleshooting
**Problem:** Crystal doesn't hum when positioned
**Solution:** Ensure all anchor posts are properly grounded. Check that posts are not cracked.
**Problem:** Ward shimmer is inconsistent or flickering
**Solution:** Scroll may be damaged or improperly activated. Obtain replacement scroll from Castle Support.
**Problem:** Salt line keeps breaking or dispersing
**Solution:** Check for drafts or air currents. Summoning circles should not be placed near windows or ventilation shafts.
---
### Next Steps
Once assembly is complete, proceed to Section 5: Basic Summoning Protocols and Safety Procedures.
For advanced configurations, see Section 5.4: Multi-Circle Arrays and Dimensional Anchoring.
---
**Technical Support:** For assembly assistance, contact Castle Support at support@wizardcastle.arcane or via sending spell to Crystal Network Node 447.
---
# Section 12: Planar Transit Network Integration
## Overview
The Planar Transit Network (PTN) allows your castle to send and receive travelers, goods, and messages across dimensional boundaries. This guide covers initial setup, authentication, and basic integration patterns.
**Prerequisites:**
- Active castle registration with the Interdimensional Transit Authority
- At least one properly installed teleportation circle (see Section 8)
- Castle Nexus Crystal (included with Premium tier and above)
- Mage level 5+ or authorized castle administrator
**API Version:** PTN v3.2
**Protocol:** Ethereal Transport Layer (ETL)
**Base Endpoint:** `ptn://network.planar.transit`
---
## Authentication
### Obtaining Your Castle Key
All PTN requests require authentication using your unique Castle Key.
1. Navigate to your castle's central control chamber
2. Locate the Castle Nexus Crystal (typically mounted above the main hearth)
3. Channel a simple identification spell while touching the crystal
4. Your Castle Key will be revealed as a 32-character runeglyph sequence
**Example Castle Key:**
```
ᚱᚢᚾᛖ-ᚲᚨᛊᛏᛚᛖ-ᚺᛖᛪ᛫᛫᛫᛫
```
⚠️ **SECURITY WARNING:** Never share your Castle Key in public forums, sending spells, or scrying communications. Unauthorized access can result in dimensional breaches, entity infiltration, or transit hijacking.
### Key Rotation
For security purposes, rotate your Castle Key every 90 days:
```
castle.nexus.rotateKey({
currentKey: "your-current-key",
verificationType: "blood-seal"
})
```
---
## Making Your First Request
### Basic Transit Request
To send a traveler through the PTN, you'll invoke a transit request with the following parameters:
**Required Parameters:**
- `origin`: Your castle's planar coordinates
- `destination`: Target location's planar coordinates
- `payload`: Traveler or cargo manifest
- `signature`: Cryptographic seal (generated via castle key)
**Example Request:**
```
PTN.initiateTransit({
origin: "Prime-Material.Realm-47.CastleBlackspire",
destination: "Prime-Material.Realm-47.TowerAzure",
payload: {
type: "humanoid",
count: 1,
species: "human",
name: "Aldric the Bold",
inventory: ["sword", "traveling cloak", "rations(3)"]
},
signature: castle.generateSignature(payload, castleKey),
options: {
priority: "standard",
returnRoute: true
}
})
```
**Response:**
```
{
status: "transit_initiated",
transitId: "TRN-9847562",
estimatedArrival: "47 seconds",
energyCost: 250,
route: ["BlackspireNode", "RegionalHub-7", "AzureNode"],
confirmation: "ᛏᚱᚨᚾᛊᛁᛏ-ᚲᛟᚾᚠᛁᚱᛗᛖᛞ"
}
```
---
## Response Codes
The PTN uses standard ethereal response codes:
| Code | Status | Description |
|------|--------|-------------|
| 200 | Success | Transit completed successfully |
| 201 | Queued | Transit queued due to high traffic |
| 400 | Invalid Request | Malformed coordinates or missing parameters |
| 401 | Unauthorized | Invalid or expired Castle Key |
| 403 | Forbidden | Destination blocks transit from your origin |
| 404 | Not Found | Destination coordinates do not exist |
| 429 | Rate Limited | Too many transits requested (see Rate Limits) |
| 500 | Network Error | Dimensional instability detected |
| 503 | Service Unavailable | Destination circle is offline or damaged |
| 666 | Infernal Interference | Demonic activity disrupting transit path |
---
## Rate Limits
To prevent dimensional strain and energy grid overload, the PTN enforces the following limits:
**Standard Tier:**
- 50 transits per day
- 5 simultaneous active transits
- 10 transit requests per minute
**Premium Tier:**
- 500 transits per day
- 25 simultaneous active transits
- 50 transit requests per minute
**Enterprise Tier:**
- Unlimited transits (fair use policy applies)
- 100 simultaneous active transits
- 200 transit requests per minute
When rate limited, you'll receive a `429` response with a `retryAfter` timestamp:
```
{
status: "rate_limited",
message: "Transit quota exceeded",
retryAfter: "2026-01-13T14:30:00Z",
quotaReset: "2026-01-14T00:00:00Z"
}
```
---
## Error Handling
Always implement proper error handling for transit requests. Dimensional travel is inherently unstable.
**Best Practice Example:**
```
try {
const result = await PTN.initiateTransit(transitRequest);
if (result.status === "transit_initiated") {
castle.notifyStaff(`Traveler ${payload.name} in transit`);
return result.transitId;
}
} catch (error) {
if (error.code === 503) {
// Destination offline - notify traveler
castle.alert(`Cannot reach ${destination}. Circle may be damaged.`);
} else if (error.code === 666) {
// Demonic interference - activate defenses
castle.shields.raise();
castle.alert("INFERNAL ACTIVITY DETECTED - Transit aborted");
} else {
// Generic error handling
castle.log.error(`Transit failed: ${error.message}`);
}
}
```
---
## Webhook Notifications
Configure webhooks to receive real-time updates about transit status without polling.
### Setup
```
PTN.registerWebhook({
castleKey: "your-castle-key",
endpoint: "castle://blackspire/transit-notifications",
events: [
"transit.initiated",
"transit.completed",
"transit.failed",
"entity.arriving"
]
})
```
### Webhook Payload Example
When a transit completes, you'll receive:
```
{
event: "transit.completed",
transitId: "TRN-9847562",
timestamp: "2026-01-13T12:45:33Z",
payload: {
name: "Aldric the Bold",
status: "arrived_safely",
integrity: 100,
location: "circle-3-north-tower"
}
}
```
**Note:** Webhook endpoints must respond within 5 seconds or they will be considered failed and retried up to 3 times with exponential backoff.
---
## Advanced Features
### Scheduled Transits
Schedule future transits for automated courier services or routine deliveries:
```
PTN.scheduleTransit({
...transitRequest,
scheduledTime: "2026-01-15T09:00:00Z",
recurring: {
frequency: "weekly",
dayOfWeek: "Monday"
}
})
```
### Cargo Manifests
For bulk transit of goods, use detailed cargo manifests:
```
payload: {
type: "cargo",
containers: [
{
id: "CONT-001",
contents: "enchanted_weapons",
count: 50,
weight: "250 lbs",
magicLevel: "moderate"
},
{
id: "CONT-002",
contents: "potion_supplies",
count: 200,
weight: "150 lbs",
hazardClass: "volatile"
}
]
}
```
### Emergency Recall
Cancel an in-progress transit and return payload to origin:
```
PTN.emergencyRecall({
transitId: "TRN-9847562",
reason: "hostile_activity_detected",
authorization: castle.ownerSignature()
})
```
⚠️ **WARNING:** Emergency recalls consume 3x normal energy and may result in minor temporal displacement (±15 minutes). Use only in genuine emergencies.
---
## Testing
### Sandbox Environment
The PTN provides a sandbox for testing integrations without risking actual dimensional travel:
**Sandbox Endpoint:** `ptn://sandbox.planar.transit`
Sandbox features:
- Simulated transit delays and responses
- Controllable error injection for testing error handling
- No energy costs or rate limits
- Test entities are non-corporeal and cannot interact with physical plane
### Test Coordinates
Use these coordinates for development:
- Origin: `Sandbox.Realm-Test.CastleAlpha`
- Destination: `Sandbox.Realm-Test.TowerBeta`
---
## Monitoring & Diagnostics
### Energy Usage Tracking
Monitor your castle's energy consumption:
```
const usage = PTN.getEnergyUsage({
castleKey: "your-key",
period: "last_30_days"
});
// Returns:
{
totalTransits: 247,
totalEnergy: 61750,
averagePerTransit: 250,
peakDay: "2025-12-28",
remainingQuota: 15000
}
```
### Network Status
Check PTN network health before critical transits:
```
const status = PTN.getNetworkStatus();
// Returns:
{
status: "operational",
dimensionalStability: 98,
averageTransitTime: "42 seconds",
activeTransits: 1847,
incidents: []
}
```
---
## Security Best Practices
1. **Validate incoming travelers** - Always verify identity before granting castle access
2. **Implement allowlists** - Restrict which origins can send transits to your castle
3. **Monitor for anomalies** - Unusual transit patterns may indicate attempted breaches
4. **Regular key rotation** - Rotate Castle Keys every 90 days minimum
5. **Backup transit logs** - Maintain records for at least 1 year for security audits
---
## Support & Resources
**Documentation:** `ptn://docs.planar.transit`
**Status Page:** `ptn://status.planar.transit`
**Developer Portal:** `ptn://developers.planar.transit`
**Technical Support:** Send spell to PTN Node 108 or visit support.planar.transit
**Community:**
- Wizard's Forum: Discussion and integration examples
- PTN Developer Discord: Real-time help from other castle administrators
- Monthly Office Hours: First Tuesday of each month, 2pm GMT
---
## Changelog
**v3.2 (Current)**
- Added webhook notification support
- Improved error messages for dimensional instability
- New emergency recall feature
- Enhanced cargo manifest validation
**v3.1**
- Increased rate limits for Premium tier
- Fixed issue with temporal displacement on recalls
- Added sandbox environment
**v3.0**
- Major protocol update (breaking changes from v2.x)
- Introduced Castle Key authentication
- Deprecated legacy portal stones
---
# Section 15: Troubleshooting Common Castle Issues
## How to Use This Guide
This troubleshooting guide is organized by symptoms rather than systems. Locate the issue that best describes what you're experiencing, then follow the diagnostic steps to identify and resolve the problem.
**Severity Levels:**
- 🔴 **CRITICAL** - Immediate safety risk or castle system failure
- 🟡 **MAJOR** - Significant functionality impaired, resolve within 24 hours
- 🟢 **MINOR** - Inconvenience only, resolve at your convenience
For emergency situations (dimensional rifts, entity breaches, structural collapse), contact Castle Emergency Services immediately at Node 911.
---
## Magical Systems
### My castle keeps turning invisible at random times 🟡
**Possible Causes:**
- Illusion wards overtaxed or misconfigured
- Unstable enchantment interaction
- Previous owner's pranks still active
**Diagnostic Steps:**
1. Check your castle's enchantment registry for conflicting spells
- Navigate to: Control Chamber > Enchantment Log > Active Effects
- Look for multiple invisibility or illusion effects
2. Verify ward crystal charge levels
- Invisibility often occurs when ward crystals drop below 15% charge
- Recharge crystals if needed (see Section 9: Ward Maintenance)
3. Inspect for prank runes
- Check doorframes, archways, and window sills for hidden glyphs
- Previous owners often hide time-delayed prank enchantments
- Use a dispel magic scroll if found
**Solution:**
- If charge-related: Recharge ward crystals and reduce illusion ward sensitivity to 60%
- If conflicting spells: Disable the newer spell or consult Section 11: Enchantment Priority Rules
- If prank runes: Apply universal dispel to affected areas, may require professional curse-breaker
---
### The lights flicker whenever I cast a spell 🟢
**Possible Causes:**
- Insufficient magical grid capacity
- Grounding issue with primary ley line connection
- Spectral infestation in the lighting system
**Diagnostic Steps:**
1. Note when flickering occurs
- Does it happen with all spells or only certain schools of magic?
- Is it worse in specific rooms or castle-wide?
2. Check your magical load
- Cast: `castle.diagnostics.getMagicLoad()`
- If consistently above 85%, you're approaching capacity
3. Inspect ley line tap
- Located in sub-basement, beneath main ward crystal
- Look for corrosion, loose connections, or unusual energy discharge
**Solution:**
- If capacity issue: Upgrade to Premium Ley Line Package or reduce number of active enchantments
- If grounding issue: Re-anchor ley line tap using procedure in Section 7.3
- If spectral: Deploy spirit ward in lighting conduits (see "Ghosts in unexpected places")
---
### My summoning circle teleported my cat instead of the demon I requested 🟡
**Possible Causes:**
- Incorrect runic configuration
- Cat walked through circle during invocation
- Targeting parameters too vague
**Diagnostic Steps:**
1. **DO NOT attempt another summoning until issue is resolved**
2. Check current location of intended summon
- Cast: `summon.locate(targetEntityID)`
- Verify demon is still in home dimension
3. Check cat's current location
- This is more urgent
- Demonic realms are not cat-friendly
4. Review summoning parameters used
- "Small, furry, with claws" describes both cats and certain demon species
- Ensure you specified dimensional origin coordinates
**Solution:**
- Immediate: Perform emergency recall to retrieve cat (see Section 12: Emergency Recall)
- Prevention: Install pet barriers around summoning areas
- Recalibrate circle targeting to require dimension-specific coordinates
- Consider subscribing to PTN Premium for entity verification before transit
**Note:** If your cat returns with unusual abilities or speaking in tongues, contact a cleric immediately.
---
### There's a strange humming coming from the north tower 🔴/🟡
**Severity depends on pitch and volume**
**Possible Causes:**
- Dimensional portal forming
- Experimental spell gone wrong
- Trapped entity attempting escape
- HVAC system needs maintenance
**Diagnostic Steps:**
1. **Safety First:** Do not enter tower until you've completed initial assessment
2. Identify the pitch
- High-pitched whine: Likely dimensional/energy buildup 🔴
- Low rumble: Probably structural or mechanical 🟡
- Melodic/harmonic: Possible entity presence 🟡
- Rhythmic clicking: Just the HVAC 🟢
3. Check for visual anomalies
- Glowing lights, shimmering air, or floating objects = 🔴 STOP and evacuate
- Heat waves or unusual shadows = 🟡 proceed with caution
- Nothing visible = 🟢 probably safe to investigate
4. Scan for magical buildup
- Cast: `castle.detect.magicLevel("north-tower")`
- Reading above 500 units = 🔴 critical
- Reading 100-500 = 🟡 concerning
- Reading below 100 = 🟢 normal
**Solution:**
**If Critical (🔴):**
- Evacuate tower and seal entrance
- Activate emergency containment protocols
- Contact Dimensional Stability Bureau at Node 447-DIM
**If Major (🟡):**
- If entity-related: Attempt communication before entering. May need exorcist.
- If magical buildup: Safely discharge excess energy using grounding rod (Section 8.4)
- If structural: Inspect tower foundation for cracks or settling
**If Minor (🟢):**
- Schedule HVAC maintenance
- Check for loose shutters or wind interference
- Verify all experimental equipment is properly powered down
---
## Environmental & Structural
### My moat is bubbling and smells like sulfur 🟡
**Possible Causes:**
- Moat dragon indigestion
- Underwater volcanic vent activation
- Alchemy lab waste disposal violation
- Demonic contamination
**Diagnostic Steps:**
1. Locate your moat dragon
- If dragon is present and appears distressed: Likely indigestion
- If dragon is absent: Check other causes
2. Test water sample
- Use basic alchemy kit to test pH and magical contamination
- pH below 4 or above 10 = chemical issue
- Glowing or changing colors = magical contamination
3. Inspect moat perimeter
- Look for discharge pipes from castle interior
- Check for cracks in moat floor (volcanic activity)
4. Scan for demonic presence
- Cast: `detect.evil(area: "moat")`
- Any positive result requires immediate action
**Solution:**
- Dragon indigestion: Reduce knight intake, add fiber (hay bales), administer antacid potion
- Chemical: Identify source, stop discharge, consider moat water replacement
- Volcanic: Contact geological survey; may need to relocate moat
- Demonic: Consecrate moat water, install holy ward markers every 50 feet
**Prevention:** Install filtration system and establish waste disposal protocols (see Appendix F: Environmental Compliance)
---
### Doors open and close by themselves 🟡/🟢
**Possible Causes:**
- Poltergeist or ghost
- Faulty automation enchantments
- Castle settling causing latch failures
- Draft from dimensional portal
**Diagnostic Steps:**
1. Observe the pattern
- Random doors at random times: Likely supernatural
- Same doors repeatedly: Likely mechanical/magical malfunction
- All doors simultaneously: Likely systemic enchantment issue
- Only during storms/high winds: Likely pressure differential or drafts
2. Check for ghost signs
- Temperature drops near affected doors
- Unexplained sounds (chains, moaning, "GET OUT")
- Items moving when doors open/close
- Feelings of being watched
3. Inspect door automation system
- Review: Control Chamber > Automation > Door Settings
- Check for conflicting open/close schedules
- Verify sensors are clean and properly aligned
4. Check for drafts
- Hold candle near door frame when closed
- Flame disturbance indicates air flow
- Trace air flow to source
**Solution:**
- Ghost: Hire medium for spiritual assessment; may need exorcism or negotiation
- Automation: Disable automatic door function, manually reprogram with clear priority rules
- Settling: Adjust latches and hinges, may need carpenter for door realignment
- Portal/draft: Seal the source; check Section 12 if portal-related
**Note:** Some ghosts are benign or even helpful. Consider cohabitation before exorcism.
---
### The castle is always cold no matter what I do 🟡
**Possible Causes:**
- Insufficient furnace capacity for castle size
- Heat-draining curse or enchantment
- Phantom ice elemental infestation
- Poor insulation or air leaks
- Dragon refusing to heat central chambers
**Diagnostic Steps:**
1. Verify furnace operation
- Check that fire elementals are well-fed and content
- Ensure coal/magical fuel reserves are adequate
- Inspect heating ducts for blockages
2. Test for curses
- Cast: `detect.curse(scope: "entire-castle")`
- Pay special attention to result: "perpetual_winter" or "ice_affinity"
3. Check for elementals
- Look for frost patterns in unusual places
- Listen for crystalline tinkling sounds
- Note if cold spots move or concentrate in certain areas
4. Inspect insulation
- Check window seals, door gaps, and chimney flues
- Cold castles built before 1600 often lack modern insulation standards
5. Dragon status check
- If you employ a dragon for heating: verify their cooperation level
- Check last payment/tribute date
- Assess dragon's mood and comfort
**Solution:**
- Furnace: Upgrade capacity, add supplemental heating sources
- Curse: Hire curse-breaker; investigate who cursed your castle and why
- Elementals: Deploy fire wards, raise ambient temperature until they leave voluntarily
- Insulation: Retrofit with modern thermal enchantments (expensive but effective)
- Dragon: Renegotiate terms, improve living conditions, consider signing bonus
**Quick Fix:** Deploy personal warming charms to residents while addressing root cause
---
## Creatures & Entities
### My dragon won't stop hoarding my mail 🟢
**Possible Causes:**
- Natural draconic hoarding instinct
- Boredom or lack of enrichment
- Insufficient designated hoard space
- Mail smells interesting (food stains, perfume, etc.)
**Diagnostic Steps:**
1. Assess current hoard situation
- Is dragon's designated hoard area full?
- Is hoard composition satisfying to dragon? (gold, gems, magical items preferred)
2. Evaluate dragon enrichment
- When did dragon last receive new hoard items?
- Does dragon have adequate flight space and exercise?
- Is dragon socially fulfilled? (some dragons are social)
3. Inspect mail for attractants
- Food particles or grease stains
- Strong scents
- Shiny/metallic packaging
**Solution:**
- Expand hoard space if needed
- Provide regular "hoard allowance" (weekly gold coins or gems)
- Establish enrichment routine: weekly flight, puzzle feeders, new hoard items
- Enchant mailbox with "boring" aura to reduce dragon interest
- Train dragon with positive reinforcement: reward for leaving mail alone
**Alternative:** Hire dedicated mail retrieval specialist (hazard pay required)
---
### There are ghosts in my plumbing 🟡
**Possible Causes:**
- Spectral residue from previous owners
- Improper disposal of haunted objects down drains
- Ley line intersection beneath pipes
- Actual aquatic ghosts (rare)
**Diagnostic Steps:**
1. Document manifestations
- Voices from drains
- Water running when taps are off
- Toilets flushing autonomously
- Ectoplasm backing up into sinks
2. Research castle history
- Were previous owners involved in necromancy?
- Any deaths related to plumbing? (drowning, scalding, etc.)
- Check for records of hauntings
3. Inspect plumbing physically
- Look for objects that shouldn't be there
- Check for ectoplasm buildup (green-grey residue)
- Verify all pipes are properly grounded spiritually
**Solution:**
- Professional exorcism of plumbing system (specialized service)
- Install spectral filters at main water intake
- Blessing of water supply by qualified cleric
- Remove and properly dispose of any cursed objects found in pipes
**Prevention:** Never flush cursed objects. Use designated magical waste disposal.
---
### Something is living in my walls but I can't figure out what 🟡
**Possible Causes:**
- Ordinary vermin (rats, mice, squirrels)
- Brownies or other helpful fae
- Gremlins
- Small escaped familiar
- Mimic larvae
**Diagnostic Steps:**
1. Listen carefully to sounds
- Scratching: Likely mundane vermin or gremlins
- Giggling: Possibly fae
- Purring/meowing: Escaped familiar
- Slurping or chewing sounds: Possibly mimics 🔴
2. Leave out test offerings overnight
- Cheese: Appeals to vermin and some fae
- Shiny objects: Attracts gremlins
- Milk in saucer: Traditional fae offering
- Small amount of gold: If it disappears, probably fae or gremlins
3. Check for physical evidence
- Droppings indicate type of creature
- Tooth marks on wood
- Small items going missing
- Repairs mysteriously completed overnight = helpful brownies
**Solution:**
- Vermin: Standard pest control, hire ratcatcher
- Brownies: Leave offerings, do NOT attempt to pay them or see them directly (they'll leave)
- Gremlins: Traps baited with mechanical components, relocate outside castle grounds
- Familiar: Locate owner, facilitate reunion
- Mimic larvae: 🔴 **EVACUATE AND CALL PROFESSIONALS IMMEDIATELY**
**Warning:** Never attempt to remove brownies. They're helpful and provide free household labor.
---
## Magical Interference
### My scrying mirror only shows infomercials 🟢
**Possible Causes:**
- Mirror locked to commercial frequency
- Previous owner's subscription still active
- Insufficient scrying power/focus
- Mirror has been cursed by marketing wizards
**Diagnostic Steps:**
1. Check mirror settings
- Locate frequency dial (usually on frame edge)
- Verify it's not stuck on channel 666 (Home Shopping Abyss)
2. Clear browser history
- Scrying mirrors retain viewing history
- May be serving targeted ads based on previous owner's interests
3. Test scrying ability
- Attempt to scry a known location (your own front door)
- If successful, mirror works but needs tuning
- If still showing infomercials, hardware issue
**Solution:**
- Retune to desired frequency
- Cancel unwanted subscriptions (call 1-800-UNSCRY)
- Factory reset mirror if needed (see Section 13: Mirror Configuration)
- Consider upgrade to premium scrying service for ad-free experience
**Quick Fix:** Cover mirror with cloth when not in use to prevent unwanted broadcasts
---
### Teleportation spells keep sending me to the wrong room 🟡
**Possible Causes:**
- Castle spatial reorganization without updating teleport markers
- Dimensional drift affecting coordinates
- Someone moved your teleportation anchors
- Castle has developed spatial non-euclidean properties
**Diagnostic Steps:**
1. Test with known safe location
- Teleport to main entrance (should be stable)
- If this works correctly, issue is with specific markers
2. Check for recent castle modifications
- Renovations, room additions, or tower construction
- Any of these invalidate old teleport coordinates
3. Inspect teleportation anchors
- Located in corners of each room (small crystal markers)
- Verify they haven't been moved, damaged, or stolen
- Check for magical interference near anchors
4. Cast spatial diagnostic
- `castle.spatial.verify()`
- "non-euclidean" result = you need expert help
**Solution:**
- Remap entire castle teleportation grid (tedious but necessary)
- Replace or repair damaged anchors
- If non-euclidean: Hire dimensional architect for evaluation
- Temporary: Use mundane stairs until issue resolved
**Safety Note:** Disable teleportation if sending you outside castle walls or into solid objects
---
## General Diagnostics
### I followed the troubleshooting steps but the problem persists
**Next Steps:**
1. Check for multiple simultaneous issues
- Some symptoms have overlapping causes
- You may need to resolve several problems
2. Verify you have sufficient permissions
- Some castle systems require owner-level authorization
- Previous owner may have left restricted settings
3. Review castle log files
- Access: Control Chamber > System Logs > Past 7 Days
- Look for recurring error messages or warnings
4. Consider professional assessment
- Some issues require specialized expertise
- Contact Castle Support for remote diagnostic
---
### How do I prevent future problems?
**Maintenance Schedule:**
**Daily:**
- Visual inspection of high-traffic areas
- Check ward crystal levels
- Verify dragon/creature status
**Weekly:**
- Test all magical systems
- Inspect perimeter and structural integrity
- Review automation logs
**Monthly:**
- Deep clean summoning circles
- Service HVAC and plumbing
- Recharge all ward crystals
- Check ley line connection
**Quarterly:**
- Full system diagnostic
- Professional chimney sweep
- Creature health examinations
- Update teleportation grid
**Annually:**
- Comprehensive magical system audit
- Structural engineering inspection
- Curse detection sweep
- Enchantment refresh
---
## Emergency Contacts
**Castle Support:** support@wizardcastle.arcane
**Emergency Services:** Node 911
**Dimensional Stability:** Node 447-DIM
**Pest Control:** Node 555-PEST
**Exorcism Hotline:** Node 666-BEGONE
**Structural Engineering:** Node 123-BUILD
**After-Hours Emergency:** For life-threatening situations only, send an emergency flare spell (red) and evacuate to safe distance.