Back
DEV UTILITY SCRIPTS
// No Screenshots

Overview

What is this?

Not every project is a game or a mod. This is a living set of scripts that have accumulated over years of development work — each one built because a task was done manually too many times and the frustration threshold was finally crossed.

The collection covers four main areas: document processing (primarily PDFs), file system automation, Windows system configuration, and GPU/compute workflow tooling.

  • PDF metadata stripping automation
  • Batch file pipeline scripts
  • Windows registry configurations
  • GPU task optimisation scripts
  • Ongoing personal toolchain

Technical Breakdown

What's in the Collection

PDF Metadata Manipulation
Python
Scripts using PyPDF2 and pikepdf for stripping, rewriting, and auditing PDF metadata fields. Built for handling academic submission documents where metadata needs to be clean before submission. Handles bulk operations across directories with logging.
File Organisation Pipelines
Python
Batch renaming, sorting, and deduplication scripts. The most-used is a recursive duplicate finder that hashes files and produces a report before any deletion — no silent data loss.
Windows Registry Tweaks
PowerShell
A set of idempotent registry modification scripts for system configuration. Covers context menu cleanup, display scaling overrides for specific apps, and disabling specific telemetry services. Each script is reversible.
GPU Workflow Optimisation
PowerShell
Scripts for managing GPU task priority and VRAM allocation across concurrent workloads — specifically for running Topaz Video AI alongside a development environment without one starving the other of VRAM. Includes a quick-toggle for hardware scheduling modes.

Challenges & Lessons

What Scripting Has Taught Me

The most important habit this collection enforced is writing scripts that are safe by default — dry-run mode, confirmation prompts before destructive operations, and log files for everything. The first version of the duplicate finder deleted files without asking. That happened once.

Key lesson Automation that can delete or modify files should always default to preview mode. The extra friction of a confirmation step has never cost more than it has saved.

PowerShell's COM interop for Windows system tasks is genuinely powerful but poorly documented in places. Several of the registry scripts went through multiple rewrites to handle edge cases around UAC elevation and WOW64 registry redirection on 64-bit Windows.