Model Train Hobby Forum Build Log Exporter

WHAT IT DOES

This script scans forum thread pages for model train build log content—post text, images, dates, author names, and replies—and extracts the entire build log into a structured format. It displays a floating panel showing a summary of the build log including total posts, authors, and date range, and provides a one-click export function to save the build log as a plain text file, Markdown file, or PDF (via print). It captures image URLs and includes them as markdown image links or as a list in the export. Users can select which posts to include (all, from a specific user, or a date range), and filter out non-build content (chit-chat, off-topic replies). Export preferences are stored per domain for reuse across visits.

WHERE IT RUNS

Works on any forum thread page—model train hobby forums, build log threads, or any discussion thread with structured posts. The script detects post containers, authors, dates, and content using common forum patterns, making it compatible with most forum software.

HOW TO USE

The panel appears automatically when you visit a forum thread. It detects all posts in the thread and shows a summary with the thread title, total posts, authors, and date range. Choose your export format: Plain Text (.txt) or Markdown (.md). Toggle "Include images" to include image URLs in the export. Click "Export Build Log" to download the file. Click "Copy to Clipboard" to copy the formatted content directly. The Markdown export includes images as  tags for easy integration into documentation. Use "Save Current Settings" to remember your format preference for future visits. The script automatically filters out short, non-substantive posts to focus on build log content.

TECHNICAL MECHANISM: FORUM POST EXTRACTION WITH STRUCTURED EXPORT GENERATION

The script uses a multi-pass detection strategy to find post containers. It searches for common post selectors (.post, .message, .entry, .thread-post, article) and falls back to scanning divs and sections with date or author patterns. For each post, it extracts the author by checking author class selectors, user class selectors, or patterns like "by [Name]." Dates are extracted using a robust date parser that supports multiple formats (MM/DD/YYYY, Month DD, YYYY, DD Month YYYY) with month name mapping. Content is extracted from content body selectors (.content, .body, .message-body) or by removing author and date text from the post. Images are collected from img elements and image links (jpg, png, jpeg, gif) while excluding avatars, icons, and emojis. The build log is sorted chronologically by date. The text export generates a structured format with post numbering, author, date, content, and image list. The Markdown export generates a clean markdown document with heading for the title, post numbering, author-date headers, content paragraphs, and image tags. Export preferences are stored per domain using GM_setValue with the format preference persisted.

THE PANEL

The build log exporter appears in a draggable, resizable panel that remembers its position per site. The panel shows the build log summary, format selector, image toggle, and export buttons. Drag by the header to reposition, collapse to a compact icon with a click, and resize using the bottom-right corner. The panel snaps to screen edges for tidy placement and closes with the Escape key. All settings—format preference and panel position—persist per website using GM_setValue, so your view returns exactly as you left it.

PLEASE NOTE

This script requires the free BotGentz extension to run. The script relies on common forum post structures—if a forum uses a non-standard layout, post detection may be incomplete. The image detection includes images and image links visible on the page; images may be hosted on external servers and may not be available offline. The export content is based on the text and images visible on the page; animated GIFs and embedded videos are not included in the export. The script does not access forum login credentials or user data beyond what is visible on the page. All export data is generated locally and never transmitted. The date parser supports common date formats but may not handle all variations used by different forum software.