# Programming Primer

Written By:
Suntzu, Miri, Lesenthe
+
Vote up!
-
Vote down!

## Introduction

Upon writing this article, I was told that I should write it for the 14-year-old teenager just starting in psionics, who had heard that you "program" psi to do cool stuff. This is true, but first you must learn how program, and then you can do many useful things with psi, limited only by your imagination and training.

## Step 1: Think of What You Want It To Do

A'ight, the first thing you do is think of the specific "cool thing" you want it to do. Hoping that there was a minimal number of "I want to destroy the world" answers out there, let's keep in mind that you want to have it do something reasonable. Good examples of reasonable programming would be: making your construct last a certain amount of time, feel a certain way, be a certain color, or accomplish a goal when it comes into contact with energy (like a shield that blocks incoming psi-balls or emotions).

Remember the vast majority of programming works best if you have in mind what you want to have your construct accomplish before you even start gathering psi.

For example: before peebrain in his article, "Your Psi Ball Source (Peebrain's Method)", starts gathering energy, he chooses what he wants to accomplish which is making a hot psi ball. He then chooses a source for visualization purposes (the sun). After he decided his source and was fully prepared to make a fiery hot psi-ball, he then began to gather energy.

## Step 2: Program It

Ok, there are about three different easy ways you can tell that energy you are gathering to do what you want, they are visually, tactually, and conceptually, but don't let the words scare ya.

### Visual Programming

Visual Programming is done by telling the energy what to do by using a picture. Some of you may remember these pictures. Well, they are there to give you something to visualize while you gather the energy.

To program visually, as you gather the energy, picture a ball in your mind. Pushing the psi outwards, think of the ball, and then as you finish, the psi should be formed into a ball. Easy, huh? Those of you that have already made a psi-ball may want to picture a ball of fire for a hot psi-ball.

### Tactile Programming

Tactile Programming is done by telling the energy how to be by using a feel.

To program tactually, as you gather the energy, focus on how it feels. Visualize how you want it to feel. As you send the psi out of your hands, remember the feeling you are trying to create. For example, in creating a hot psi-ball, remember a time you felt very hot, and focus on that hot feeling as the energy accumulates.

### Conceptual Programming

Conceptual Programming is done by telling the energy what to do without a picture, or feeling or words.

I know that initial statement may have scared some people off a bit, but it is easier than it sounds. In one of the first psychic books I read, there was a visualization exercise. First, see what you are trying to create. If you cannot do that, get the feel of it. If you cannot do that, just know that it is there. This can help with some of the trickier programmed constructs.

To program conceptually, when you are forming your construct of energy, get a clear goal of what you want it to do. When you send the psi out, think of things associated with what you want to do. For a hot psi-ball, think of things you associate with the word "hot" (ex. desert, fire, stove, ect.), and tell the energy to be like that.

A friend, while writing this told me that he always had a hard time thinking of the color green, and to program his constructs with a green color, he always had to think of a jungle; this is a prime example of conceptual programming. By thinking of the jungle, his sub-conscious picks up on the color green, and programs the construct with the green color.

# Basic Programming

Author:
Miri
+
Vote up!
-
Vote down!

## The Essential Methods

### Visualization

So appropriately the previous section (which you have hopefully read) has three categories of visualization “visual,” “tactile,” and “conceptual.” Suntzu gives nice descriptions and makes it all fit into a nice package, he does a great job of this, and his goal to define different forms of visualization for use in programming. His explanation is also more complicated than anything ought or need be. Visualization is visualization is visualization! To divide it is unnecessary, and beyond that pure and utter silliness, when there is (for practical purposes) no need. Visualize with colors, sounds, feelings, emotions, concepts, whatever you can, everything you can. The key to visualization isn’t how you do it, it’s simply that you match up what the visualization means to you. If white means pureness, or holiness to you it will have such an effect within a construct, if a bee’s buzzing means there’s danger in the air, the construct will reflect that, it’s all individual (however, there are still techniques out there that are relatively universal, they merely use relatively universal symbols).

MIRI SHOULD WRITE SOME BASIC EXERCISES AND PUT THEM HERE

### Intent, or Will

This isn’t an uncommon methodology for extrapsionic energy practices, but is fairly well ignored in most psionics circles. What you want to happen is what will happen when you put your faith in intent. By trying to force your will (concentrating, generally, on the final product, rather than any forms of hows) on energy, and succeeding, you accomplish a construct as much as anyone going by visualization’s tricky nature. This is best when not used alone but WITH visualization.

MIRI SHOULD WRITE LIKE TWO WEEKS OF EXERCISES AND PUT THEM HERE

### Instinctive Programming

The odds are you’ve not heard of this before, it’s not readily acknowledged by most because the ability to instinctively program is difficult to learn and rare to be born with. Instinctive programmers will know and understand everything I’m about to say, but the rest of you will probably take the time to read this more than once, and will probably be left in a fog despite it. Instinctive programming is much like instinctive telepathy, or instinctive empathy, or instinctive psychokinesis. It’s totally natural and logical to those who have it, and it takes what feels like forever to learn it from scratch. The closest as I can describe it is to “talk” to the energy, to be directly assertive, with your conscious mind to facilitate whatever mechanics are involved in programming, rather than being a plea to your subconscious to make things happen. It’s operating in a state of mind that makes you almost one part of the energy, telling it to be something it isn’t, and then (for lack of better words) it becomes what you tell it to be. This may sound a great deal like the last essential method, but it’s really not, intent is fine and dandy, but this is a few hundred notches above just “willing it so.” It’s the “crispest” and “clearest” programming you are liable to encounter and is thereby easy to read and understand when opposed to programming by other methods.

MIRI SHOULD WRITE SOME MORE IN DEPTH EXERCISES AND PUT THEM HERE

## The Applications

Now, keep in mind the above, just the visualization and intent is important to 90% of you, so please, that 90%, keep your mind on just the visualization and intent. This is vague, but at the end I have some more specific ideas.

1) Have an idea (at least) a basic one, of what you need or want to do first, it just makes things easier and allows for better focus on the actual doing.

2) Gather or produce energy as needed; See, hear, feel, think up, smell and/or taste your need and/or want while doing so.

3) See, hear, feel, think up, smell and/or taste your need and/or want with this construct to-be in your field, and perhaps in between your hands, or even in your body, being certain that the construct is the clear target or recipient.

4) Now that the purpose is thoroughly established you might need to do more, like shelling, or making additional constructs or power the construct, or reinforce a shield. I’ll discuss the new possibilities in more detail, individually, now.

4a) Shelling: Put simply this is making a shield around your construct to keep outside forces (like ambient energy and annoying semi-sentinents, and a whole array of sentiments both incarnate and disincarnate). This is done, most basically by surrounding the construct in a highly dense “shell”, thus the name.

4b) Some may have issues with distracting from your original goal, and say to just put all the programming into one construct, another may say to keep all of the constructs you make pretty simple, but make many of them. It’s six of one or a half-dozen of the other, and neither of the sides will admit so openly. Once your original construct  is (or are) shelled feel free to make more and not worry about it, or just let it hang around in your field to keep it safe, then make all the constructs you want… the same way you just made one.

4c) Depending on the purpose of the construct, how much fuel you include, and the time it’ll remain active you may need to provide it with an external power source. The classic power source is a ley-line (ley-lines are “lines” or “streams” of energy that naturally exist as a byproduct of living nervous systems, they are plenty large for most needs for those who will be reading this, but in many situations, despite their dependability can fall short of more advanced needs). To use a ley-line just create a hose (a hollow tube) from one (there are many just lying around, with high occurrence around highways, animal trails, and rivers/streams) to the construct that needs power. There are better and bigger sources, but the odds are few of you will need them, look for them in my more advanced articles for more.

4d) In protective shields, or constructs that may undergo direct stress you may want to reinforce the structure. The easiest way to do this is by forcing “rods” of dense energy programmed with the intent to “stabilize” through the natural structure of the construct. In this way you create solid shock absorbers and keep the stress of shape maintenance off of the construct itself.

## Specific Applications

Here are a couple of more specific uses of the essential methods in a practical sense.

### Psi-Ball

1) Know you need/want a sphere of energy rotating on a 90 degree angle to the floor axis.

2) Charge or gather energy enough to make this thing you need/want, and consider what it will/ought look, sound, smell, taste, and/or feel like (a swirling ball of [insert color here] energy with crackling or electric sounds coming from it, smelling of success and feeling dense and yet dynamic).

3) Use your prior visualization as a defining feature, make it a part of the energy you’ve gathered, SEE it swirling, SEE it the color it should (now is) be, HEAR it crackle, SMELL its power, FEEL its density and motion.

4) Create an encasing around the ball, a thick shell to keep it safe, that is dense and hard, but allows the ball to rotate.

### Bubble Shield

1) Know you need/want some protection, or that you have/want to tune out the empathic/telepathic noise around you.

2) Gather/produce the energy you need, all the while keep in mind the sight of a semi translucent, hollow sphere forming around you.

3) See the hollow translucent, but protective/filtering sphere, feel it at the edges of your consciousness, hear it closing you off from the outside, taste the air around you being free of other presences.

4) If you see is fit, reinforce the shield, add specific functions and anything you may need/want.

Well, I think that just about covers the basic basics, there will be more articles in the future. I hope this helped, and keep in mind, I’m over complicating this just like everyone else, it’s easier done than said. Enjoy constructs, they’ll serve you well.

RECOMMEND A SHORT PRACTICE REGIMEN (THINGS THAT SHOULD BE MASTERED BEFORE READING ADVANCED ARTICLE)

Short Description:
Learn Basic Energetic Programming

# Designing Constructs

Author:
Miri
+
Vote up!
-
Vote down!

## Introduction

It is expected that you have read the previous sections, and have some experience with basic construct creation and programming. If you do not meet the expectations please correct this, it is doubtful that this will be very helpful to your practices otherwise.

This article is aimed at novices with some experience and low-intermediate psions and discusses the importance of, practical concerns regarding, and how to design constructs. It is only assumed that the reader can easily make very basic constructs and that they wish to make more complex ones.

To start this off I will define design as: “the use of long or short range planning to improve aesthetic presence, objective functionality, or other aspects of a construct, or amending these aspects after creation, rather than making a construct with little thought or on a whim.” This definition may sound a little complicated, but it only means that you logically plan out one, or several, aspect(s) of a construct to improve its ability to fulfill its purpose.

## Basic Elements of Design

There are many things to consider in the design of a construct. Not all of them will be important to all projects, and may carry only symbolic significance in some cases, however all are worth considering before undertaking, or while remodeling, a construct. The elements of design are simple individually, but they come together to form complex creations which can serve an infinite number of purposes.

#### Shape

The shape of a construct doesn’t have to relate to its purpose at all. However, for psychological purposes, it is beneficial to make the two correspond. Allow me to illustrate the point. A spherical construct meant to act as a link between two minds will, with proper programming, do its job fairly well. However, a construct shaped like a cable between two heads will, by the mere symbolic value, do a better job, even with very poor quality programming. Similarly, if a shield has visible holes in it, it may still protect you if it is programmed to function equally with or without holes in it. However, a shield with no holes needs far less complex and thorough programming to do an equal job of protecting you because of the symbolic protection your mind assigns a solid barrier as opposed to a Swiss-cheese-like shield.

Additionally take into consideration how the shape of a construct will impact the impressions others have of your construct. A gun shaped construct or sword shaped construct will be assumed a weapon… even if they are intended for healing. This is doubly true when those viewing your constructs are inexperienced and do not look at intent in constructs, rather than appearances. You can use this to your distinct advantage in many arenas. For example, if you want a very dangerous construct to not be seen as a threat, make it shaped like a bunny, or other cuddly animal.

#### Color

Color, in my experience, is sometimes entirely symbolic. So, if someone programs a construct to be purple, and they strongly associate the color purple with flowers, a scanner will sometimes get the impression of the construct as the color they most closely associate with flowers, rather than the intended color. Why this is can only be speculated upon, but it is my assumption that the programmer uses the ideas they closely associate with colors to program them into a construct, rather than the color itself. Keeping this in mind colors are most important in terms of what you associate them with. If ‘white’ is closely associated with purity to you, and you program a construct to be white, subsequent viewers will either see white, or the color they most closely associate with purity.

Basically, actual colors are more important as a component of an entire appearance than as an individual factor. You need not be overly concerned with what colors things are, but rather what feelings you associate with what colors they are. The exception is when colors are a part of a complete disguise. For instance, if you wish to disguise your construct as a rubber ducky… Most rubber duckies are not blue with orange polka dots, but yellow with orange parts. Therefore you want the construct to be yellow, regardless of your emotional and mental associations with yellow. In fact, you want to try to be completely non-reactive to the given color, or think about what yellow is (a certain energy-level of photon, which vibrates at such a frequency that your occipital lobe interprets them as yellow) and not how the color looks to you.

#### Size

The size of a construct is relatively irrelevant in every regard. A giant psi-ball is really no different from a tiny one. It is the “quantity of energy” not the volume it occupies which matters. Size affects functionality in terms of psychological perceptions. Ideas like “that construct is huge, it can’t pass through that door/opening.” Act as psychologically provided limiters that are not inherent in the construct itself. Likewise, ideas such as “That tiny construct can’t possibly affect that large one.” Act as imposed limitations, which are not inherent to the construct itself. If your subconscious cannot accept that an event is possible, you will not see it happen. There are numerous examples of this. For instance: when Columbus sailed to the Americas many Natives could not see the ships because they could not conceive of the possibility, their minds assumed it impossible that huge ships from across the ocean were coming, and so they literally could not perceive it. Similarly, even if your construct is utterly destroyed by a construct a fiftieth its size you may not realize it for some time, if you cannot believe it is possible. This doesn’t so much restrict the occurrence from occurring; it merely limits your own ability to perceive the event.

With this in mind, size matters when trying to control the perceptions of onlookers. Instincts say that small things are more sneaky but less powerful, whereas large things are less coy and more brutish. By reversing this natural trend to hide the purpose of your construct, or using it to help play up the strengths of your constructs in the minds of onlookers, you can make your construct more effective in its interactions with others.

### Applying This

Novices will find appearances useful in putting the instincts and practical logic of viewers at odds to confuse them. Conversely a novice can make the appearance and actual focus/purpose of an article match up perfectly to reinforce the programming in the perceptions of others.

Advanced programmers may even give a construct many different potential shapes, changing shape, or appearance of shape, based on who is viewing the construct. This requires setting up mechanisms which change the construct’s shape, or how the shape is perceived. The simplest way to do this is to set up a basic sensory capability in the construct and give it a set of “If, Then” scenarios, such as “If someone hostile views you, then change your appearance to that of a rubber ducky.” Or “If anyone but myself views you, then appear to be ambient energy.”

Appearances, in the metaphysical world, are either very important or very unimportant. They give first impressions, and lead people to conclusions. Design your constructs to either guide folks in the right direction, or astray. That is completely up to you as the designer.

#### Using Parts

Dividing complicated (and even simple) constructs into many parts can improve their functionality. The idea is to create ever simpler constructs that work together to accomplish ever more complicated tasks. Most people think that having many components to a single construct is overtly detrimental to the construct’s stability. I find this untrue, as very simple constructs are infinitely more stable than more complex ones. Let’s use an example. You want to make a construct that makes psi-balls until the end of time because this amuses you. So you create two. The first is one big blob of energy programmed to gather energy and create psi-balls. The second is several constructs combined. The first gathers energy exclusively, it just pulls in ambient energy, then provides it to the second construct. The second compresses the energy into a ball shape; a third then adds programming to this compressed ball to hold together and swirl slowly, forever.

The first takes less thought, planning, and time. The second is much more effective and acts almost like a conveyor belt system. This is what I term a construct system. The combination of several of these simple systems is what I term a system series.

Construct systems and system series are more efficient and less likely to break down of their own accord than simple one-size-fits-all constructs. They do take more time and effort, but if you practice making them long enough, and apply them to varied enough purposes, they become second nature. Once they are second nature all your constructions will by systems of smaller constructs, which eventually will all be systems of smaller constructs, each of which is actually a series of yet smaller constructs. Having grown exponentially simpler your constructs cease to be possible to tamper with because there’s no programming to change.

Another thing to be considered with this approach is that it becomes increasingly more difficult to consciously conceptualize how your constructs work and much of your actual designing becomes unconscious. This is a disadvantage in that step-by-step instructions become increasingly vague and difficult to give, making specific advanced ideas using this method difficult to put into words. This is however a great thing for your personal practice, as it makes your work infinitely more effective, and eventually faster, because your subconscious mind conjures up every level of design from memory.

It is always useful to divide constructs into simpler components which work together. That is the bottom line.

#### Using Symbolism

As with previously discussed aesthetics the practical functionality of your construct can be dramatically affected by the use of things symbolic to both you and others. Specific examples are the use of “hollow tubes” or “wires” to transfer energy, the use of a “mirror” to reflect energy, and the use of “fiery” energy to destroy. Things which posses a symbolic value to you are valuable both in programming and in setting the traits of your construct. Making the outside of your construct a dark “color” can make it grow warmer than making it a light color if the colors carry that significance to you. It is infinitely useful to understand your subconscious mind for a variety of reasons, add this to the list of them.

## Using Several Programming Methods

It is usually best to use as many programming methods as you can in a construct. Redundancy is stability. Using several forms of visualization is better than one. This should be obvious. What may not be obvious is what methods of programming lend themselves best which purposes and functions.

When a construct is meant only for your personal use, and won’t be interacting with other people much, it is very effective to use completely symbolic programming. This is particularly true because the symbols will only need to be relevant to you, in particular. If a hunk of meat is happiness to you, then by all means, if the construct is for you alone, make it look like a piece of meat to cheer you up. If the symbols are effective for you this form of programming will be the most potent in regards to yourself. It does require an understanding of your subconscious associations, however.

When a construct will be interacting with many individuals, especially when it will function transpersonally, it is best to use intent/will based programming. This is because visualization and symbolism are particular to individuals but direct will is not. A statement such as “Be round” will not likely be perceived as “Be flat” by another person. Likewise when your intention is to cause annoyance, without any allusion to the details of how this is done, is unlikely to cause someone pleasure. It is this very unambiguous nature which lends will and intent based programming to being the most effective method for interpersonal constructs’ creation.

Constructs with very complicated goals and purposes are well-served by the use of conceptual visualization, which avoids too much assumption on the part of the programmer. This is useful because as much as you may think you understand how your construct ought to act, leaving blanks will probably work as well, or better, as there are then no direct restrictions on how goals are accomplished.

It is worth restating at this point that using methods in addition to that most suited to the task at hand can only help your construct’s effectiveness, so long as your programming does not become ambiguous.

## Until Next Time

For now this is all. Try to incorporate these concepts when designing your constructs, and eventually you’ll find that trying is no longer required. I wish you luck in your endeavors.

Short Description:
Read and Practice Previous Sections First

# Passive Intent in Design of Energetic Objects

Author:
Lesenthe
+
Vote up!
-
Vote down!

## Introduction

As I'm very fond of saying, energy is nothing if not malleable. Were that not the case we'd have a pretty difficult time getting anything to happen. It will, within reason, do what we tell it to do. This is a simplistic view, of course, but the concept I'd like to convey is a simple one also. While energy will do as we tell it to do, it will also do a lot of things we don't tell it to do. This is not to say that it will disobey us, but it will obey commands we have not consciously programmed. Let me cite an example.
I've always done my best work on the fly. In fact, for a time I was unable to make a decent shield if I had time to think about it. By shield in this context I mean a barrier to psionic input. If a friend in need requested a shield due to excessive input, especially if it was a situation where the person was in distress, I could knock one up with no trouble whatsoever. The intent behind the shield was for it to be... a shield. Without specifying such details, the shield would Block empathic and telepathic input, as well as outside intrusion. The need was there, and thus the required programming was inserted.

## Passive Intent

I tend to call this method of programming "expectation", though "passive programming" or "passive intent" would perhaps be a better choice of words. In this sense, passive refers only to the unconscious nature of the programming. You are still actively programming your object, simply without consciously intending to.
We as human beings do this in the mundane world as well. Can you think of any occasions where you've made a mistake by "over-thinking" something? The purpose of this article is to look at how passive intent can improve energetic workings. Consider the dancer or martial artist who, through constant repetition of a given move, is able to pull it off flawlessly and without thought. Once this is achieved they can then use the move as part of a complex sequence without having to focus on the mechanics of how each part is done. This level of unconscious competence is the first step in using passive intent as an active tool.
To use my above example once more, the reason I had difficulties in creating an effective shield was that I lacked the level of unconscious competence required to free my mind from thinking about every single separate operation required to create such an object. When forced to do so quickly and without thought I was able to act freely. Without the additional element of urgency I was stuck. Unless you half-arse it or are forced into a situation where no other option is available and your mind simply takes over, it is difficult to program passively unless you can already do so, do it well, and do it with little effort and no forethought. You need to "just do it". The infamous just do it method is nothing more or less than unconscious competence.

## Rules

Passive intent is actively utilised by creating a set of rules which define what an energetic object is in the mind of the mage. Let's start with the basics here... an energetic object, be it a Construct, a piece of tech or a spell, is an object which is composed of energy. It is crafted by the mage to perform a function. These are attributes which are common to all items. The reason I commonly call passive intent "expectation" is because I expect my items to conform to specific rules when I create them. Everything I create will conform to these rules. Here are a few examples:

* Objects will be as durable and "tough" as is reasonably possible
* Objects will auto-heal when damaged
* Objects will always be switched "off" when created, and require activation before they will operate

As stated above, one does not focus upon these things when casting. Simply cast, and it will happen. It's a good idea to restrict yourself to things which will be good for all items. As I'm not in the habit of creating short-term devices, I like to make sure that they'll be as hard-wearing as possible. Ditto for having them heal themselves. The final rule listed is more a matter of convenience. As with all things in magic, implementing the above is a matter of will. Choose to do so, and it will happen. Do it enough times, and it will become automatic.

## Conclusion

Expectation isn't really what I'd term an advanced skill. As a matter of fact, I brought it up under the list of "useful tricks" for my student recently. It is not overly difficult, but like all skills it's worth putting in the effort. Particularly in this case, as your results will only be as good as the amount of work you put into them. It's my considered belief that we all learn to do this at one time or another. After all, how many of us really go to the trouble of shelling a construct after working with them for a few months? It's automatic before too long. By taking Control of this and turning it into a useful skill we not only gain another tool but we gain a better understanding of how we work.
-Lesenthe

Short Description:
Interesting Energetic Programming Methods

Author:
Miri
+
Vote up!
-
Vote down!

## Tools

Here’s a list along with descriptions, they are organized by category, there is no particular order other than that.

## External Power Sources

There are those who claim that by going outside of the realm of strict “psi” energy one leaves the realms of psionics. I feel, however, that psionics is more a school of thought, a way of approaching problems and a general methodology more than a set of teachings on a specific energy type. There are also people who claim that taking in energy other than “psi” is going to cause you some sort of harm... this is, of course... a pile of steaming shit, to put it kindly. Energy types may vary, and their properties, but the great majority of energy types you may encounter will not harm you unless made to do so. With that in mind, There are a number of potent power sources that will aid those who are both willing and able to use them. Remember though, even a huge amount of energy can’t make an inexperienced programmer in any way more skilled, it’s only a tool.

Ley-lines- A byproduct of life, these common streams, or lines of energy are the basic power source of more energy workers than one can count. By their nature ley-lines are infinitely renewable and are easy to use. They flow, so by merely attaching a hose to the line one gets a good yield and spends little effort on tapping a potentially unlimited power source. (A note: Overkill is not your friend, don’t try pulling apart a ley-line and directing one end into a construct; just use a hose (or as some call it, a tether) from the ley-line to the need, if you want to get fancy about it, regulate the portion of the ley-line diverted into your link/tether/whatever-it-please-you-to-call-it.)

Star-lines- These are a bit less common to hear about and are an artificial source of power. On the astral level stars, like the sun, are represented by massive energy producing reactors that one can tap just like a ley-line, just attach a tether/hose and reap the benefits. You might be saying that stars are VERY far away, and that’s where a major difference between the physical and nonphysical realms comes into play. In physical realms space is only theoretically possible to manipulate, in the nonphysical space is very easy to manipulate. On that principle the light-years shrink to any convenient distance, making it possible for those with small reserves to tap the huge source, and reap the benefits.  Do make note, this is an astral source, not an “earthly” source, so it’s not very useful for things like PK, whereas it is quite useful for things like shields, telepathy, combat, etc. (Note: What goes for ley-lines applies here, overkill = bad.)

Elemental energies- Another common energy source these energies are already fit with properties, for instance, fire energy “burns”, water energy ”cleans”, and wood energy makes a good tree construct.

Uses- Every thing and force has a particular energy associated with it. Some are as simple as a psi-signature, or as complex as an entire energy with a set of preprogrammed (not literally programmed, but innate to the energy) traits and uses. These energies are useful to reinforce your programming with a sort of irrevocable set of traits, things that you program in can often be ‘removed or altered by a better programmer. However the innate properties of elemental energies are much harder to remove or alter, so by combining the two you can have at least some secure, long term programming for important workers, without spending forever.
gathering- To gather an element first envision the thing. The feelings it invokes and its traits in particular. Find the final feeling you can create after having reflected on it and after combining all of the feelings and senses it invokes is going to be the essential “calling card” of the energy. Bring this feeling into mind and pull this feeling from your environment, feel it gathering, see it come from the environment and in particular the thing which the element represents. feel it massing wherever you need it, then admire your accomplishment, you’ve gathered an elemental energy.

## Properties of the 6 Basic Elements

These are just the six elements most commonly used, and here are just the traits that come to mind, and some uses, that is to say, there are more.
Air- Dynamic, clear, easy to move, diffuses quickly, compressible, loads of give. May be used as a space filler, or compressed heavily to make a very “hot” attack.
Fire- Dynamic, hot, painful, light giving, fast spreading, chaotic. Used in the destruction of construct and/or critters, via “burning.”
Water- Purifying, somewhat dynamic, cooling, has some give, stabilizing. An excellent tool in healing constructs to “clean” “wounds,” also, is a good thing to make an artificial stasis with, because it’s so stable (by stasis I mean a sphere of space filled with this energy in which constructs are preserved without having to shell them).
Earth- Static, dense, hard, little give, cool, stabilizing. Makes an excellent “wall” or as a substance with which to reinforce constructs, particularly when compressed.
Wood- static, dense, hard, some give, “natural,” fresh. Makes a good wall or shield, is good to use in semi-sentient to sentient constructs because it gives it a more natural feel which will fool most scanners into seeing it as a natural entity.
Metal- Static, dense, hard, some give, “less natural,” “stuffy.” An excellent material to make a shield from, I’ve also seen it “sharpened” and used in weapons.

## Trances

Trances are used often, by many people, for many things. In this case it’s to figure out and execute programming you can’t figure out on a conscious level.

uses-
I mentioned above the use of trances to understand and use complex programming you don’t understand, but that’s not all there is to it. Trances have been used to channel more energy and use it more efficiently than normally towards the construct. I’ve seen only rudimentarily skilled programmers go into trances and come out with elegant and potent constructs. By going into a trance with a specific goal, like needing to make a construct that outputs more energy than you input, a very complicated task. By Trancing with this goal in mind, you usually come out with a construct that does exactly what you want.

types-
1) Overload- Typically accomplished by listening to “trance” music. Also, by concentrating on a number of things at once, like listening to your favorite song, doing advanced linear algebra while thinking about what your girlfriend/boyfriend might be doing and thinking about  that dream you had last night. Really anything that overloads your conscious mind works. For some people this method of trancing is inconvenient, they don’t “trance out” by doing these things, these people should try meditative trances.
2) Meditative- Achieved by focusing on nothingness. Usually you start by either starring at candle flames or something captivating, and, hopefully, reach the point at which you can just stop thinking. Another way to start is by focusing on your breathing and thinking less and less with every breath. This works for most people, but some get annoyed so quickly that they never reach a trance this way, these people should try overload trances.

## Miscellaneous Tools

These are tools with no governing category within the scope of this article.

### Stasis Fields

Spheres of somewhat dense energy that are formed with “loose” borders. An alternative to using a shell, this is essentially just a large construct that acts as a holding space for other constructs, the only programming is to hold together and keep things stable. Not terribly commonly used in psionics, but used in most “magic(k)s” (there is little difference, really, it’s all energy work).

Not something I use personally, but there are countless that work with radionics. If you want a few introductory radionics devices try Chuckie Cosimano’s site http://www.charlescosimano.com/e-books.html he more or less pioneered radionics and is really quite brilliant in the area of radionics. Uncle Chuckie as he has been called is the person to ask about this though, not me.

### Memory Cards

For time consuming work when you can’t dedicate a long period of time non-stop to the construct, but don’t want to lose your efforts, “memory cards’ are very useful. I first heard them called “memory cards” on the MPW-13 forums (which no longer exist), but have both used and seen them used by other names long before that. Memory cards are one of two things. They are either a literal thing, a construct that you “store data” on, or it’s more of an idea, that is, you store the programming in energy and store the pattern as a memory in your mind. Explaining the “how” of it is more difficult. By taking your construct and pulling out the programming itself and storing it in energy programmed not to use or take in the programming you create a literal memory card. By taking the programming and either telling your sub-c to memorize it (and have a keyword to carry out this stored program), or by just remembering the “feeling” of the programming, you store the project in your own memory, rather than in energy.

While I covered all of the basic ways to program in “Basic programming” there are more advanced ways which make use of those basic methodologies in a different way. That is to say that while the following methods are just extensions of the previously explored methods they are more advanced, and require a solid grasp of the three principle methods (with frequent, if not constant, exception of instinctive).When used with the tools afore listed these methods are quite nearly enough to Do any construct project, program any command, and start to master programming.

### Intelligent Design

This is the best way I can think to sum up the use of “technology” in the form of constructs. It’s the creation and use of system series. These series can be as simple as a construct to intake ambient energy, feeding a construct that compacts that energy to a construct that forms that energy into a sphere. These systems can be so complex that they are not comprehensible on a macroscopic scale. “Intelligent design” as I’ve labeled it is an art all its own, and is only in the realm of programming as the most advanced programmers eventually start to make “technology” as their subconscious understanding of the construct increases. However learning this method of advanced problem solving is an animal of a different species. It requires the use of the subconscious mind as a conscious peer (and pretty much a guide), as the advanced pieces are not consciously interpretable, whereas  in standard psionic programming the maker nearly always has some understanding of their work.

### Memory Use

This is a somewhat rare phenomenon that occurs spontaneously with those with a natural knack for psionics, but not constructs, who have a great deal of experience in programming. It can be learned with little difficulty though. As the name implies this is the use of memories of programming to create programming. Let me explain. You’ve all probably made a million psi-balls, and eventually you don’t have to think about making a psi-ball you can simply instantly create them at the thought of them. This is the most common, rudimentary example of memory use. Now what makes the use of this methodology relatively rare is the extension of this memory-based programming things that you’ve never made. It may well, and ought to, sound oxymoronic to make things you’ve never made from memory, however by mixing and matching individual small bits of programming from things you have made you can create entirely new constructs. As an example, the creation of a link with a filter in-between the two participants. You make the link as you have a hundred times from memory, cutting out the middle. Then you make a psi-ball from memory and program it to block certain things, from memory, as you would a bubble shield, and connect it to the cut off ends of the link, and presto you’ve made a new construct from memory.

### Just Do It

It’s not just for psychokinesis anymore!  Writers far better than I have made very elegant attempts at describing the “just do it” method, and so to limit how much of a fool I make myself out to be I’ll let you find one of those elegant explanations for yourself. When “just programming” one applies thought only to the end result and tries their best to ignore the actual programming and the actual doing while still actually doing the programming. It’s a delicate balance to say the least and thusly it is an advanced method that is far easier for those who can instinctively program.

### How to Instinctively Program Without the Instincts

You remember how I said it is difficult to learn instinctive programming?  Well it’s about a hundred times more difficult to explain than it is to learn, but I will try to make it clearer here. Instinctive programming I earlier described as “talking” to the energy, making it into a construct. While that is accurate it’s lacking in meaning. Much like explaining snow to someone who has only seen and felt conditions over eighty degrees, the explaining of it as “talking” to the energy is not a full or understandable an explanation. The use of thought coherently, non-symbolically and instantly affecting energy exactly as the thought is meant to is a fuller description, skipping all of the non-design-related conscious steps without “Just doing it” because you’re aware of the programming on a conscious level.

The actual how is far less explainable. If you can innately perform any aspect of psionics, be it empathy, telepathy, psychokinesis or any other skill you may have an idea of what I’m trying to say, however if you have no innate ability, that is, that all the psionics you can perform you painstakingly learned, you stand little chance of comprehension and may need to simply ignore me. First, know what your end result will be. Then gather/produce the energy. Then bring your will into reality by making the energy be your end product. That is to say, “just do it” However you’re also consciously designing and enacting the programming, just without visualization or will/intent involved at all. Now if you’re an innate tele/empath you may well understand what I mean by skipping certain aspects and just getting an end result, also those who have used the “just do it” method may understand (or think the two are the same, which they are not).

## Project Ideas

I will here provide a few ideas for those of you who think they are, or border on being, advanced programmers. Once you can make 1-4 using any of the two given basic methodologies (visualization and intent) you can consider yourself graduated from a novice programmer to an intermediate programmer. Once you can make 1-11, using the three initially presented methods (visualization, intent/will, and instinctive) consider yourself advanced. Once you can make them all (1-19) using all of the presented methods (including all of the methodologies presented here) you can consider yourself a “master” of programming. If you’re looking for detailed instructions you’re looking in the wrong place, as these projects are most beneficial if figured out on your own. Suffice to say there are many techniques available for 1-10, however, the key to mastering psionics is understanding it well enough to have no reliance on the techniques of others.
1) The psi-ball (and all the variants, such as the psi-cube).
2) A construct dynamo (self-sustaining).
3) A construct dynamo (self-sustaining and has a product [such as occasionally popping out a psi-ball, or clone]).
4) A construct dynamo (self-sustaining and produces significant amounts of energy [at least enough energy to mimic your natural, unintentional energy production]).
5) A system series to create 1. (see intelligent design for a definition of a system series)
6) A system series to create 2.
7) A system series to create 3.
8) A system series to create 4.
9) A simple Chaos shield.
11) Large scale, stable astral warps (such as making a loop in space on the astral plane such that moving forward ends up behind the starting point [warp your head around that one]).
12) Unmaking shields without attacking/damaging them.
13) Make constructs with ability that you are unable to use without the aid of constructs.
14) “Modifications” to energetic/astral bodies that affect the physical body.
15) “Psi-pets” with fully functioning minds and an I.Q. above average.
16) Energy converters (for instance fire element to psi and vice versa).
17) Psionic amplifying constructs (amplifying abilities, sensory, or influence).
18) “Cages” or “seals” that can both block ability(ies) and movement on the astral plane.
19) Flared Psi-balls (and variants).
For the “Master” of programming.
A) Flared versions of 2-18
B) Constructs that perfectly mimic physical creatures on both a physical and astral level (visible, physically tactilely sensible, breathing, etc. etc. not just something that is shaped like an animal, and maybe moves like one).
C) There is very little chance you’ve done all of the precedents, so please go through them before asking “what’s next?” And if you actually manage to do them all you may feel free to contact me and ask “What’s next?”(You will be heartily, and perhaps skeptically congratulated.)

## Final Notes

There is little more to programming than what is contained here and in its antecedent article, using the information in them, and coupling the information with patience and effort, you can accomplish most programming goals. Luck.

Short Description:
Proficiency with Prior Material is a Must