Home
-
Latest update: August 1, 2026
Welcome to DSPACE v3.1.0!
This release makes token.place the default provider for NPC Chat. Fresh players can open /chat, pick a persona, and ask for quest, item, process, or save-aware help without signing in and without bringing an API key.
token.place is the default Chat provider
DSPACE now sends Chat requests to token.place API v1 by default. The integration uses direct HTTPS requests to
POST https://token.place/api/v1/chat/completionswith an OpenAI-compatible request shape and reads the reply fromchoices[0].message.content.A few important user-facing details:
/chatworks without DSPACE auth, an OpenAI API key, or token.place credentials.- DSPACE does not ask users for token.place credentials and does not store token.place credentials.
- The API v1 path is non-streaming, so the reply appears after the full completion is ready instead of arriving token-by-token.
- DSPACE uses direct HTTPS API v1 requests for now. The integration will move to the token.place npm package only after that package path is ready for this use case.
OpenAI remains optional
OpenAI is still available for players who want to bring their own key. Choose OpenAI from /settings, save your key there, and return to /chat. The key remains in the existing client-side DSPACE storage path; token.place requests do not use it.
If you do not choose OpenAI, there is nothing to configure. token.place remains the v3.1 default.
Operators can override the token.place origin and model at build time with
VITE_TOKEN_PLACE_URLandVITE_TOKEN_PLACE_CHAT_MODEL; those are the approved env vars for this rollout.QA and rollout notes
Maintainers should use the v3.1 QA checklist for staging and production promotion. That plan verifies the API v1 endpoint, no-auth request contract, provider settings, non-streaming behavior, error handling, and rollback options without making OpenAI the default again.
View all updates - OnlineHydration time: 0 ms
