These systems we operate in are 'owned' by our alliance and the responsibility of defending it ultimately falls on our shoulders, whether you are just new here or a seasoned null veteran. Amazing PVP skill isn't a hard requirement to take up arms and defend our sovereignty. With proper guidance and the right ship, the noobest of the noob can make a huge difference in making sure these pockets stay close to home.

To this point things have gone rather swimmingly, but every day there is a period of time where YOU can be the HERO that saves our lands. When a message like 'R3-K7K ihub under attack' or 'R3-K7K ihub being toasted' appears in fleet or intel, its your moment to shine.

Course of Action

Step 1.

If you see the call, stop what you are doing. Get in a clean clone, grab a shuttle and get to R3-K7K (unless you're mid PVP or 4 holes deep in a wh dive). Do not come into system in other ships. They will camp the gates and often be trying to stop you with extreme firepower. Just wave as you go by in a shuttle.

Step 2.

Get in fleet and jump into comms on discord. IF no one is on discord comms, jump in alpha channel and wait for other channel call - congratulations you've just started the fleet scramble comms link and are already making a name for yourself as an action hero.

Step 3.

In fleet or comms, someone will identify the 'toaster' ship. When we say toaster, this means someone who is currently using an Entosis Link module to influence our sovereignty structures (Territorial Claim Unit & Infrastructure Hub) as a way of contesting our ownership of a specific system. This 'toaster' is our only target. We must lock him and jam him to stop the 'toasting' process. In doing so we would need to identify the ship's sensor strength attributes. Right click on the toasting ship to show info, go to attributes, down the bottom you will see 'sensor strength'. Hover the largest value one and the first word is the jammer we need to use to stop him. Check your locking range. You'll need to be inside that range when you land, burning toward him will end in death if its more than 5?km before you get a jam.

In the station in R3, R3-K7K - Skipp's Banana Boat, there are griffins on contract. Buy one, get in and fit all the rigs, fitting the jammers that will work on the toaster by name.

You are now fully set. You can save the world (system).

Step 4.

Open the LINE Providence bookmarks folder. People will be calling the bookmark names to warp to so you avoid bubbles when attempting to jam.

How to tell when to jam

Hopefully, by the time you've arrived in system, one person is cloaked on a bookmark near the IHub/TCU and can tell you when a jamming attempt should be made. If there is no present coordination, you can undock from base and stop your ship on tether. From there, you can see the IHUB/TCU. If the IHUB/TCU is reporting that 'LINE is making progress' (click on it to focus it), no need to warp and jam. This avoids us from potentially accumulating unnecessary losses while the sov structure is repairing. When it says 'Attackers are making progress', it's time to be a hero. If there are others on comms, organise who is next, make a queue, and coordinate defensive actions.

How to Jam

If someone is calling, they will give you a bookmark name in comms or fleet chat. Once you have the go signal, warp to that specific bookmark. Make sure your overview is setup properly so you can see your target ship right away. Pre-heat your ECM modules and get them running before you land on grid. This way once you lock up the target, the ECMs activate immediately. (Take care if prefit, they may be on wrong row for F1,F2). As you land on grid with the ihub/tcu, your one and only task is to lock the toaster and have your jams running. If you get lock and they are running, your job is done. 1 second is enough. Warp out. You're now the saviour of the system!!!

If you die in the attempt all ships will be paid for.