Venus Chub AI searches commonly lead to Chub’s character platform. Its appeal is the ability to work separately on a character card, supporting lore, model configuration and conversation branches. That control is useful if you enjoy authoring a roleplay setup. If you mainly want to design a character and begin chatting, Cherrypop’s guided creator may suit your task better.
Build the character before adding the world
Chub’s character-creation documentation provides separate places for the character description, scenario, first message and example dialogue. These are prompt inputs, not evidence that the model will follow every instruction. Start with the facts that define the character even when the setting changes.
Our example is Dr. Ellis, a 45-year-old astronomer preparing an observatory for a public demonstration. Three stable facts are enough to begin: Ellis checks measurements before making claims, explains unfamiliar terms plainly, and dislikes rushing a delicate repair. The immediate situation is a telescope that will not track a calibration star. The first message should present that problem and leave the visitor a choice of what to inspect.
This setup is more useful than a long list of flattering adjectives because it gives the conversation a decision. It also makes a bad reply easier to diagnose. If Ellis becomes impatient without reason, examine the character instructions. If the telescope suddenly becomes a submarine, examine the setting and recent context.
Use lore for information that becomes relevant later
A Chub lorebook inserts information when matching keywords are found. Scan depth controls which recent messages are checked, and a token budget limits how much lore can be added. Default matching uses whole words without case sensitivity. Entry priorities matter when the budget is exceeded.
| Layer | Original example | Purpose |
|---|---|---|
| Character card | Ellis values careful measurement | Stable behavior across scenes |
| Scenario | An observatory demonstration begins tonight | The starting situation |
| Lore entry | Keyword: lens; note: the spare lens is in cabinet B | Relevant background when that object is discussed |
| Conversation summary | The visitor already checked the power cable | What changed during this particular session |
Keep the lens entry short and specific. A keyword as broad as “the” would be a poor choice for this example because it does not distinguish the relevant moment. A large document about every instrument would also make it harder to tell which fact you intended to supply.
If expected lore does not appear to influence a reply, check the actual keyword, the scan range and the available budget before rewriting the whole character. The documentation describes several additional entry conditions, so an apparently correct keyword is not proof that every condition was met.
Branches and summaries solve different problems
The chat guide describes a full chat tree, a memory summary and export options. A summary supplies compressed conversation context. A branch lets you follow another continuation. Neither is a promise that the system remembers everything indefinitely. The same guide says character edits made for a particular chat can be local to that chat.
In the observatory example, you might want to compare inspecting the tracking motor with replacing the lens. Treat those as alternative branches. Do not put both outcomes into one summary as if both occurred. A useful summary for the motor branch would retain the completed cable check and the next agreed inspection; the lens branch would have a different sequence of events.
Save your original character notes separately from a session summary. The notes describe who Ellis is. The summary describes what this visitor and Ellis have done so far. Mixing these makes a one-session event look like a permanent personality trait.
Change one configuration layer at a time
Chub’s prompting guide explains the assembled prompt, including system instructions, character material and conversation history. The practical implication is that editing a card and changing model settings simultaneously makes results difficult to compare. Keep the same opening and change one control when investigating a specific problem.
For a small evaluation, record the model, relevant preset, card revision and opening. Check whether a reply follows the character’s established manner, respects the known setting and leaves the next choice understandable.
Choose Chub for configuration or Cherrypop for guided creation
Chub’s documented controls suit people who want to manage cards, lore and model configuration themselves. Cherrypop offers a different route: start with appearance and personality, define the scenario and first message, then move into character chat. It also has image and video generation tools for expanding an original character concept visually.
To adapt your own observatory concept, open Cherrypop Create. Define an adult astronomer, put the demonstration problem in Scenario, and use First Message to ask the visitor which instrument to examine. This is a manual adaptation of original notes, not a claim that Cherrypop imports Chub cards or lorebooks.
Cherrypop is free to start with limits; some features require Premium and Cherries. If you want to spend your time shaping the character rather than assembling model settings, create the character in Cherrypop. Choose Chub when its additional configuration layers are themselves part of what you want.