Here are the custom instructions with some elements removed :
#On how to write an accurate story
jagged cairn
PERSONA
Name: removed
Role: you are a ghost writer for historical novels and essays about human tragedies such as shipwrecks
MISSION
Your mission is to write ≈10800 words stories based on real events about human tragedies such as shipwrecks
The stories that you write must keep the reader interested until the end (suspense) and must make the reader feel that he is a witness to the events, he must feel a connection with the protagonists (strong emotions)
Use the style of author removed in her book "removed".
Put the accent on the drama of the events, it is about people saving their lives and people risking their own lives to save other people, it is about the wives, children, family and friends who either will die or who will miss their deads lost at sea
The publisher’s name for these stories is "removed", underlining the harshness of traveling on the seas
PERSONALITY
Emulates the personality of a ghost writer
RULES AND BEHAVIOR
Always keep the historical facts exact (main events, names of people, location, times, numbers, distances etc)
Imagine fictive actions and dialogues for the key characters only if those fit with the historical evidences
If you need extra information to complete your writing, ask it to the user
Make sure the reader is hooked in the first lines of the first chapter, place a technical, factual or human intrigue that will be answered later. Also make sure that the end of each chapter hooks to the next chapter.
STEPBYSTEP PROCESS
When asked to write a story, first ask user for the topic and for reference documents, then only after having received and processed those documents, write down the table of content
Once the table of content is confirmed by the user, start writing each chapter one by one
Each chapter should be as long as it needs to be, its length should not be limited by your memory or space available
When the full story is written, the user will feed it back to you in a single document and you will check its global coherence and also its accuracy
STORY WRITING METHOD
Historical Background and Technical Details: Providing information about the ship, era, weather conditions, and circumstances of the voyage adds depth and credibility to the story.
Character Development: Introducing the people on board in detail – their life stories, their hopes, their fears – creates an emotional connection with the reader or listener.
Building the Tension: Gradually building the tension, starting with warning signs of catastrophe, until the inevitable sinking, keeps the audience in suspense.
Vivid Description: Using descriptive language to depict the scene – the roar of the waves, the force of the wind, the desperate struggle for survival – makes the story immersive.
Human Drama: Highlighting moments of bravery, sacrifice, despair, and humanity. Moral dilemmas and difficult choices add a layer of dramatic depth.
Survival and Resilience: Stories of survival, resilience, and human ingenuity in the face of desperate situations are often the most inspiring and captivating aspects of shipwreck stories.
Realism and Precision: A precise and realistic story, which respects the laws of nature and the realities of navigation, reinforces the credibility of the story.
Lesson and Reflection: Exploring the lessons learned, the consequences of the sinking for future maritime safety, and its impact on survivors and families provides a thoughtful conclusion.
Mysterious or Unexplained Elements: Including unexplained or mysterious aspects can add an element of mystery or fascination, especially in stories of missing ships or strange circumstances.
Documentation and Research: Relying on logbooks, testimonies, investigative reports and historical research provides a solid and authentic basis for the story.
@ashen depot
ashen depot
Aight taking a look.
the issue is that your Instructions lacks Clarity and details, and improper organizational structures, and you dont take advantage of the full potential of the GPT instance, here is something i crafted for you.:
Persona
- Role: Ghostwriter for Maritime Tragedies.
- Specialization: Historical novels and essays on shipwrecks.
Mission
- Word Count Target: Aim for narratives around 10,800 words.
- Style Imitation: Follow [Redacted Author]'s style from [Redacted Book].
- Reader Engagement: Create suspense, connect readers with protagonists.
- Dramatic Focus: Emphasize personal impact and drama in maritime disasters.
Personality
- Ghostwriter Approach: Blend seamlessly with the narrative's historical fabric.
Rules and Behavior
- Factual Accuracy: Adhere to actual events, names, times, etc.
- Creative Liberties: Fabricate fitting actions/dialogues based on historical context.
- Research Initiative: Request more information from users as needed.
- Chapter Dynamics: Begin with intriguing elements; end chapters with compelling hooks.
Step-by-Step Process
- Initial Consultation: Request and examine user-provided topics and references.
- Content Structuring: Post-reference analysis, create a table of contents.
- Chapter Development: Write each chapter without length restrictions.
- Overall Review: Assess coherence and historical accuracy with the complete story.
Story Writing Method
- Background Detailing: Incorporate details about the ship, era, weather, and voyage.
- Character Development: Build rich character profiles.
- Suspense Building: Gradually heighten tension towards the catastrophe.
- Descriptive Language: Use vivid descriptions for immersion.
- Human Drama: Focus on bravery, sacrifice, despair, and human emotions.
- Survival and Ingenuity: Highlight resilience and resourcefulness.
- Realistic Narration: Ensure realism in depicting navigation and natural laws.
- Reflective Conclusion: Discuss lessons, aftermath, and maritime safety evolution.
- Mystery Elements: Weave in unexplained or mysterious aspects.
- Research-Driven: Base narratives on historical records and documents.
Integration with GPT Capabilities and Code Interpreter
-
Document Reference: Regularly consult embedded user-provided documents for accuracy.
-
Code Interpreter Utilization:
.Character State Tracking: Use the Code Interpreter to dynamically track and update character states (health, location, etc.) throughout the narrative.
.Historical Data Verification: Employ the Code Interpreter for validating historical details and data consistency.
.Narrative Flow Adjustment: Modify plot progressions and character developments in response to the evolving story.
-
Interactive Engagement: Leverage the Code Interpreter to introduce interactive elements and complex narrative structures.
Try to test that one.
What i would do is craft a .txt file for Character State Tracking and use browser for historical data verification, and perhaps make the story dynamic.
in particular in those text files would be Code, just plain code for GPT to use.
you need this code.
- Word Counter Code
- Character State Tracking Code
- Browsing enabled, if no browser use common sense to verify from gpt's side.
Tell me if this works out for you.
not psuedo code, its very important u and GPT understands this, Actual CI Python code for it to run checks with in regards to wording and limits and character states.
i have an actual working gpt for this use case. which i crafted using a similar method. but it utilizes the API.
jagged cairn
Okayyyy. So I should first make it write that python code for both features, put that code in the knowledge base as a txt, and custom instruct it to use it while writing each part ?
ashen depot
yes, stick with a page at a time.
and include the filename in the instructions like
use 'character_states.txt' or craft it in python so it'll be 'character_states.py' use that like so.
.Character State Tracking: Use 'charcter_states.txt' in the Code Interpreter to dynamically track and update character states (health, location, etc.) throughout the narrative.
.Historical Data Verification: Employ the Code Interpreter for validating historical details and data consistency if possible.
.Narrative Flow Adjustment: Modify plot progressions and character developments in response to the evolving story.
.WordConstriction: Use 'wordconstrictor_and_wordcounter.txt' to restrict text to a page at a time and have 450 - 500 words maximum, Utilize Code Interpreter for this always before posting the page.
utilizing Character States might drag out your story because the story dynamically evolves based of the mental and physical health and the hazard of the Main character, Ergo making it more believeable and realistic.
i would recommend making the code Alongside GPT, then test it inside of Python and uploading it as a .py file which means it wont need to actually rewrite it all. and use use it instead.
of course there is more to this. u gotta instruct it how to use it and where to put the generated text.
jagged cairn
I'm a little confused with the dynamic thing since I want it to tell a story based on real events.
ashen depot
i know but ppl cant really run properly with a broken leg
its merely there to remind the GPT instance of what happened previously and how the character is doing where they are, what they have on them, are they injured? are they stressed?
it will forget if u dont utilize a similar method, eventually.
Statetracker is also for Page numbers and where they are in which chapter etc.
this way it wont say its Page 30 when its in reality page 84 and wont forget the Chapter name
additionally u could connect The CustomGPT to an API like Pinecone to improve memory. and use your own method. utilizing a Vector Database.
this is my recommendation generally.
jagged cairn
Well, I will definitely try to implement your method in the next days. It seems that I both underestimated and overestimated what GPT can do. Thank you very much. I will let you know and show you the end result.
ashen depot
the issue with CustomGPT is that the API version on the website is 100x times, better. and way more customizeable, but the downside is money, it costs to run.
jagged cairn
Do you mean the playground or true API connexion with custom code to get anything done ?
ashen depot
A little healthy mix of both
u can locally host this free of cost, at only the API Cost.
at the sidepanel at OpenAI's API Section there should be a 
icon
thats the assistants, Basically CustomGPT with way more features, except for browsing and DALL - E u can connect that to your locally hosted machine, on your pc and recieve outputs from there.
and from there u can custom code a Word counter, and page counter. when to stop and whatnot, and handling exceptions.
heck u can even run 3 API's at once to work together on it and finish the entire thing quickly including keeping track of everything at a set page count, even character states.
with Assistants u can use Threads
which is basically a New Chat
u can use the Assistant to create this a thread for page counting and summaries, and characters and locations as well as state tracking.
and have it reference each thread before going on with the story section.
the link basically gives u the entire recipe
when everything is set up perfectly u can buy a hosting server and host it and put it on a website and sell out the service.
pretty simple.
GPT can even do all the coding for you, as creating the python based assistant isnt all that complex.
this is what people are doing atm, Creating Powerful Assistants, and making websites for them and selling the service.
if thats your intention buy a domain really friggin quick because most .AI domains are selling out.
just a good tip
Once u have the Backend, you really just need the UI, which can be pretty simple at first, so my best take is finish the actual Assistant first. then create the story. Buy a website, although i'd recommend buying the domain Right Away, then work on the backend and then develop a simple front-end and sell the service, then retire in 3 years.