Repository: anchapin/ModPorter-AI
Author: anchapin
## Overview
After validating core conversion quality and acquiring initial paying users, integrating PortKit into the existing Bedrock development toolchain is the highest-leverage distribution move available. This issue tracks the investigation and implementation of plugin/extension integrations.
## Rationale
Marketplace creators and serious Bedrock add-on developers already live in tools like **bridge.**, **Blockbench**, and **VS Code**. A PortKit plugin that triggers a conversion from within their existing workflow removes the biggest friction point: switching to a new standalone SaaS.
Key insight: **a plugin can call back to the PortKit cloud API**, so this is a distribution surface, not a separate product. The conversion engine, billing, and subscription remain centralized.
## Target Integrations (Priority Order)
### 1. bridge. Plugin (Highest Priority)
- bridge. is the most-used Bedrock add-on IDE
- Plugin ecosystem exists and is actively maintained
- Marketplace creators are already here daily
- A "Convert from Java" action inside bridge. is a natural fit
### 2. VS Code Extension
- Bedrock scripting workflows increasingly use VS Code
- Large developer audience; extension marketplace has good discoverability
- Could surface conversion suggestions inline when editing Bedrock add-on files
### 3. Blockbench Plugin
- Focused on 3D model/entity creation — less directly relevant to full mod logic conversion
- But asset conversion (models, textures) is a key sub-task; a Blockbench plugin for that subset could be valuable
## Implementation Approach
- Expose a stable **public REST API** (or reuse the existing API with API keys) that plugins can call
- Plugin authenticates with the user's PortKit API key
- Plugin sends the mod/source files and receives converted output + conversion report
- Subscription enforcement happens server-side (no changes needed per plugin)
## Pre-conditions Before Starting
- [ ] Core conversion quality validated against real commercial/Marketplace-tier mods
- [ ] Stable public API with versioning (`/api/v1/convert`)
- [ ] API key management feature live (Issue #X)
- [ ] At least some paying users confirming the product is worth building distribution for
## Notes
- **Do not start this before the above pre-conditions are met** — plugin distribution amplifies a working product, it doesn't fix a broken one
- bridge. plugin API docs: https://bridge-core.app/plugin-docs/
- VS Code extension docs: https://code.visualstudio.com/api
- This is a **post-launch growth lever**, not an MVP feature
## Labels
- `enhancement`, `post-launch`