>>106965511
This is pretty much how I started back in January or February when I tried uploading text files to Grok , before Gemini 2.5. This anon is basically RAGsing it. I've only done that once with Empire of the Petal Throne one night when I met RAGs anon here. I said it's okay, but stuck with my lorebook method. There is very little room for improvement in my case. This is faster, but riskier plus you have no control over what's going on.
I call my method 'adoopting' after 'cooming' or 'vooting'. I upload the .pdf (OCR it and compress or split if I need to because AI studio works with files lighter than ~32mb), then I copy paste a prompt from my list of prompts saying something like 'I am adapting this VtM Revised sourcebook into a SillyTavern lorebook for AI Storyteller to run. You must derive world entries from the .pdf. Sort them out by prefixes: Table:, Rule:, Mechanic:, Ability:, NPC:, PC:,... Write in three code boxes (title, keys, content), make sure to name-drop the title in the content. Write the list in a code box, don't start adapting yet.
Then I copy-paste those code boxes into lorebook entries: vectorized, @D system, depth 0, order 80-150, trigger 100%. Then I bind these systems together with indexing/utilization entries called Meta-Nav (locations), Meta-Relationships: (factions, followers, rivals, friends, lovers, this one encourages the AI to add some drama), Meta-Equipment (encourages use of items, spells, vehicles, pets), Meta-Scenario (makes adventure module's story play out), Meta-Continuum (makes time pass during downtime and traveling).
My way of doing things is very crude and time-consuming, but my output is getting better all the time. I only adapt when I feel stressed or bad. I like imagining my lorebooks as piles of labels (like old library cards the librarians used to place inside pockets at the books' end) bundled with oversized duct tape.