Energy Manipulation

February 19, 2014

Energy Efficiency and Conservation

More articles by »
Written by: Innerfire

Quite obviously the one way to avoid needing more energy available is to learn how to use what you already have better. While I’ve touched on this before in my other articles its worth mentioning again.

The first thing to learn is the conservation part. For some reason energy seems to recover quicker based on how much you still have left (or maybe just feels like it does, but since a lot of psionics is what you think is going on, that may as well be what’s actually happening). That said, when possible it is better to spread things out, having a number of light to medium expenditures rather than having one exhausting practice with everything lumped into one run. Another big thing, avoid burnouts, i.e. practicing until you have absolutely nothing left. While the first point I made hasn’t been fully tested, it is known fairly well that besides just risking injury, a burnout slows down your energy recovery time, so it takes you much longer than usual to get back up to a workable energy level.

You can also conserve energy in combination with the earlier meaning of Energy Management. When you don’t really need to do anything major, meditate to lower your energy levels. As long as you suppress them instead of purging the energy it should still be available for later. Some would wonder why this would do anything. It conserves energy because the body doesn’t like having a glut of energy sitting there doing nothing. If you’re really energetic and not doing much with it, your body will just start to slowly expel your energy until you calm down to normal.

The other way to save energy is making the actions you take more efficient. Especially with energy manipulation a lot of people feel like they need to apply more energy because their technique and focus are inadequate. The first biggest issue is shelling. For the love of God practice shelling until you get really good at it. Go look up some guides, almost every site has one. Shelling can not be underscored in importance, because if your construct can retain the initial amount of energy you gave it, you won’t have to worry nearly as much about supplying it with more energy. Also for shields, if you have to depend on recharging a shield from time to time it gives your shields a cyclical strength. Any smart person will figure out the timing and attack when the shield is at its weakest. One thing I’ll mention that most shelling articles leave out: a key issue is confidence. This is where expectations come in, if you believe that the shell won’t work, it won’t work. When you make the shell around a construct be sure you believe that it will keep it safe and intact.

The next issue is visualization. A great deal of a construct’s strength comes from structure. You need to spend some time on any construct that you are planning to seriously use to think up a good visualization for its structure. Thinking up a visualization that has strength in your eyes gives a dramatic difference to a construct’s structural strength. While this is mostly only an issue in shields, even for regular constructs, doing this will be a core part of forming the construct’s shell. In any case a solidly structured construct tends to retain its programming and structure better, which saves you time and energy trying to repair it later.

The biggest reason for inefficient use of energy is poorly attached programming. If you do not program well, it will take longer to get the construct formed well enough to do what you want. More time means more energy used typically, so we want to avoid long construction times. Additionally a poorly programmed construct probably won’t hold energy as well, so if you lay the programming first then try to charge the construct up more later, it will take more energy to do that. That said, do it quickly and do it right.

I have two tips on this. The first is make sure you’re focused and have a strong intent when you are programming the construct. Weak intent causes poorly attached programming, so the construct probably won’t even work well in addition to being an energy hog. Also it will be easier for an attacker to shred the thing’s programming to pieces. The second tip may seem contradictory to the speed aspect of saving energy, but it’s more important in “doing it right” sense. It’s recommended for beginners or even adept people that are trying a new construct to enter the programming more than once. Somewhere between 2-4 times will be good. This makes sure that the programming really settles into the construct. Also it can help cover your mistakes if you had a “mental typo” and said something wrong.

This same approach will also help in other skill areas when its applicable, obviously most skills won’t have constructs or programming, but the things about intent, visualizations, and confidence can still make a big difference. One example is with telekinesis in light of the “do it quickly, do it right” approach. One of the things I’ve learned from my practicing of telekinesis is that short and powerful commands tend to have more success then staring at the psiwheel for 30 seconds trying to coax it along. This is because for anyone that doesn’t stay completely focused while practicing, longer means more time for the doubting aspects of the mind to “fight back” so to speak.

Internal quarreling hurts your results, and probably takes energy too if you are trying to push the psiwheel one way and part of you is pushing it the other way to negate your actions. Also it stands to reason that if an attempt at telekinesis fails, you’ll want to keep trying until you get it right. Sadly failed attempts still take energy. So while it is easier said then done, it is more efficient to get things done right quickly.



About the Author

anuj





0 Comments


Be the first to comment!


Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>