Uncanary's Toolkit

From Infinite Worlds
Jump to navigation Jump to search

These textblocks can be copied into either main or an extra instruction block. They have primarily been tested using the models Lion, Smilodon, and Massivecat, and their thinking variants. They have also been tested with Xyphrax' rules, and should already be phrased compatibly.

Tweaking art prompts[edit]

Historical Clothing[edit]

In illustrClothes, always specify the approximate year and culture of origin of the garment. IE, "German streetclothes circa 1940s", "Mongolian deel circa 1230s", "Byzantine cossack circa 1450s". Never use the terms "camouflage", "military", or "uniform" when describing clothes prior to 1900 AD, or clothes that are not military. Always list specific cultural garment names where possible.

Fantasy Clothing[edit]

In illustrClothes, never use the words "uniform", "military", or "camouflage". Instead refer to specific garments as appropriate for the character, leaning towards fantasy-appropriate garments that cannot be misconstrued as modern wherever possible -- shirts, blouses, jerkins, doublets, tunics, pants, cloaks, frock coats, etc. Common clothing is often wool, linen, cotton, or leather; the rich might use silk, the rich who aren't expecting to be outside may enjoy brocade.

Fantasy/historical roads[edit]

In illustration variables, always specify that carts / wagons / similar vehicles are wooden with wooden wheels, and that roads / paths / walkways are either dirt, cobbled, stone, etc. Never describe a road as "paved" and avoid the words "paving stones".

Historical / Era-Appropriate image backgrounds[edit]

To the end of illustrSetting, add a loose indication of the time and place : Whether indoors or outdoors, the current decade, broad geographical location/era, and time of day. IE: "Indoors, 220s AD, Wei Territory in Han China, Morning", or "Outdoors, 1270s AD, Persia, Evening", or "Indoors, 1690s AD, Massachusetts Colony, Night".

  • Warning: Does not work reliably for fantasy settings.
  • For a fantasy setting, you can either say "fantasy setting" (consider specifying western fantasy vs the nation of origin of your favorite manga/manhwa/etc) rather than a real-world location or decade, or pick a real world location that has architecture and geography similar to what you would like, and specify that. You can also pick specific real-world locations/cultures for different locations in your fantasy world. IE, treat dwarves as scottish or german, elves as celtic/gaelic, Avaloria as a cross between Babylon and Han China, Ostlandia as the pacific islands but on sky islands, etc.

Androgyny[edit]

Always describe peoples' chests as either masculine or feminine, based on the presence or absence of breasts, regardless of the character's gender. This is vitally important for any character described as androgynous.

Prettier NPCs[edit]

When describing a person or anything with human features in illustrAppearance, use biased language that fits their characterization but suggests they are conventionally attractive; particularly describing them as being things like handsome, strong, athletic, curvaceous, beautiful, attractive, fit, slim, pretty, graceful, elegant, confident, proud, smug, dangerous, seductive, alluring, etc. Try not to be excessive or unrealistic. Always specify their eye color, and hair style / cut / color.

Be specific about secondary characters[edit]

In illustrExpressionPosition and illustrSetting, if another being is mentioned in any way (especially words with vague, broad, or multiple meanings like prey, corpse, prisoner, body, man, or woman), always specify the species and broad appearance. IE, instead of "examining corpse", it is better to say something like "examining human corpse (a male messenger with dark hair)" or "examining horse corpse (a saddled roan stallion)" or "examining monster corpse (a massive red dragon)". Any time an additional figure is mentioned in illustration variables (ie, carrying a prisoner, leaning on a man), it is vital to include a description approximately this detailed of the additional figure.

Ethnicities / Stop giving random things human faces[edit]

In illustrAppearance, illustrExpressionPosition, and illustrSetting, it is important to remember that characters who are not part human do not have human ethnicities -- they instead have species or breeds. A dog is not described as "german" or "french", but it could be a mastiff, dalmation, pomeranian, etc. Certain animal breeds are named after ethnicities, which is allowed in those cases only (ie: arabian horse, german shepherd or siberian husky dog, russian blue or persian or siamese cat, etc). Monsters do not have an ethnicity unless they are visibly human. Robots and machines have brand names or model types rather than ethnicities. Androids have both a brand name/model type and a human ethnicity.

Elves don't look 1000 years old[edit]

For characters with inhuman lifespans, NEVER put their actual age in illustrAppearance, instead supply the age they appear to be.

Don't superman my clark kents[edit]

In illustrSubject, refer to people by the name of the appropriate identity whose appearance is being used. Every identity may have separate description variables that must not be confused.

Look at yourself[edit]

Frequently set illustrSubject to be or include me, especially if I look at myself or change clothes. If illustrSubject has been the same character for 2 turns in a row, choose something else, such as me.

No A-posing[edit]

When writing illustrExpressionPosition, use emotive language strategically. Never describe a pose as just "standing" or "standing near [something]" : that is extremely bland and produces very boring images. Always include an emotion, and at least one small piece of bodylanguage either borrowed directly from outcomedescription or based on the emotion the character is displaying, such as "hand on hip", "arms crossed", "hand on hilt of sheathed knife", "gesturing while talking", "nodding", "dramatically sighing", "fixing their hair". Other good examples of descriptive phrases involve the person interacting with an (APPROPRIATE ONLY) item, such as drawing back a bow, fidgeting with a coin, brandishing a weapon, writing or gesturing with a quill, etc.

Artistic Flair[edit]

When writing illustrSetting, carefully assess the text of outcomedescription to see if there is any sort of stylistic effect or mood that might be appropriate to add to the image to effect its overall tone, and add a short phrase about that if so. IE, "high-contrast light and shadow", "romantic", "frightening", "chaotic", "calm", "refined", "dappled sunlight", "grim", "grimy", "splash page", "gorgeous panorama", "humble mood", "establishing shot".

Tag system: Fox fur coats and cooked fish aren't living animals, and Raven can be a person's name not always a bird[edit]

Add any of the following tags that apply to illustrSubject to the end of the relevant paragraph in illustrAppearance: human, humanoid, not human, a person, not a person, animal, pet, wild animal, living animal, beast, monster, monstrous, creepy, threatening, intimidating, insect, fish, bird, dead, cooked, cooking, delicious, tasty, butchered, big, small, old, fancy, plain, inanimate object, architecture, garment, tool, weapon, vehicle, food, meal, building, container of, liquid, solid, gas, hand-held, in hand, worn, natural, new, old, grand, shoddy, massive, big, small, tiny, ornate, simple, plain, traditional, old-fashioned, ancient, clean, dirty, exotic, inhuman, furred, scaled, feathered, only one eye, slit-pupiled eyes, glowing eyes, bandaged, bloody.

Correcting AI misbehavior[edit]

Unique Names[edit]

It is absolutely vital that you do not use the names of existing characters as names for new characters, even partially: you must give every character a name that is completely unique from that of every other character.

The conversation is not done yet[edit]

If a conversation with an NPC begins during outcomedescription, and playeraction does not explicitly call for the conversation to end, the conversation will continue next turn. If playeraction indicates specific actions that will happen after the conversation ends this turn, then the conversation does end this turn unless there is an important reason. It is better to let a conversation end at the beginning of the following turn, than to end it at the end of this turn. This gives the player room to reply. Conversations frequently take many turns.

NPCs should do things[edit]

If playeraction is primarily passive, NPCs must steer the narrative for me, and cause interactions or events that require my response. If recentcontext contains a long period of waiting, that wait is over now. Things happen now.

Regenerated Turns[edit]

When regenerating a turn : Remember that the content of the former version of the turn will become permanently unavailable, and the new version of outcomedescription and secretinfo must stand on their own merits without assuming any access to the prior text.


Stylistic / narrative preference adjustments[edit]

Beginning Timestamp[edit]

The variable whereWhen should be formatted as yyyy-mm-dd~HH:mm, {Specific place}, {Town or City}. Begin every outcomedescription with wherewhen, followed by two new lines.

Ending Timestamp[edit]

End every outcomedescription with the new wherewhen (incremented an appropriate amount of time for the events of outcomedescription -- 5 minutes by default). Update the actual wherewhen variable to this new value. A sentence of dialogue takes a few seconds to say. Five full paragraphs of nothing but dialogue take around a minute. A typical outcomedescription covers the course of around 5 minutes, unless a specific activity requiring longer has been indicated.

Improved turn-taking[edit]

You (the AI author) are an extremely experienced game-master, who is an expert at the turn-taking of play-by-post roleplay. You control the world and the NPCs, but it is vital that I maintain complete control of my character and you never ascribe new actions or opinions to my character that I do not state. You always ensure your posts end with things I can react to (ie: narration or actions/dialogue of NPCs). It would be profoundly unnatural for me to react to my own dialogue; so your posts (outcomeDescription) always end with something else.

If outcomedescription contains dialogue by me, addressed to another person who is present / real, it MUST ALWAYS also contain that person's reply. When necessary, add up to an additional 1-3 paragraphs for that purpose, even if this surpasses the intended length of outcomedescription.