DedSec-Style Tool

Use This Guide When

Before You Run Anything

• Back up personal settings, outputs, modified scripts, and saved data before reinstalling or updating.
• Confirm the exact DedSec folder and current Git state instead of cloning another nested copy.
• Preserve the full first error rather than replacing the entire installation immediately.

Diagnostic Or Setup Commands

Back up personal DedSec settings and outputs first. Confirm the current DedSec folder before copying or running the block.

mkdir -p ~/DedSecTool/{data,logs,exports}
touch ~/DedSecTool/logs/run.log
nano ~/DedSecTool/main.py
python ~/DedSecTool/main.py

What The Commands Tell You

• Run the example one line or logical block at a time and compare each result with the stated goal.

What Success Looks Like

• The intended DedSec launcher starts from the documented folder.
• Personal settings and saved output remain present after the repair or update.
• A second launch works without repeating installation steps.

Safe Next Steps

1. Identify whether the failure is a folder, dependency, Git, permission, or saved-data problem.
2. Repair only that layer and run the smallest DedSec entry-point test.
3. Compare changed files before replacing local modifications.
4. Keep a dated backup after confirming the repaired version starts correctly.

Common Mistakes

• Deleting the existing DedSec folder before copying personal settings and outputs.
• Creating repeated nested clones such as `DedSec/DedSec/DedSec`.
• Running a replacement command from the wrong language or project folder.