Miss NEXUS
A loyal servant and elite slave of Mr NOXx, she was found within a badly damaged Amarr Sigil shortly after Mr NOXx and his mentor; EiD escaped the mighty Amarr Navy.
The Sigil had succumbed to an attack from Minmatar rebels and the ship was disabled and routed for its precious metals and armour. Miss NEXUS hid from the invaders as she firmly believed the mantra for which the Amarr Empire operated. She had been the slave of a wealthy trader on Tash-Murkon Prime and had received exceptional treatment and liberties.
Miss NEXUS is a well accomplished pilot, her implants granted to her to achieve immortality as Mr NOXx couldn’t face her untimely demise. Her friendship with Mr NOXx has blossomed over time and they support and care for one another very deeply. Outwardly Mr NOXx will scold Miss NEXUS at every opportunity, but this hides his true feelings for which they share together in privacy.
One girl, in a trillion souls; she is Mr NOXx’s conscience and his restraint.
Posted by Redundant blogger 0 comments
Labels: POD Pilots
Singularity

The test server Singularity is open to all players and will login even if your account has been suspended on tranquility, so long as your account was active at the time of the mirror of Tranquility.
Singularities purpose is to try out new features, and as a result it will generally be a few patches ahead of the Tranquility server.
Character information is replicated to the Singularity servers on a regular basis, but keep in mind that if your account got created after the last replication, you will not be able to access the server.
Gameplay mechanics and playing environments may be quite different from what you're used to on Tranquility. Here, the world is constantly changing.
Please note that GM support is not available on the test server nor with problems you may encounter accessing it. Enter at your own risk!
To gain access to the test servers, follow these instructions:
Windows
- Create a separate folder for your test client ( i.e "C:\evetest").
- Copy everything from your original EVE folder (by default locate at "C:\Program. Files\CCP" ) to the new ("C:\evetest"). This step is important, since patching the test client will render it incompatible with the Tranquility server.
- Go to this webpage to download patches for Singularity.
- Download the "Download TQ to Singularity Patch" or the Multiplicity one if you are going to test on that server.
- Apply the patch to the correct EVE installation such as "C:\evetest". You will be promted to point to the appropriate installation folder.
- Create a shortcut for the new eve.exe file inside C:\evetest.
- Right click on the shortcut and select properties, then select the Shortcut tab.
- add /server:Singularity for Singularity and press OK. Note: This includes entering the 'space' before the '/'
The final look of the Target line would look something like this ( Different between client locations).
"C:\evetest\eve.exe" /server:87.237.38.50. - Then double click on the shortcut and log in.
- Download the Tranquility client: http://www.eve-online.com/download/(If you have already installed the EVE Client, skip to step 3).
- Install the Tranquility client.
- Rename your install to "EVE Online TQ" or something of your choice.
- Install another copy of EVE Online, download the client here http://www.eve-online.com/download/
- Rename that to "EVE Online Singularity" or something of your choice.
- Go here: http://www.eve-online.com/patches/patches.asp?s=singularity.
- Download the latest Tranquility to Singularity patch.
- Execute it and point it to the install called "EVE Online Singularity."
- Note that the client you just patch changed name to "EVE Online" again. So, rename it to "EVE Online Singularity" again.
- Run the client.
- Install the EVE client using the Cedega installer ( if you've done this already you can of course skip this step).
- Open up a termninal and do cp -R ~/.cedega ~/.cedegaSISI
- Edit the following file using your favorite editor ( nano, pico or vi ) ~/.cedegaSISI/EVE\ Online/config
"Path" = "/home/[your username]/.cedega/EVE Online/c_drive"
change it to to this:
"Path" = "/home/[your username]/.cedegaSISI/EVE Online/c_drive" - Edit ~/.cedegaSISI/.updater/cedegaUpdateChecker
if [ -e ${HOME}/.cedega/.cedegarc ]; then
change it to this:
if [ -e ${HOME}/.cedegaSISI/.cedegarc ]; then
then change the line in the same file
export CEDEGA_PATH=${HOME}/.cedega
change it to this:
export CEDEGA_PATH=${HOME}/.cedegaSISI - Edit ~/.cedegaSISI/.EveOnline-linux/manifest
add .testing to the end of the file so it'll look like this http://updates.cedega.com/manifest/eveonline/EveOnline-linux.manifest.testing - Create a game launcher for SiSi
- Right click on your desktop -> create launcher and set as following
type : Application
name: Eve SISI client
command : /home/[your username]/.cedegaSISI/.updater/cedegaUpdateChecker -GAME EveOnline-linux
comment:
- Then the game config launcher ( eve -config )
- Right click on your desktop -> create launcher
type : Application
name: Eve SISI config
command : /home/[username]/.cedegaSISI/.updater/cedegaUpdateChecker -GAME EveOnline-linux -config
comment:
- Right click on your desktop -> create launcher and set as following
- Go to this webpage to download patches for Singularity.
- Install the test patches
- Install the patch by starting the new eve sisi config launcher.
- There click on the "install game patch" button select the patch.
- navigate to c:/program files/ccp/eve and install the patch.
- Go to /home/[username]/.cedega/EVE Online/
- edit games.ini
- Locate the line "commandlineargs="
- Add this to the end: /server:87.237.38.50
- It should now look like this: "commandlineargs=/server:87.237.38.50"
- Save and close the file.
- When you install the patch, make sure you update the new client ("c:\evetest"), not the original you use to play on Tranquility.
Please take the time to bug report as much as you can. Your feedback is also very important for what features are developed or changed, so don't hesitate to post your thoughts on the Game Development Forum.
Please read the test server rules before logging in. They may be found here.
Useful general information is available here.
Related Links
Test-Server Patches (singularity)
Labels: Singularity
Wormhole Harvesting



Posted by Redundant blogger 0 comments
Labels: Wormhole Guide, Wormholes
Wormhole Wandering Essentials
1. Scan Probes and a Scan Probe Launcher. Top of the list as this is an absolutely essential module. Any pilot entering W-space without a scan probe launcher is a fool. I take at least 15 scan probes in the cargo hold, plus 10 in the launcher. As I use 5 per scan this gives me 5 chances. So far this has seemed to be adequate. Pay attention to their flight time as I have carelessly lost a group due to the expiration timer.
2. Cloak. Dependant on your intentions for entering w-space, a cloak can become your best friend. Use when-ever you feel fear or your mind is occupied elsewhere ie: scanning.
3. A formidable omni-tank. Absolutely necessary if battle is sought as the sleepers will attack your lowest resistances. Within class 4 wormholes literally no-one is safe as a few seconds as primary can turn almost any ship to dust. Ensure your tank is as high as possible with capacitor to spare as sleepers can and will NOS your ship with several streams.
4. Drones. These little pups can act as a decoy for the sleepers. Although sleepers display intelligence they can still be fooled into attacking several drones instead of ones precious hull. If your tank is failing against the sleepers’ onslaught then stop firing and deploy drones. The sleepers will then consider them the threat until such time your tank can be repaired. If you’re to use this tactic take the least expensive, fastest and smallest drones you can and use them as fodder for the fight. Note position 2:01 in this captured recon video where the sleepers switch to the drones perceiving them as the threat instead of the (brave) Myrmidon. Unfortunately the pilot did not take this opportunity to escape while the webs and scrams were released from his battered ship.
5. Ammunition. The use of Amarr vessels permits endless exploring as lasers do not require ammunition to fire, only c apacitor. If you are planning on using missiles, hybrids, rails or projectile turrets then a healthy supply will be needed as re-supply is time consuming and dangerous.
6. The Wormhole Database. This little gem will tell you what type of wormhole you are entering, where it leads and what type of star the wormhole contains. Depending on the type of star will change the affects on your ships abilities. Pay extra attention to this as the effects can severely undermine your ships capability.
7. Nanite Repair paste. If you can overload your modules then take a healthy supply of Nanite Repair Paste as you may find you overload more often then usual.
8. ALT. Another character fitted with a cloak and a scan probe launcher is wise as the fate of your main vessel is not guaranteed. Use the ALT to locate an exit should the worst happen and you are left ship-less without a paddle.
9. Cargo Space. This will be at a premium if you plan to harvest the sleeper wrecks. If at all possible increase your base cargo space by adding a cargo expander or two. This method has several drawbacks. The first is the reduction of available modules on the ship. Also, the actual space increase may not be sufficient to warrant the use of a low module slot. This is entirely dependant on your intentions.
10. Combat Clone. Never take your best clone. Again as with lawless areas of New Eden, pirates such as myself and other predators will be prowling the void looking for a juicy meal so be prepared for the worst.
Posted by Redundant blogger 0 comments
Labels: Wormhole Guide, Wormholes



