AI 产品解读Bridge/connector between the 5etools D&D 5e reference website and Foundry VTT, enabling one-click transfer of game content and dice rolls
Manually transferring creatures, spells, items, and dice rolls from 5etools into Foundry VTT is tedious and error-prone. Rivet automates this by relaying data from the 5etools webpage directly to the Foundry VTT instance running in another browser tab.
User browses 5etools in one tab → clicks a send button next to an entity or rolls dice → Rivet content script captures the event → service worker finds the Foundry VTT tab (localhost:8080/game) → relays data to Foundry VTT's Plutonium module for import
Send 5etools entities (creatures, spells, items) to Foundry VTT with one clickAutomatically relay dice rolls from 5etools to Foundry VTTOption to whisper rolls (GM-only visibility)Toggle automatic roll sending on/offSHIFT-click for temporary actor/item importWorks with Plutonium module in Foundry VTT
- 目标用户
- D&D 5e players and DMs who use both 5etools and Foundry VTT / Game masters running Foundry VTT sessions who reference 5etools content
- Cannot verify Foundry VTT side (Plutonium module) behavior as it runs outside the extension
- Extension is very small (~42KB) with minimal code; straightforward message-passing architecture
付费分析未识别到付费功能
No payment integration, no premium feature gating, no upgrade UI, no billing/subscription/checkout code. All keyword hits for 'pro' are false positives from JavaScript Promise constructors. The 'license' hit is the MIT open-source license file. The extension provides all features freely with no tiered access.
- 置信度
- 98
- 支付平台
- --
- 来源
- AI / 高
- 需要登录
- 否
- 登录理由
- The extension operates entirely locally as a message bridge between the 5etools website DOM and Foundry VTT browser tabs. It uses no authentication, no login UI, no account creation, and no external service requiring credentials. The only external host is localhost:8080 (standard Foundry VTT local server). The 'jwt' keyword hit is from base64-encoded content hashes in the Chrome Web Store metadata file, not authentication. The 'auth' hit is from the MIT license warranty disclaimer.