Jsk Studio F95zone May 2026
For developers who prefer a no‑code approach, the plugin can expose a “Generate markdown” button that copies the output to the clipboard, allowing manual posting if the API is unavailable. 7️⃣ UI Mock‑up (Textual Description) +--------------------------------------------------------------+ | JSK Studio – Bottom Panel | |--------------------------------------------------------------| | [F95Zone] Connect | Status: Connected as <username> | |--------------------------------------------------------------| | Game Title: <input> | Category: <dropdown> | | Version: <input> | Cover image: <preview + upload> | |--------------------------------------------------------------| | [Publish Build] [Sync Changelog] [View Thread] [Analytics]| |--------------------------------------------------------------| | Unread Replies: 3 (badge) | Views: 1,254 Likes: 87 | +--------------------------------------------------------------+ All controls are optional – the developer can enable only the parts they need. 8️⃣ Testing & QA Checklist | Test | Description | |------|-------------| | OAuth flow | Verify token retrieval, expiration handling, and revocation. | | Thread creation | Mock API response; ensure markdown is correctly escaped. | | Update comment | Confirm that only the new part of the changelog is added. | | Badge count | Simulate a new reply and confirm badge increments. | | Analytics | Use a fake stats endpoint and verify chart rendering. | | Error handling | Force 429/500 responses and verify exponential back‑off. | | Security | Run static analysis to ensure no token leaks in logs. | | Cross‑platform | Test on Windows/macOS/Linux installations of JSK Studio. | 9️⃣ Release Plan | Milestone | Scope | Approx. Effort | |-----------|-------|----------------| | MVP | OAuth, thread creation, markdown
| Use‑case | How the Bridge helps | |----------|----------------------| | on F95Zone when a build is published from JSK Studio. | Generates a markdown‑ready post with title, description, version, changelog, cover‑art and download link. | | Sync changelog & screenshots whenever a new commit is pushed to the project repo. | Updates the existing thread (or creates a new “Update” post) with the latest screenshots and release notes. | | Two‑way notification – get forum replies or private messages inside the JSK Studio UI. | Shows a badge in the IDE with the count of unread forum replies; clicking opens a small chat‑like panel. | | User‑based access control – only allow verified developers to post on behalf of the game. | OAuth2 login via F95Zone’s API (or a custom token flow) stores a short‑lived access token per developer. | | Analytics dashboard – view page‑views, download clicks, and “likes” directly in the studio. | Pulls public statistics from F95Zone (or parses the thread HTML) and visualises them in a tab. | 2️⃣ High‑Level Architecture +-------------------+ +----------------------+ +-------------------+ | JSK Studio IDE | HTTP | JSK‑F95Connector | HTTP | F95Zone API / | | (plugin UI) +--------->| (Node/TS backend) +--------->| Webhooks / HTML | +-------------------+ +----------------------+ +-------------------+
/** * Pull unread replies (used for badge count). */ export async function getUnreadCount( threadId: string, token: string ): Promise<number> const data = await authFetch( `https://api.f95zone.to/v1/threads/$threadId/replies?unread=true`, token ); return data.unreadCount ?? 0; jsk studio f95zone
// store threadId for later updates await context.state.set("f95_thread_id", threadId); context.ui.notify(`Thread created: $url`);
## Changelog $changelog `;
/** * Helper – perform an authorized request. */ async function authFetch( url: string, token: string, init: RequestInit = {} ) { const res = await fetch(url, { ...init, headers: { ...(init.headers ?? {}), Authorization: `Bearer $token`, "Content-Type": "application/json", }, });
async function publishRelease(context) const token = await context.secrets.get("f95_token"); // encrypted store const threadId, url = await createThread( title: `$context.game.title v$context.version`, body: buildReleaseMarkdown( version: context.version, changelog: context.changelog, downloadUrl: context.downloadUrl, coverImgUrl: context.coverImg, ), category: "Adult Game", , token ); For developers who prefer a no‑code approach, the
/** * Simple markdown builder – you can replace this with a template engine. */ export function buildReleaseMarkdown(opts: version: string; changelog: string; downloadUrl: string; coverImgUrl?: string; ): string const version, changelog, downloadUrl, coverImgUrl = opts; return ` # $opts.version – New Release!