DIY Hypnotism

Hypnotic Scripts

This repository contains legally curated hypnosis scripts for DIY Hypnotism.

These scripts now target DIY Hypnotism v3.

About the App

DIY Hypnotism is a macOS self-hypnosis app that lets you create your own hypnotic sessions using text to speech, your own scripts, background audio, and visualisations.

This repository contains the script files used by the app.

For more information about the app, see:

• Website: https://www.diyhypnotism.com/
• App Store: https://apps.apple.com/gb/app/diy-hypnotism/id1331447267?mt=12

v3 Update

DIY Hypnotism v3 changes the recommended script format.

The main change is that the older [[...]] speech commands are now deprecated.

DIY Hypnotism v3 introduces XML-style tags to control speech behaviour instead.

In practice, that means:

• plain text should be preferred wherever possible
• natural punctuation should be used to guide the spoken rhythm
• blank lines may be used to create stronger pauses between thoughts or sections
• XML-style tags should be used when you need explicit speech control
• variables are still written like %VARIABLE%

Supported v3 Speech Tags

DIY Hypnotism v3 currently has support for basic XML-style speech markup, including:

• <break time="1000" />
• <emphasis>important words</emphasis>
• <emphasis level="strong">important words</emphasis>

Example:

Take a deep breath in.
<break time="1000" />
And let it out slowly.

This word is <emphasis>important</emphasis>.
This word is <emphasis level="strong">very important</emphasis>.

Legacy [[...]] Commands

The old bracketed commands are deprecated in v3, but there is still basic support for some of them.

At the moment, the legacy commands with basic support are:

• [[slnc 1000]]
• [[emph +]]
• [[emph -]]

New or updated scripts should prefer the XML-style tags instead of adding more legacy [[...]] markup.

Compatibility

These script changes are not compatible with DIY Hypnotism v2.

In particular, the v3 XML-style speech tags are part of the new format and should not be treated as v2-compatible.

If you need v2-compatible scripts, you should use the older v2 script set instead of this v3-targeted version of the repository.

Script Authoring Guidelines

There are a few formatting rules for scripts:

• everything after a # symbol on a line is treated as a comment
• variables should be written like %VARIABLE%
• variable names should use uppercase letters, and may also use underscores
• prefer XML-style tags over legacy [[...]] speech commands
• prefer readable text over dense inline control markup
• use blank lines deliberately, because they may affect pacing in v3

Notes for Contributors

When updating older scripts for v3:

• replace legacy [[...]] commands with XML-style tags where explicit speech control is still needed
• remove legacy pacing markup where plain text and spacing now read better
• keep wording natural when converting pauses into punctuation or paragraph breaks
• preserve the intent, cadence, and safety language of the original script
• keep variable placeholders stable unless there is a strong reason to rename them

Licence

Each file should have a header that states its licence.

Source and original licence information, if different, should be recorded in the commit message.

Pull Requests

Please make sure any file you submit is legally allowed to be copied.

It should have a known licence, or be in the public domain.

When possible, note whether the contribution:

• adds a new v3 script
• updates an older script to the v3 XML-tag format
• preserves any intentional variable placeholders

Thank you.