菜单
Roleplay community culture and player intent behind The BASICs chat features. Read before designing, defaulting, gating, or writing copy for any RP-facing surface. Captures how RP players actually use these features, which is often not inferable from the code.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/BASIC-BIT/Vintage-Story-Mods --skill rp-culture命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | rp-culture |
| description | Roleplay community culture and player intent behind The BASICs chat features. Read before designing, defaulting, gating, or writing copy for any RP-facing surface. Captures how RP players actually use these features, which is often not inferable from the code. |
| compatibility | opencode |
| metadata | {"audience":"maintainers","domain":"product-design"} |
The BASICs is a roleplay mod. Most of its features look, from the code, like generic chat plumbing: ranges, channels, prefixes, toggles. The reasons players and server owners actually want them come from roleplay community culture, which is not derivable from the source and is easy to get subtly wrong while writing something that compiles, passes review, and ships.
An agent working here will understand roleplay conceptually. That is not the same as knowing the culture. This file records the specific cultural facts as they come up, so design decisions stop being re-derived (or re-guessed) each time.
Read this before:
When you learn something new about how players use this, add it here. That is the point of the file. The entries below are a growing list, not a complete one.
They look like the same feature at two ranges. They are not, and treating them as one is how you get a wrong config surface.
Local OOC ((...), /ooc) is meta-commentary inside a scene. A player is mid-roleplay and needs to say something as themselves, to the people physically present: reacting to something that happened in-game, "brb", clarifying a confusing action, sorting out whose turn it is. It is tightly coupled to the scene and to the people in it. Range matters, because the audience is "the people I am currently roleplaying with".
Global OOC (((...)), /gooc) is roleplay coordination across the server. Announcing an adventure and looking for people to come along, asking if anyone is around to run a scene, organising. It works as a substitute for general chat, and it exists mainly because everyone is already looking at the roleplay tab. Range is irrelevant by definition.
A player being deliberate about it will usually split these:
The distinction between general chat and global OOC is soft and plenty of players do not observe it. But the split is real for the players who care, and it is why global OOC is not simply redundant with a channel the game already has.
Config decisions on this mod are made by roleplay server administrators, not by the players using the feature. Their reasoning is frequently about protecting the fiction, not about performance, safety, or preference.
Examples of real motives behind toggles:
When choosing a default, ask what a roleplay server owner would want out of the box, not what is most permissive or most featureful. The default config for this mod deliberately leans feature-forward for RP servers (see docs/FEATURES.md, "Default Configuration Philosophy").
This recurs constantly and should be decided deliberately each time rather than by habit. For any given behavior there are up to three levels:
Default to the lowest level that solves the actual need. Adding config later is easy; removing config from a live mod is not. Level 3 is what RP servers with a house style eventually ask for, but "eventually asks for" is not the same as "needs now".
As of #207 the mod has two independent axes, and the terminology was chosen carefully. Keep it consistent in code, copy, and docs.
| Axis | Term | Values | Commands |
|---|---|---|---|
| How far it carries | chat mode | whisper, normal, yell | /whisper /say /yell |
| What kind of message | chat type | in character, emote, OOC, global OOC | /me /ooc /gooc |
Rejected names, and why (do not revisit without new information):
"Chat type" is deliberately bland. Its job is to stay out of the way while the values (in character, OOC) carry the meaning, because RP players already think fluently in IC/OOC.
RP players type *, (, (( thousands of times. These are not discoverable UI, they are motor habit built over years, often carried between servers and between games.
Consequences:
/me park the player in emote mode where it used to be a harmless "missing argument" error. That is the intended feature, but on a server with years of muscle memory it is the most likely source of "the update broke chat" reports.**) over redefining existing syntax.Recorded so they are not silently answered by whoever touches the code next.
ChatHistoryPermission, default commandplayer), so it is effectively an admin/staff surface rather than a player one.[OOC] / [GOOC] prefixes are currently fixed strings. Server owners may want custom labels, shorter markers (a bare G), or no brackets. See the issue tracker.Product decisions here are currently made from intuition and a handful of Discord reports. The mod has a large installed base and an enormous amount of accumulated player typing time, and almost none of it is being measured.
An analytics system exists (src/ModSystems/Analytics/) with root-admin consent, three levels (off, server, personalized), and a repeating prompt. Treat verifying and using it as a first-class task, not a chore: the questions in this file (which chat types get used, which toggles get flipped, which commands get attempted while disabled) are answerable with data rather than argument.
Signals worth having, noted as they come up:
Roleplay community culture and player intent behind The BASICs chat features.
Prepare owner-reviewed Vintage Story release changelogs and automate ModDB uploads using Playwright when direct API upload is unavailable.
Prepare and publish Vintage Story ModDB releases, including owner-reviewed public changelog copy and Playwright browser upload when direct API upload is unavailable.