 tap into the subconscious to solve problems, create wealth, heal relationships and remain young in spirit.
3 Keys That Make Trypliminal Affirmations Technology More Efficient Than German Engineering!
For any form of hypnosis or suggestions to work, you must be able to bypass the conscious mind and speak directly to the subconscious operating system.
Imagine being guided into the deepest alpha brainwave level where your subconscious mind is the most receptive to suggestions.
This NLP hypnotic script is the missing link to why most other affirmations audios that miss this key component have little or no results.
Suggestions are engineered for a full immersive stereo soundscape with vocals being played in the right ear, left ear and in both ears at alternate times.
Combining this with the Trypnaural brainwave music you can create a more powerful reprogramming effect and tap into the 4th dimension of the superconscious mind.
In Breathobics you will learn powerful breathwork techniques that I developed after my own self healing experience from a chronic illness and then later from training with the super human Wim Hof based on the ancient science of breathwork called Pranayama.
You will also learn simple breathwork techniques that will dramatically enhance the power of the Trypnaural technology.
Extended Exhalation Breathwork – this technique will help you switch of stress on command, flood your body with vital oxygen and create higher levels of mental clarity and calm.
Whole Brain Breathwork – this technique will harmonise both left and right hemispheres of the brain awakening its potential.
Midbrain Buzz – this technique will stimulate the reptilian center of your brain awakening its serpent power for deeper intuition, insight and cognitive power.
Scaling/reappearing villains

To get right into the context, planning on some homebrew sessions and one of the major antagonists essentially can't die (at least not without a magic mcguffin placeholder until I can make something better. Or some smart enough planning on player's parts to constantly outsmart/avoid him). 

In short, every time this antag killed, his body turns incorporeal, and he spends the next few days regenerating it and can reappear basically wherever he wants, even on certain planes. He always knows the general/vague locations of the PCs, only getting more exact pinpoints on them the closer he gets

His sole goal is to track down and kill/DoWhateverElseInCaseHeAccidentlyWipes the PCs, I wont bother explaining everything for dumb plot reasons. But overall they are Increasingly getting smarter and stronger in their methods for hunting the party, they don't rest or tire, and they work alone.


So, in addition to new combat tactics in attempts to specifically screw the pcs, I was wondering if I should also give them newer and better equipment. Like a magic item that can hide their location, or temporarily turn themselves incorporeal, or whatever other types of some magic weapons/armor/items

That way at late levels they won't get wiped instantly and in fact might even be too hard for the pc's to directly confront; or at the very least, not make them too medicore or boring at the end


But at the same time, I am worried that I would make the fights in general grind to a halt just to make pcs drudge through "yet another encounter with the same immortal they can't kill", or at least can't outrun for too long. 


Anyways, what is your opinions or advice on scaling/reappearing antagonists?





P.S.  His literal purpose is to slow down the pc's via some bbeg's autistic tier plan. But, as said previously, I am worried making him too tough will make him too much of a bore/timewaste to bother fighting him. But I also don't want to overscale him too early# JIT SCSS Compiler #

"Just in time" SASS compiler for Symphony CMS. Supports SCSS syntax only.

- Version: 1.1
- Date: 18th March 2015
- Requirements: Symphony 2.3 or later
- Author: deepilla, <EMAIL>
- GitHub Repository: https://github.com/deepilla/scss_compiler

## Synopsis

A fork of <NAME>'s [SASS Compiler](http://symphonyextensions.com/extensions/sass_compiler/) extension with the following changes:

- The [phpsass](https://github.com/richthegeek/phpsass) compiler library has been replaced with [scssphp](https://github.com/leafo/scssphp/)
- If compilation fails, the error message is output to the CSS file so you can see what went wrong

## Why fork the SASS Compiler extension?

The [SASS Compiler](http://symphonyextensions.com/extensions/sass_compiler/) discards compilation errors which makes diagnosing problems a pain. Initially I just wanted to expose the error messages and maybe upgrade to the latest version of [phpsass](https://github.com/richthegeek/phpsass). But after some investigation I decided to switch to the [scssphp](https://github.com/leafo/scssphp/) library because:

- it implements a slightly newer version of SASS (3.2.12 vs "approx 3.2")
- it appears to be more actively maintained
- it has a [server mode](http://leafo.net/scssphp/docs/#scss_server) which caches the compiled CSS rather than recompiling on every request. Implementing this would make the extension suitable for production environments

On the downside, [scssphp](https://github.com/leafo/scssphp/) doesn't support [the old SASS syntax](http://sass-lang.com/documentation/file.INDENTED_SYNTAX.html). But you weren't really using that, were you?

## Installation

See [*Install an Extension*](http://www.getsymphony.com/learn/tasks/view/install-an-extension/) in the Symphony docs.

1. Uninstall the [SASS Compiler](http://symphonyextensions.com/extensions/sass_compiler/) extension if it's installed
2. Install the SCSS Compiler extension per [the docs](http://www.getsymphony.com/learn/tasks/view/install-an-extension/)
3. Install the [scssphp](https://github.com/leafo/scssphp/) library into `lib/scssphp` either by manual copy or `git submodule update`

**Note**: Installing the SASS Compiler and the SCSS Compiler at the same time may result in unexpected behaviour due to conflicting `.htaccess` rules. Use one or the other but not both.

## Usage

### Basics

This extension is a drop-in replacement for the [SASS Compiler](http://symphonyextensions.com/extensions/sass_compiler/). Include your SCSS stylesheet, say `workspace/assets/sass/style.scss`, using:

	<link rel="stylesheet" href="/scss/assets/sass/style.scss" />

Your SCSS is compiled on the fly when the page is loaded. A copy of the compiled CSS is saved in `/path/to/project/manifest/cache/scss_compiler`. Note that this file is never used - the SCSS is recompiled on every page load whether it has changed or not.

Files imported with `@import` are assumed to be in the same directory as the parent file.

If an error occurs during compilation the CSS file will contain the error message as a comment.

### Warning: Do Not Use In Production

Because your SCSS is compiled on every page load, you should **only use this extension for development**. Use the compiled CSS on the live site. You can use a template to switch between the two, e.g.

```XSLT
<!-- Are we in Production? -->
<xsl:variable name="production" select="{test for production environment goes here}" />

<!-- Compile SASS in Development, use compiled CSS in Production -->
<xsl:template name="compile-sass">
    <xsl:param name="filename" />
    <xsl:choose>
        <xsl:when test="$production">
            <link rel="stylesheet" href="/workspace/assets/css/{$filename}.css" />
        </xsl:when>
        <xsl:otherwise>
            <link rel="stylesheet" href="/scss/assets/sass/{$filename}.scss" />
        </xsl:otherwise>
    </xsl:choose>
</xsl:template>
```

You are responsible for placing the compiled CSS files in the correct location (`/workspace/assets/css` in this example).

Implementing the [server mode](http://leafo.net/scssphp/docs/#scss_server) of [scssphp](https://github.com/leafo/scssphp/) would make the extension usable in Production. It compiles the SCSS once, caches the resulting CSS, and serves the cached files on subsequent page loads, only recompiling if the SCSS changes. It's on the todo list...

## TODO

1. Look into [scssphp