Wild Velator Hunt
This Event revolves around "named" Noobships Corvettes placed in a couple of highsec systems that participants have to combatscan & destroy. Whoever got the most kills at the end wins.
It's meant to demonstrate howto combatscan, be fast while doing, and how to link kills into a chat.
Ppl have to go from the starting system to a destination system, from which within X jumps are placed Y amount of "Wild Velator"s (renamed Corvettes).
As it's happening in HighSec, it only works if the organizer and participants are in the same corp and that corp has Friendly Fire enabled. E-Uni corp does.
As Info: If you decide to run this event let it be known that it takes a huge amount of prepwork (read: time), mainly for making bookmars & placing/renaming the Corvettes on them. The actual runtime is like an hour.
Prepwork


Locations
- Decide on a formup system. This is where the start is. It needs to be at least not be adjacent of any of the systems where Corvettes are going to be placed (Example: Amygnon).
- Decide on a destination system. (Example: Luse).
- Decide how far out you want to place the Corvettes (Aka the X: i usually go for within 1 or 2 jumps).
- Decide how many Corvettes you want to place (Aka the Y: i usually go for 4 or 5 ).
In my example picture i go for "within 2 jumps" and place "5" Corvettes in each system. That'll give 45 Corvettes to destroy.
Bookmarks
- Start from the Sun and make Y amount of bookmarks.
- Verify that none of the bookmarks is further than 14.3 AU of the Sun. This is important as that way i tell ppl "check your D-Scan, if you dont see any Wild Velators the system is cleared".
In my example picture the furthest is 13.1 AU.
Ship placing
- Dock up in station or structure in system.
- Board "free corvette".
- Rename to "Wild Velator". (Or "Wild Ibis" if Caldari / "Wild Reaper" if Minmatar / "Wild Impairor" if Amarr).
- Warp to bookmark at zero, eject from ship.
- Back to station/structure, rinse and repeat until all bookmarks have a Corvette placed.
- Once system seeded, go next system.
This is the time consuming part of this event.
It needs to be done by the organizer ! Otherwise the kills will not show up in your "Notification History" and/or Zkill. This is relevant for the running part for keeping track.
Fits
Participants are restricted to bring T1 fitted T1 Explorers. This to make it fair...ish regarding trained skill differences. Preferably clean clone but that's too much of a pain to verify.
They're all pretty much the same, toy around with modules to have at least the expanded launcher and the prop online.
Guns to taste if fitting space allows.
For elite persons who want a challenge there's an option too but so far i've had it seen being brought exactly once. (Hint: it's a joke, dont bring this).
Expanded Probe Launcher I
5MN Y-T8 Compact Microwarpdrive
Scan Rangefinding Array I
Scan Acquisition Array I
Nanofiber Internal Structure I
Nanofiber Internal Structure I
Small Gravity Capacitor Upgrade I
Small Gravity Capacitor Upgrade I
Hobgoblin I x3
Combat Scanner Probe I x16


















- should be alpha friendly.
Expanded Probe Launcher I
5MN Y-T8 Compact Microwarpdrive
Scan Rangefinding Array I
Scan Acquisition Array I
Co-Processor I
Nanofiber Internal Structure I
Nanofiber Internal Structure I
Small Gravity Capacitor Upgrade I
Small Gravity Capacitor Upgrade I
Hobgoblin I x3
Combat Scanner Probe I x16



















- should be alpha friendly.
Expanded Probe Launcher I
5MN Y-T8 Compact Microwarpdrive
Scan Rangefinding Array I
Scan Acquisition Array I
Nanofiber Internal Structure I
Nanofiber Internal Structure I
Co-Processor I
Small Gravity Capacitor Upgrade I
Small Gravity Capacitor Upgrade I
Hobgoblin I x3
Combat Scanner Probe I x16



















- should be alpha friendly. only 3 drones so it's fair compared to the other T1 explorers.
Expanded Probe Launcher I
5MN Y-T8 Compact Microwarpdrive
Scan Rangefinding Array I
Scan Acquisition Array I
Co-Processor I
Co-Processor I
Nanofiber Internal Structure I
Nanofiber Internal Structure I
Small Gravity Capacitor Upgrade I
Small Gravity Capacitor Upgrade I
Hobgoblin I x3
Combat Scanner Probe I x16




















- should be alpha friendly.
Expanded Probe Launcher I
1MN Civilian Afterburner
Scan Acquisition Array I
Scan Rangefinding Array I
Sensor Booster I
Civilian Damage Control
Inertial Stabilizers I
Inertial Stabilizers I
Inertial Stabilizers I
Civilian Armor Repairer
Civilian Armor Repairer
Civilian Armor Repairer
Explosive Coating I
Large Gravity Capacitor Upgrade I
Large Gravity Capacitor Upgrade I
Civilian Hobgoblin x5
Combat Scanner Probe I x16
Scan Resolution Script x1


























- do NOT use this, it's a joke.
Running
Example Fleet MOTD: |
---|
. ✫ ✫ ✫ ✫ ✫ Wild Velator Hunt ✫ ✫ ✫ ✫ ✫ Rules: => Formup in *insertformupstationhere* => In each System within X jumps of *targetsystem* are Y "Wild Velator". => Use D-Scan & Combat Probes to scan them down. => Shoot them. (Fit drones or weapons or both). => Link the Killmail here in Fleet. => Whoever kills the most, wins. Hint: Start from the Sun. |
- Participants need to link their kills into Fleetchat, this allows for others to check if a system is cleared or not.
- Organizer needs to keep track of kills.
Contesting a kill (if more than one participant lands on a Corvette and starts shooting) is fair game.
Shooting eachother however is not !
For keeping track of kills, ean easy way is to have ingame notepad open & add the kills per person as numbers as they come in.
Alternatively, check your own zkillboard for losses.
Personally i run a console script to keep track. Code here. ( IF you decide to use that one, edit accordingly and do not blame me for spaghetti).
HF !