Purpose of the LoRAMouth vore is a specific subtype of vore (consumption fetish) in which the miniature person (tiny/prey) is taken into the mouth of the larger character. The focus is on the lips, tongue, teeth, and oral cavity. It often emphasizes the sensory and visual aspects of the mouth: the lips sealing around the tiny, the tongue moving them, and saliva. It can range from soft/gentle (the tiny is held, licked, or gently sucked) to hard/predatory (which goes beyond the scope of this LoRA). In size-difference and shrinking contexts, it is extremely common because a mouth is a natural, intimate “container” for a tiny person.The mouthvore LoRA is trained gives users the choice of how the subject is entering the mouth, as illustrated in the gallery. How to use itSee examples in the gallery. Focus on the interaction between the 'miniature person' (whose appearance you can customize and describe) and the other character. Avoid referring to both as 'person'. For example, it can be the 'miniature person' and the 'man', or whatever its name is (if you use a character LoRA). The interaction is about the character's mouth and the miniature person's body, so be specific on this part. Limitations and combination with other LoRAsAs demonstrated in the gallery, the LoRA can be combined easily with character LoRAs. The giant person can be whomever you want. Depending on how the character LoRA was trained, it may contaminate the face of the miniature person; that depends on the character LoRA, not on this LoRA. If you want the miniature person to have a specific look, you should train a LoRA for that purpose. This can easily be done: create images that consistently show a miniature person (e.g., with ChatGPT), and then tag 'miniature person' each time. If you do not use a LoRA for a specific miniature person, this LoRA will use its default style and it can look a bit plastic at times.Personal musingsIt was less annoying to train than the <a rel="ugc" href="https://civarchive.com/models/2881795/cockvore">cockvore LoRA</a>, since Grok used to happily comply with just about any request and provided most of the data without having to ask twice.

Files with SHA256: 71e9a295ee09785347fff5b42c880bf98e6634b57a1deb26a9482d8e91de15b7