Bahamut Gaming Forum & VOC Scraper

Collect structured, public discussion data from the Bahamut Gaming Forum (forum.gamer.com.tw) for game research, community monitoring, and auditable VOC analysis.

This Actor is purpose-built for Bahamut's bsn, snA, floor, comment, GP/BP, and board-search model. Generic phpBB or Discourse scrapers do not understand those relationships; broad web/forum search Actors usually return snippets instead of complete Bahamut threads.

Choose this Actor when

• You need to discover a Bahamut game board from a game/board name or start from known bsn values.
• You need keyword search inside selected boards with latest or GP-based ordering.
• You need the original post, every available floor, public comments, GP/BP, and available listing view counts in one discussion record.
• You need repeatable post-release monitoring that emits new or updated discussions and preserves a crawl audit.

Do not choose it for logged-in, age-restricted, deleted, private, or permission-gated content. The Actor records those URLs as inaccessible and does not bypass platform controls.

What it collects

Each successful discussion is one Dataset item containing:

• board bsn, discussion snA, board name, title, canonical URL, tags, and timestamps;
• original post and all available floors with content text/HTML, author identity handling, GP, BP, and timestamps;
• all public comments per floor with comment IDs, content, timestamps, GP, and BP;
• available view count from board listing discovery;
• public image URLs and external links referenced in content;
• pagination and comment completeness fields;
• source keywords/listings, monitoring status, and optional game version label.

The Actor never downloads images, videos, animations, or linked files. It excludes links hosted by Bahamut Anime (ani.gamer.com.tw) and Bahamut Store (buy.gamer.com.tw) and never visits external links.

Inputs

Provide at least one source:

• boardQueries: game/board names, such as 原神, for board discovery;
• bsns: known board IDs supplied as numeric strings, such as "36730";
• startUrls: direct public C.php discussion URLs.

The Console prefill uses one known public discussion and one-item limits so Apify's automated quality test can validate the Actor quickly. These prefill values do not change API, schedule, or Saved Task defaults; those runs must still provide at least one source.

Useful controls:

• keywords: searches every selected board. Empty keywords use board listings.
• sortBy: LATEST or HOT. Keyword hot ordering uses Bahamut GP sorting. Without keywords, hot ordering ranks the page-bounded candidates by GP.
• publishedAfter / publishedBefore: filter using the first floor's Asia/Taipei publication time.
• maxListPages, maxThreads, maxThreadPages: hard collection limits. maxThreadPages: 0 means all available thread pages.
• includeComments, includeImages, includeExternalLinks: output depth controls.
• authorMode: HASHED (default), RAW, or OMIT.
• authorHashSalt: optional secret salt for hashes stable across unrelated runs.
• proxyConfiguration: defaults to the verified Taiwan residential proxy route. The tested direct and generic data-center routes returned Bahamut HTTP 403 challenge pages; changing the proxy route can affect access and cost.

Example: keyword VOC collection

{
  "operation": "SCRAPE_DISCUSSIONS",
  "boardQueries": ["原神"],
  "keywords": ["更新", "卡頓", "閃退"],
  "sortBy": "LATEST",
  "publishedAfter": "2026-08-01",
  "maxListPages": 3,
  "maxThreads": 50,
  "maxThreadPages": 0,
  "includeComments": true,
  "authorMode": "HASHED",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "TW"
  }
}

Example: known board, popular discussions

{
  "bsns": ["36730"],
  "keywords": ["聖遺物"],
  "sortBy": "HOT",
  "maxListPages": 2,
  "maxThreads": 20,
  "includeComments": true
}

Incremental version monitoring

Run the same input repeatedly with the same monitor key. The Actor stores only fingerprints and monitoring metadata in a named Key-Value Store; successful discussion results remain in the current run's Dataset.

{
  "bsns": ["36730"],
  "keywords": ["7.0", "更新", "BUG"],
  "publishedAfter": "2026-08-12",
  "sortBy": "LATEST",
  "monitoring": {
    "enabled": true,
    "key": "genshin-7-0",
    "onlyNew": true,
    "includeUpdated": true,
    "versionLabel": "7.0"
  }
}

• First run: records are NEW.
• Later runs: unseen discussions are NEW; changed floors/comments/metrics are UPDATED; unchanged discussions can be skipped.
• Set reset: true only when intentionally starting a new baseline for that monitor key.

Audit and completeness

Audit records are stored in the default Key-Value Store so they are not mixed with business results:

• RUN_AUDIT: sanitized input summary, counts, deduplication, monitoring, and media policy;
• PAGE_AUDITS: requested/final URLs, response status, attempts, bytes, and timing;
• FAILED_URLS: failed, deleted, sensitive, or login-required URLs and reasons;
• INCOMPLETE_DISCUSSIONS: successfully parsed but capped/incomplete discussions. These are deliberately not pushed to the default Dataset.

completeness.is_complete requires all detected thread pages, expected floors when known, and requested comments to be present. View count can be null for direct URLs and keyword results because Bahamut exposes exact views on board listings, not consistently on every discussion/search response.

Responsible use

Collect only public data and follow applicable laws, Bahamut terms, and research ethics. Use conservative limits and delays. Hashed author IDs reduce direct exposure but are pseudonymous, not anonymous; use a private salt and restrict access when identity linkage is unnecessary.