PsiOnline.org

by Cullen

There are two articles that are reqired reading:
Thread Construction by Cullen
The Strength of a Weave by FrozenFlames
You must be able to sustain complex thread-constructs with 5-6 threads woven together to be able to use the techniques listed in this article. It is highly recommended that you be able to program your threads.

All right everyone; let’s get down to it. This article is clearly about thread shielding. Now you might ask, why go through the trouble of learning this? Well the key reasons are:

1. Reliability: The program density and cohesive properties of threads allow for a much stronger and longer lasting shield.
2. Strength: the same aspects apply, allowing the shield to withstand more stress.
3. Variability: Do to the nature of thread, this shield type allows for multiple defenses within the same space, without worrying about data degradation.

Here is the easiest way to create a thread shield when you are just starting out. First you need to create a shell of raw energy, programmed around you in the structure you want. Pump a rather substantial amount of energy into this area/shell-esque shield. Once you have a decent amount stored (of raw energy) program a strong resistance to change in shape, and then a basic mesh grid. Now condense this energy into an ovular (or whatever base shape you want) sturdy mesh grid. This therefore becomes your base thread and provides a place to weave in the rest of the threads.

The next step is to flow in extra raw energy, and make sure it is affected properly into an even shape by the initial mesh. Now then, Focus energy in front of you (probably between your hands) and create a large quantity of thread from it. This should be your primary defense programming (empathy, cloaking, whatever) now split the thread and weave it into the mesh, preferable getting a fairly even distribution. You need to make sure you can run 10-20 threads at once for this, basically by giving the same order and weaving them through, first vertically, then horizontally, or vise-versa. Once you have this thoroughly woven through make sure to set it in place, and test a little more raw energy with it. It should form the correct defense. Next you add whatever else you want the same way. I leave these next several threads to you, based on need, but remember not to put in two threads with conflicting programming (you will just rip the whole shield apart and have to start all over.) Once you have them all in place, you need to set up one last thread, which is programmed to maintain the data of the others. You can do this as either a tightly interwoven thread, or like a ‘laminate’ covering over all of them. If you chose to do it as a laminate, make sure you don’t accidentally direct the programming into the threads themselves, and mess up the whole project. The laminate style also acts as a protector, helping with data degradation, but again, is a little trickier to program.

And there you have it, your very own thread-shield.

Tips:
Be careful on the weaves, if you don’t get a good tight weave the shielding can end up uneven.
Assign mental colors to the thread as you weave it. It helps for later repair and keeping straight which thread is which.

Thank you for reading this article, and my all your efforts be met with eventual success.

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...

by FrozenFlames

Advanced Energy Manipulation and Programming (aka psychoenergetics) requires a deep skill in trancing, sensitivity, and energy manipulation. It is a priceless skill, however, and can easily be applied to many other skills, such as Crowd Control (via Telepathic/Empathic Suggestion). To understand and accomplish this, you first need knowledge of how energy patterns work in conjunction with programming. You can find this information in my Basic Energy Programming article. From here, we expand.

Seeing the Patterns

The first step is to enter a heavy trance. When I say heavy, I mean as deep as you can go without falling asleep completely. Next, you have to expand your "vision" and sense out around you to begin feeling the vibrations of ambient energy. The goal here is to effectively combine your real vision with your psychic sight (the "eyes" that you use when you scan energy). Once this is done, you may begin to "see" patterns of energy flowing off of everyone and everything. All of these pattern waves are different, yet simple. However, when one person walks into a room (or even more effective, walks into the vicinity of another person) his or her pattern begins affecting the other patterns. It creates a complex wave of interaction in which every minor thing affects something else, causing an infinitely complex domino effect.

Theories of how Natural Empathy works can relate to these patterns; one human's EMF (Electromagnetic Field) will affect another's in a very subtle or drastic way. For this example, we will call the original person: PersonA. We will call the person who is being affected: PersonB. If PersonB's subconscious is sensitive enough to pick up on PersonA's distortion, PersonB's subconscious will duplicate it within his mind and body. This will cause the PersonB to actually feel what PersonA is feeling. Thus, Natural Empathy occurs. The size, energy strength, will power, and pattern of the person's EMF all play a role in how it will affect the world around it.

Once you begin to "see" these patterns in your heavy trance state, you're on your way to entering a PIM (Pattern Interpretation Mindstate). The next step is to learn, to some extent, how these patterns work.

Effecting the Patterns

Now that we can sense these patterns, we must begin experimentation with them. Once again, you must enter a heavy trance. Then, expand your sight once more to see these patterns affecting the world around you. Start simple for now; only view the area that is approx. ten feet out from you in all directions. Begin to see the energy pattern waves flowing all around you. See your field and it's unique pattern, and see how its pattern effects all the patterns nearest it, and how those patterns in-turn effect other patterns, and so on. Meditate deeply on this; it can be quite relaxing and, at the same time, very interesting.

Now we need to begin affecting these waves of complexity. Start by creating a simple psiball, then shell it. Once this is done, move it slowly around the ten-foot area. Watch as the pattern within the psiball's shell (the programming) begins affecting the ambient patterns in the room. Watch as, when the psiball touches your field, it effects that portion of your field ever so slightly. Next, bring the psiball back and program the psiball itself to emit a certain pattern wave (of your choosing). This pattern can be drastic or subtle, fast or sluggish. Then, set it loose in the same ten-foot area. Watch as the emitted pattern changes the pattern that flows through the room. Watch as it also changes the smaller patterns surrounding each object. Look the objects that are handled a lot or that you have emotional attachment to. Notice how they emit odd patterns of their own.

As a last step for this exercise, we will use our field as the manipulator. Begin by destroying the psiball and meditating on the patterns of the ten-foot area once more. Then, put about 75% focus directly on your field, and feel it as just another extension of your body (after all, that's what it is). After you have a firm grip on your field along with a strong focus of the energetic area around you, begin forming the intent. The intent to cause a wave of cause-and-effect (the butterfly effect) in a certain point of the room. From here, extend your field and intent outward to this point, and will that spot to do as you forethought. The patterns in the room should begin changing in a subtle way, effecting each other by a butterfly effect caused simply by the extension of your field coupled with your will. If you have begun to understand how these patterns work, then the state you are in is what I call the PIM (Pattern Interpretation Mindstate).

Advanced Programming

Now, we all realize that the programming of a construct is actually just that construct having a certain pattern to it. And this pattern is what causes the energy to behave in certain ways, essentially causing the energy to carry out any programming commands that was given it. Most of the time that we program, we simply state our will to our subconscious mind by means of visualization or command repetition. From there, our subconscious is the one who patternizes the construct. It is a good thing that this is the way things are too, because there is no way on earth any conscious mind could remember the millions of patterns, the millions of different ways each pattern effects the other patterns, and the millions of ways these pattern combinations work together. This is also the reason programming skill increases exponentially (if a steady practice regime is in place), the more you learn, the more you subconscious understands each pattern and the quicker it can interpret the others. Now, however great it is that patternization of energy takes place subconsciously, it can be even greater if done somewhat consciously. This is where all the aforementioned topics of this article come into play; all that skill and experience in consciously effecting patterns (though fantastic in and of itself, giving you the ability to program and manipulate faster as well as the application to Empathy) is needed in Advanced Programming. To begin advanced programming, you must once again reach the PIM. This is obviously done by entering a deep trance and then meditating on the patterns around you, as done before. Once in the Pattern Interpretation Mindstate, create a construct with some sort of program (just make sure that this program is much more complex then a simple "hold together"). Observe the pattern of this construct and meditate on it for a few minutes. Next, destroy the construct and move on to the next step. Begin pooling a mass of energy in front of you, it is easier (for now) to work with a larger amount of energy. Make sure that the energy is dense however; we do not wish to trade size for density. Next, you have to do something that will possibly be very hard, all at once. What we want to do here is manually insert a few simple patterns into the energy at once and have them affect each other. When three patterns affect each other, a more complex pattern is created. When four patterns affect each other, something extremely complex is created, and so on. So what we want to do is insert a few simple patterns into the energy and have the ending result be the construct that we previously programmed and destroyed. This manual method of programming is extremely difficult; perhaps the hardest part is actually understanding what to do. It is hard, at first, to know what patterns to combine. Most likely you'll find yourself sitting there, clueless. However, this manual method has many benefits. The first, most obvious benefit is the speed and simplicity of programming (once you get the method down). You can combat that with, "I can get just as fast with my normal method of programming". But, with this method you can program quite a number of constructs at once, spreading your pattern emission wave over a wide range. That can also be combated, so the question remains: why use this method? Self-Defense is one, very pertinent, answer. When struggling to interpret the programming of an attacking construct, you can simply enter the PIM and see through all the mechanisms that hide the programming and sig. From there, it is quite easy to insert your own patterns into the construct and bypass any resistance to re-programming. When in the PIM, you get down to the very base of programming and can see the mechanisms that make the construct function, allowing you to bypass anything that previously prevented your mental "hack" into the construct. This enables you to more easily destroy the program function that is harming you. When performing manual programming such as this, you become fluent in understanding and manipulating patterns, allowing your programming skills to improve more than previously imagined. This also improves the ability to shield against incoming attacks with more proficiency. There is one last method of Advanced Programming that takes place in the Pattern Interpretation Mindstate. This obviously includes manual manipulation as well, and actually builds upon the previous method (making this one slightly more difficult). The purpose of this method of programming is to make the construct more efficient, and to drastically cut down on any program corruption. This also allows for more efficient dormant programs that only "kick in" once a certain circumstance comes into play. You begin by entering the PIM and pooling a mass of energy in front of you. Next, you take the patterns that you would normally combine, and contain them inside a shell. You then insert these into the energy mass. From here, you would form everything into a more economical shape (shelling the energy mass and making is smaller, arranging the shelled patterns so they aren't simply floating around inside aimlessly, etc.). Also, as a side note, make sure that the shells of the patterns have an anti-pattern within them; this way the pattern within the shell does not affect the shell and cause a horrible mess of corruption. Next, you want to program these shells to release and re-contain these patterns when certain things take place. This makes the construct quite versatile. Basically what happens is the construct goes about its task, then when something happens that causes the shell to release another pattern, the construct is re-programmed and does whatever its new program tells it to do (as a result of whatever activated the pattern's release from the shell). Holding these patterns separately within the construct until needed cuts down on any corruption that might come from all of the patterns being mixed in what would be an over-programmed construct. Once a pattern is released it can change the entire nature of the construct, or only effect it on a small scale, depending. For those who have read my Core Construction Manual, the concept is very much the same. The construct itself operates like a team of smaller applicatio ns, much like a human cell.

Conclusion

Overall, even if you choose not to do these methods of Advanced Programming, through entering the PIM your Energy Manipulation skill will increase. This includes your skills in programming. Not only will entering the PIM allow you a much greater skill in Energy Manipulation, but it also allows for forms of Crowd Control and Manual Empathy. The skills in this Manual Empathy can also, as previously stated, be used to create more efficient shielding. And on the topic of shielding, through this newfound knowledge in patterns, your self-defense should improve as well. Overall, I hope this article has given you a few things:
1.) An overall improved understanding of how programming works
2.) A vast improvement in your Energy Manipulation skills through PIMs
3.) A skill in Crowd Control and Manual Empathy
4.) More effective shielding

by Stony1205

Up until now, many of you probably make most of your constructs with very simple intentions. For the most part, there is no need to make use of anything too horribly complicated. Yet, sometimes there are instances where complicated programming is needed. Let me provide an example for you go chew on, a telepathic message filter. Perhaps it seems a tad easy at first, but let's break it down a tad. You'll want it to:

• Keep its programming
• Regenerate from your energy supply
• Keep out all non-friendly thoughts
• Make sure it lets out all of your sendings
• Allows sendings from friends to come in, but only if they don't contain anything harmful

That's a short list, but I think you get the basic idea. Now, if you don't plan things out it can be easy for your sub-c and the construct to become confused. If your sub-c becomes confused, it can usually sort out what you want it to do on your own. However, your constructs lack that intelligence.

Definition of a Construct Error: An event that occurs when a construct's programming becomes corrupted due to personal confusion in the creation stage, overuse of the construct, age of the construct, or outside influence, like a virus.

The following paragraphs will show you just how corruption works, and what causes it.

Natural Corruption

I've found over my years of practice and communication with other psychics, that people tend to overuse their constructs. They put large stress loads on them, and don't take the time to properly regenerate. When they programmed them last week, they didn't think as to how much they would be used, instead, the said person just "did it". It's similar to, "Hmmmm, I'm going to build a house, I don't know its dimensions, or even if the ground is level, I just want to build a house. Now gimme some bricks."

If this was the conversation your contractor had, I'd suggest leaving your home... now. When you don't plan out your constructs before hand, you end up destroying them after, and sooner than you might think. What many people don't realize is that your construct will work only in the exact way you tell it to. Constructs don't adapt to situations. They work quite similarly to a Windows application. If you don't program it for every little situation, you get a nice lovely error, or sometimes nothing at all. Basically the same thing here. So when you force too many commands into your construct, it becomes twisted, and can't handle all the information coming into it. The programming begins to weaken, and it eventually cracks and morphs because of the pressure. These can range from change in color, to totally change in the main idea.

I have a quick personal story (no, you can't sit in a circle on my floor) to tell you. I'm not proud of it, but It serves a purpose in this article.

As some PsiPog members may know, I like to experiment with various construct oddities. You could say that's my psychic hobby. I recently had an unfortunate mishap with one of my more successful constructs. Now usually, I only have a few projects going on at the same time, so I can keep them all recharged and up to date. However, one specific project required not one construct to get the job done, but about ten or so. I knew that would be too many for me to keep going at one time, so I created another construct to pump them up for me. To keep this from becoming my life's story, I basically made a giant battery for psiballs (giggles from the crowd).

It took me about a week to fully get this giant dry-cell up and running but I finally connected all the "wires". My constructs managed to be stable for about two days when I found some of them began to move around, and lose their responsiveness. After another couple of days, they lost form completely, and fell apart. Weeks of hard work ruined. It wasn't without gains, however. I learned a lot about the way energy works from this. I found out that energy has certain "stress loads" based on its size, density, and programming. If you overload constructs with energy, such as the unregulated amounts coming from my battery, they tend to give out finding space for all that extra and sudden energy. Such weaknesses make complicated programming a tricky art to learn. It may not be necessary for everyone to learn to program as complex as this, but if you want to become specialized in energy manipulation, you are going to need it.

Viral Corruption

Although this is an extremely rare occurrence, there are forms out there that can be dubbed "viruses". Many just follow you around or play psychic jokes, but there are a few that could cause you some grief. Again, these are highly uncommon, but they are out there. In fact, my community (area of about 50ish square miles) had a rather odd outburst of them about a year ago.

So how do these work? Viruses tend to float randomly about, not being directed at any specific target. They are usually copies of the original construct that were released on a mass scale. They attach themselves to other constructs, mostly shields, then they release their destructive programming. Think of them as a bubble with acid on the inside. When the bubble pops, the acid spills all over your shield, melting it away, layer by layer. Of course, the programming is more complicated than that, but that's the general idea. Disclaimer: Please don't go around making these constructs. This is considered in most parts of the world as an attack. Nobody here is going to bail you out if you get in hot water. Point being, don't be an ass.

There are ways to prevent such a devastating thing from happening to you. I'll list a few here.

• Don't program your shields to deflect once hit, use them to repel things instead. This way, the construct won't know it attached to anything, and make a false infection.
• Use "Anti-Virus" programming. This one is harder, but it can be effective on a long-term basis. Keep updating this one with construct signatures and examples, similar to Norton or McAffee.
• Keep some repel shields around. These make viruses just zip away. Simple.
• If you know an area is infected, use dummies to use up the viruses. Haven't tried this one, experiment for yourself.

So there you have it, two kinds of construct corruption. I hoped this helped make some of you realize that constructs aren't as pliable as you may think. Be easy on your programming. If you have to, make construct systems instead of one big one, and don't over do it. The simpler the better.

by FrozenFlames

Intro

In life there are those who will wish to harm us. Some of those people might even be you, albeit some of you might just be the victims. Perhaps you're both, or luckily enough, neither. In life these people will most likely choose to attack us physically, however, there does exist the ability to harm in the psychic realm. If you are reading this article, it is safe to assume that you are a psion that exists in this psychic community of which I speak. Whether you have ever experienced psychic combat or not, you most likely wear shields "just in case" that scenario happens to arise. If you do not wear defensive shields, I recommend you learn now. There is an article here written by Stony that covers rudimentary defensive shielding. If you already know how, I recommend you start now. From here on I shall assume you are one of the smarter ones that have a shield or two up at all times. In this article I hope to provide you with a few implements and some ideas on which to ponder, so that you may be more well equipped if you ever find yourself in a bad situation. And perhaps you will adopt a construct or two that you shall wear at all times, as you do your shield.

The Scenarios

Allow me give you one or two scenarios to work with. Let us say that because of some occurrence, you find yourself unshielded. Perhaps you were attacked, some electrical field weakened your shields, or maybe it is simply that you took them down to replace. Now let us say that at that moment, you are attacked. In the scenario that you were attacked and the assailant breaks your shields, he simply continues attacking. In the scenario of the electrical field or your shields coming down by your own will, perhaps the attacker was simply waiting for the right moment to begin his onslaught. Allow me to give you another scenario. It may peradventure be that your shields were taken down by strong empathic or telepathic pressure, from a crowd for instance. It is indubitable that in these situations is when your skills are truly tested. This is when some pre-made constructs can come in handy. While some of these constructs may be considered overkill for your day-to-day life, others I wear all the time, in addition to good shielding. Now you are probably wondering what the constructs in question are. So I shall describe them, and then I shall apply them to the scenarios I just listed to give you some ideas on how to use them.

The Four Constructs

The four constructs (as listed in the beginning of the article) are: Expanders, Maskers, Siggers, and Stampers.
Expanders: These are perhaps the first constructs you will use in your emergency defense, so it is the first place I will start. Expanders are very useful to say the least. To make one you take a fairly dense psiball and you compact it to about the size of a golf ball, then hollow it out. So you should have a very dense, golf ball sized, hollow shell. Then program it the main program, which is something like: "Rapidly expand to the edge of my field, pushing out all foreign energies. Hold in that position for 10 seconds, and then fade away." Then program it to orbit around you until you activate its main program. So if you haven't figured it out yet, lets run over its use. Basically this handy little guy will orbit around you, on standby mode. Then lets say you get some debris in your field and maybe some enemy constructs. You simply activate the Expander and it will go to the center of your field, and then almost explode outward. It will then rapidly expand to the edge of your field, pushing out all those nasty little constructs and anything else that is foreign. It will hold there for a few seconds, then fade. We'll get more into this later on, of course, but I'm sure you can already see the potential.
Maskers: In most scenarios, simply pushing out the bad energy is not nearly enough. That is when maskers come in. For most of you it probably takes two minutes, at the least, to make a decent shield. For some of you that are a bit slower, it takes much longer. When you are under attack, it can be extremely hard to focus, which makes this shield construction time even slower. In the scenario that empathy or telepathy pressure destroyed your shield, you certainly won't be able to focus, as you will be bombarded with this telepathic and empathic garbage. That is when the masker comes in. It is simply a construct that is programmed to shield you (using your energy to do so) with a sig cloaker shield. For those of you who do not know, a sig cloaker is a shield that hides your sig. Without your sig, it is impossible for any constructs or people to locate you. If you can't be found, you can't be attacked. So simply program this to orbit around you until you active the main program, as you did with the Expander. The main program is obvious, something like, "Construct a sig cloaker shield around me. Use my energy to do so." Obviously, for you strong empaths and telepaths, you will probably also want a variant of the masker as well. These might be called "Blockers". The program would be similar to the Maskers, except the Blocker would shield you with a blocker shield, rather than a masking shield.
Siggers: A sigger is the simplest of the four. However, do not take them lightly, they are extremely useful. These are just basic psiballs that are marked with your sig to look like "you". They are programmed to use your energy to replicate however many times you program it to. When attacked, you simply shoot these out in random directions. These will have your sig, and will look like "you". Thus, this causes dummies for the assailant and his or her constructs to fire at (thinking it is you).
Stampers: These are constructs that are programmed to "stamp" (or imprint) your sig on to anything you tell it to. This is a cool little thing, but what use does it have for defense you ask? I will tell you. Send this Stamper out, aimed at the attacker's shields. It then goes to his shields and puts your sig into it (a lot of shields actually won't block this, as it isn't an attack). Now that shield has its programming, the sig of its creator (whether hidden a little or not), and your sig (which usually looks like its "smeared" all over it). Now all those nasty little constructs that are aimed at you (your sig) will fly to the assailants shield as well! It will be quite confusing when the attacker launches a few mean constructs, and he ends up hitting himself. Then he will most likely realize that his shield now has your sig on it (as it will feel extremely different). So now he will have to either:

• Remove your sig from the shield (which takes a certain level of skill),
• Put special programming in his constructs to ignore anything with his sig in it as well (which takes extra time),
• Take down his shielding completely, and then put it up again (which is obviously the most non recommended plan of action).

So Stampers are a quick way to delay the enemies attacks, whether for only seconds or minutes.

Constructs + Scenario = Emergency Defense Tactics

I'm sure you have already decided some ways to use these constructs, however, I thought I'd add them to the scenario to finish off this article anyway. So in the first scenario, you are unshielded and being attacked. You first take an Expander (which you always carry around inside your shielding, orbiting around you) and you activate it. Then you take the Sigger and the Maskers, and activate them as well. So now all the nasty stuff is being pushed out and held there for a few seconds, then the Siggers are making dummy targets, while the Masker shields you to hide you. You can't attack what you can't see. So by the time the attacker realizes he is just firing away at psiballs, you will have effectively vanished. If the assailant came on hard, it is probably at this point in which you would want to activate a Stamper, and send it out at his shields. In the case that the attacker is able to locate you through your masking shield, further defense actions will have to come into play and you will most likely have to enter real psychic combat (something I do not wish on any of you). In the scenario of empathic and telepathic overload, you use the Expander first as well. Then activate the Blocker (a variation of the Masker, if you remember correctly).

Conclusion

In normal situations I usually only carry around an Expander. I can shield quickly, and it only takes seconds for me to create a Sigger. So I need not carry those. However, if I feel I might be in danger sometime soon, I will usually carry around and Expander, as well as a Stamper. If I am planning on going into a large crowd, perhaps a few concerts, I will usually carry around two Expanders and a Blocker. The reason for this being because I am empathic and telepathic, so if my shields get broken I'll need something to force the junk out and then help shield me. So basically what I'm saying is that I don't expect you to always carry around all four constructs, but I am saying that depending on your level of skill and the possible scenarios, you should think about carrying around some. If you're highly empathic and going into a crowd, carry around a few Expanders and a Blocker. If you pissed somebody off or just simply got threatened (and you feel like you might be in danger), then maybe you should carry all four. However, if you can make constructs fast, don't bother with the Siggers and just carry three. What I'm saying is that you don't have to be paranoid and carry around two of each when you go through your daily life, thats overkill. But what I am saying is that you should think ahead and use some common sense. Consider carrying an Expander around at all times, and if an out-of-the-ordinary scenario comes up, consider some extra precautions. Make no mistake, an assailant will beset you, he or she will not go about it in a circuitous manner. A psion's defense should be well thought out, not desultory. I hope that none of you ever experience psychic combat, but if you do, be prepared.