>>6025
I don't have many "guro specific tips". But I can share what worked for me in general.

I would separate them out each into their own lora, you can try to put them all into their own lora but for beginners like you and me it'll save a lot of headaches if you just make each of them their own. A lot of triggers can conflict with each other or be affected by pre-existing keywords in the base model. Having multiple concepts in your Lora can make it really difficult to figure out which concept is causing issues.

If you have enough sample data creating your own unique keyword can save you a lot of time. I'm currently working on an improved impaled Lora with another guro-chan user and the one thing we found is that using pre-exisiting triggers can be difficult with guro. Since guro is typically not a part of popular base models we constantly ran into issues with base version of the prompt messing up our gens. At the same time not having enough training data can make it hard to train a new trigger from scratch.