Cypher 11 Steps

Posted By: Heimdall on Sat Aug 15, 2009 12:16 PM
It depends on a lot of things.:

1. If you are a SpeedFreek (high SPD in skills) then perform actions take less time.

2. if you have a fast system (top right in HW screen) then software takes less time.

3. Software version, the higher the more stable, the less cycles used.

4. INT of the person in relation with SPD and PAR. INT will help you out when you are traced, where SPD will only help you up until you are traced.

5. Total node delay. For example, 3 1delay nodes are better than 1 3delay node. You want to run with the least nodes at the least delay but still win most of the time.

6. Traceability inherent to the mission.

7. Your own traceability due to your current FW rating and your PAR skill.

8. The amount of MEM being used; anything over 50% will increase instability

9. IF YOU HAVE BEEN STONED. This reduces system speed 50%, which increases cycles on software actions in a mission by 100%.

10. Maybe a few other things I may have forgotten

11. NEVER EVER overclock the system. The benefit vs risk ratios are just not worth it. You might get a couple extra points in system speed, but overall system instability will be increased. This translates into say a 2 point decrease on a software run of 100 if it doesn't crash, but a 50-100 possibly more point gain if it does crash. OCing may work OK when you have v888 or v999 softs, but not down at the lower software levels.

So, to sum up, if you are a HACKER (high INT low SPD) then run software intense missions. If you are a SPEEDFREEK (VHigh SPD) then run perform action intense missions. The longer the mission is (more actions, doesnt matter whether software or not) the more possibilty of being traced and thusly losing.

If you have low PAR you will have to use more nodes to come close to completing a mission without being traced.

If you have a crappy system, you will take more cycles to complete a mission. This also has an effect on being traced.

Even if you are perfect, you still have to beat the other guy in the mission; complete it without being traced and in less cycles.

You want to find out what the traceablility of a mission is use:

(Trace Value) = ("Cycles Required to Run Trace" - Total "Nodes Delay") / (Number of "Nodes Used")

You want to find out how many nodes you should have used because you failed the mission and already know the trace value.

(Nodes Required) = ("Cycles Run while being Traced" - "Total Node Delay") / Mission "Trace Value"

The higher the traceability factor, basically the harder the mission. NOTE: "Cycles Required to Run Trace" and "Cycles Run while being Traced" are not the same value. Look at your misison log.

You want to find out the relation between SPD and INT on mission speed, not counting the effect trace has on SPD (SPD is reduced to 0 once trace is started, INT is always INT) then use:

Effect of 1 Point of Intelligence on each Action Phase
Int Action Cycles Saved = Intelligence Skill * 7 / 11 * Cycles Required / 100

Effect of 1 Point of Speed on each Action Phase that goes by undetected
Spd Action Cycles Saved = Speed Skill * 9 / 4 * Cycles Required / 100

None of the above info has to do with hacking. All the above has to do with is finishing a mission as quickly as possible and the effects of SPD, INT, PAR, and system speed to complete that task.

There is an entirely different discussion on all the above when it comes to hacking or being hacked. I will leave that for another time.

I hope this clears things up.

I like numbers,

Heimdall