PsiOnline.org

by Cullen

Hi again everyone! I doubt that any of you have ever heard of thread constructing, since I am pretty sure that I just made up the name. Others might have done this before, but I have been experimenting with it and found it to be pretty awesome.

Prerequisites:
1. Be able to control decent amounts of energy.
2. Be able to hold several constructs in place with your mind.
3. Be able to leave constructs alone for more then three days and have them NOT fade away.
4. You really do need a good amount of experience with constructing, this is not a beginner skill.

The way this programming method works is by using highly portable and condensed constructs that I like to call Threads. Basically you need to do two things to make a Thread construct.

1. Focus a decent amount of energy into a point in space without actually programming it, just guiding it with your mind.

2. Create a very small bit of programmed energy that will act as a thread.

That is it for what you need, the implementation is where it gets cool. This method starts with a basic psiball, but you do not need a large amount of energy. Focus a decent amount (probably about half of what you would need for a ‘strong’ psiball) into an area about the size of a dime. Program it now with a couple of general commands, and the specific command you want it to have: For example:

1. Hold together
2. Form energy around threads into ball shape
3. Split into threads
4. Hold compact thread shape.

Three and four tend to work together, and can be programmed simultaneous. The thread then takes control of the energy and uses it in the same way that it was programmed. Essentially making a homogeneously programmed psiball or whatever, but you only program a small portion of it. That is kind of cool, but the REALLY cool stuff is what happens next. Now you have a psiball that doesn’t need to be shelled because it is controlled by the internal threads. Well, you can fit a lot more than one thread web inside the psiball. For practice purposes, lets put in another thread set. Program another small clump of energy to send out an energy ‘ping’ every second or two. Weave this in so it meshes evenly with the threads that hold the psiball in place. Next you could ad a third weave that is set to draw energy back into the ball from you, or a nearby source. All of the tiny constructs utilize the same energy reserve at the same time. It creates almost a fabric of programming. As long as you don’t to any seriously constructing programs, you can fit many different programs into the same psiball. Also, you can “un-weave” it by pulling the threads out again, and you don’t have to de-program the original psi, because it was only being harnessed and formed by the thread constructs. (Very useful for energy recycling.)

There are other affects that I have noticed with this method of constructing. When you scan a construct that has been made you cannot tell that there are threads within it. The construct, from the outside looks like a normal construct, but if you can get inside it you can differentiate all of the different threads. The trick is the thread programming itself. You need to have a solid concept in your mind of what each thread will do once it has been entered into the energy ball. If you want the energy to be held in a shell, you need to weave in a thread that forms a shell on the outside. If you want a specific shape, another thread that governs shape must be added. The tighter together you place the threads, the more can be woven into the construct, limiting this method only to how many constructs you can create.

Just an afterthought in case you are confused about the production of the thread.
1. Create the condensed energy.
2. Program it.
3. While still condensed, have it ‘spool’ itself into an even tighter wound thread.
4. Reinforce the programming that keeps the thread shape.
5. Don’t over power it. I have had cases where flowing too much energy into the construct will ‘burn out’ the thread, causing it to loose it’s program.

Just one more thing to go over, and that is weaving the threads into the construct. I have found that different patterns work well for different objectives. Like, if I want the thread to control shape, I will have a central point, and have the thread spread out into spokes around the entire construct, connecting to the outermost part of the energy, thus giving it control. Any threads governing power regulation, or shelling, I will weave into a mesh that is on the outside of the overall construct. Then if I want to add a flare, or a construct that makes sure the other’s don’t loose their programming, I will spider web it amongst all the constructs from the inside out, connecting it to all the other threads and ‘tying’ it around them at several points.

Some difficulties I have had:
1. If the threads are not programmed very specifically they can ‘unravel’ in a sense and the construct falls apart.
2. If there is programming in the raw energy that you are placing the threads into, it has a tendency to conflict with the thread programming. (Don’t accidentally program a shape or something of the like into the raw energy.
3. While it is fairly easy to ‘unweave’ threads from the construct, actually de-programming the threads and destroying them I have found to be difficult, if made properly they are very resilient and resist changes in programming. While this is good for keeping your constructs intact, it makes clean up a bit harder then usual. I recommend surrounding the threads with energy programmed to ‘pull apart’ or ‘eradicate’ the thread. Then you just have to de-program the normally programmed psi-ball as opposed to trying to destroy a hair-thin dense energy thread.

That is my technique of Thread constructing. I hope you where able to follow along, if not, feel free to PM me on the boards or chat for clarification.

Have fun and experiment with this tech...