Toggle search
Toggle menu
4.5K
7.6K
15.6K
232.1K
EVE University Wiki
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

User:JohnPlayerNotSpecial/wildvelatorhunt: Difference between revisions

From EVE University Wiki
More actions
← Older editNewer edit →
VisualWikitext
m pictures
m yo
Line 1: Line 1:
[[File:Bookmarks 14au.png|thumb]]
= Wild Velator Hunt =


[[File:Dotlan 2jumps luse.png|thumb]]
This Event revolves around "'''''named'''''" <s>Noobships</s> [[Corvettes]] placed in a couple of highsec systems that participants have to [[Probe scanning|combatscan]] & destroy. Whoever got the most kills at the end wins.


new
It's meant to demonstrate howto combatscan, be fast while doing, and how to link kills into a chat.
 
 
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.
 
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.
 
 
== Prepwork ==
[[File:Dotlan 2jumps luse.png|thumb|Example Locations when HSC still existed]]
 
[[File:Bookmarks 14au.png|thumb|Example bookmarks. Note the max distance being below 14.3 AU of the Sun]]
 
 
=== 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: [https://evemaps.dotlan.net/map/Verge_Vendor/Amygnon Amygnon]).
* Decide on a destination system. (Example: [https://evemaps.dotlan.net/map/Verge_Vendor/Luse 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 [[Directional scanning|D-Scan]], if you dont see any '''''Wild Velator'''''s 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 [[Frigates#Exploration|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'').
 
 
<tabs>
<tab name="Caldari">
{{ShipFitting
| ship= Heron
| fitName= Heron
| fitID= Heron-Heron
| low1name= Nanofiber Internal Structure I
| low1typeID= 2603
| low2name= Nanofiber Internal Structure I
| low2typeID= 2603
| mid1name= 5MN Y-T8 Compact Microwarpdrive
| mid1typeID= 5973
| mid2name= Scan Rangefinding Array I
| mid2typeID= 33180
| mid3name= Scan Acquisition Array I
| mid3typeID= 33176
| high1name= Expanded Probe Launcher I
| high1typeID= 18639
| rig1name= Small Gravity Capacitor Upgrade I
| rig1typeID= 31213
| rig2name= Small Gravity Capacitor Upgrade I
| rig2typeID= 31213
| drone1name= Hobgoblin I x3
| drone1typeID= 2454
| charge1name= Combat Scanner Probe I x16
| charge1typeID= 30028
| difficulty= 0
| version= 2018-02
| skills=
| notes= should be alpha friendly.
| showTOC= N
| showSKILLS= N
| showNOTES= Y
| alphacanuse= Y
}}
</tab>
<tab name="Minmatar">
{{ShipFitting
| ship= Probe
| fitName= Probe
| fitID= Probe-Probe
| low1name= Co-Processor I
| low1typeID= 3887
| low2name= Nanofiber Internal Structure I
| low2typeID= 2603
| low3name= Nanofiber Internal Structure I
| low3typeID= 2603
| mid1name= 5MN Y-T8 Compact Microwarpdrive
| mid1typeID= 5973
| mid2name= Scan Rangefinding Array I
| mid2typeID= 33180
| mid3name= Scan Acquisition Array I
| mid3typeID= 33176
| high1name= Expanded Probe Launcher I
| high1typeID= 18639
| rig1name= Small Gravity Capacitor Upgrade I
| rig1typeID= 31213
| rig2name= Small Gravity Capacitor Upgrade I
| rig2typeID= 31213
| drone1name= Hobgoblin I x3
| drone1typeID= 2454
| charge1name= Combat Scanner Probe I x16
| charge1typeID= 30028
| difficulty= 0
| version= 2018-02
| skills=
| notes= should be alpha friendly.
| showTOC= N
| showSKILLS= N
| showNOTES= Y
| alphacanuse= Y
}}
</tab>
<tab name="Gallente">
{{ShipFitting
| ship= Imicus
| fitName= Imicus
| fitID= Imicus-Imicus
| low1name= Nanofiber Internal Structure I
| low1typeID= 2603
| low2name= Nanofiber Internal Structure I
| low2typeID= 2603
| low3name= Co-Processor I
| low3typeID= 3887
| mid1name= 5MN Y-T8 Compact Microwarpdrive
| mid1typeID= 5973
| mid2name= Scan Rangefinding Array I
| mid2typeID= 33180
| mid3name= Scan Acquisition Array I
| mid3typeID= 33176
| high1name= Expanded Probe Launcher I
| high1typeID= 18639
| rig1name= Small Gravity Capacitor Upgrade I
| rig1typeID= 31213
| rig2name= Small Gravity Capacitor Upgrade I
| rig2typeID= 31213
| drone1name= Hobgoblin I x3
| drone1typeID= 2454
| charge1name= Combat Scanner Probe I x16
| charge1typeID= 30028
| difficulty= 0
| version= 2018-02
| skills=
| notes= should be alpha friendly.<li></li>only 3 drones so it's fair compared to the other T1 explorers.
| showTOC= N
| showSKILLS= N
| showNOTES= Y
| alphacanuse= Y
}}
</tab>
<tab name="Amarr">
{{ShipFitting
| ship= Magnate
| fitName= Magnate
| fitID= Magnate-Magnate
| low1name= Co-Processor I
| low1typeID= 3887
| low2name= Co-Processor I
| low2typeID= 3887
| low3name= Nanofiber Internal Structure I
| low3typeID= 2603
| low4name= Nanofiber Internal Structure I
| low4typeID= 2603
| mid1name= 5MN Y-T8 Compact Microwarpdrive
| mid1typeID= 5973
| mid2name= Scan Rangefinding Array I
| mid2typeID= 33180
| mid3name= Scan Acquisition Array I
| mid3typeID= 33176
| high1name= Expanded Probe Launcher I
| high1typeID= 18639
| rig1name= Small Gravity Capacitor Upgrade I
| rig1typeID= 31213
| rig2name= Small Gravity Capacitor Upgrade I
| rig2typeID= 31213
| drone1name= Hobgoblin I x3
| drone1typeID= 2454
| charge1name= Combat Scanner Probe I x16
| charge1typeID= 30028
| difficulty= 0
| version= 2018-02
| skills=
| notes= should be alpha friendly.
| showTOC= N
| showSKILLS= N
| showNOTES= Y
| alphacanuse= Y
}}
</tab>
<tab name="Elite">
{{ShipFitting
| ship= Megathron
| fitName= Scanotron 500
| fitID= Megathron-Scanotron-500
| low1name= Civilian Damage Control
| low1typeID= 30839
| low2name= Inertial Stabilizers I
| low2typeID= 1403
| low3name= Inertial Stabilizers I
| low3typeID= 1403
| low4name= Inertial Stabilizers I
| low4typeID= 1403
| low5name= Civilian Armor Repairer
| low5typeID= 21853
| low6name= Civilian Armor Repairer
| low6typeID= 21853
| low7name= Civilian Armor Repairer
| low7typeID= 21853
| low8name= Explosive Coating I
| low8typeID= 1264
| mid1name= 1MN Civilian Afterburner
| mid1typeID= 21857
| mid2name= Scan Acquisition Array I
| mid2typeID= 33176
| mid3name= Scan Rangefinding Array I
| mid3typeID= 33180
| mid4name= Sensor Booster I
| mid4typeID= 1973
| high1name= Expanded Probe Launcher I
| high1typeID= 18639
| rig1name= Large Gravity Capacitor Upgrade I
| rig1typeID= 25936
| rig2name= Large Gravity Capacitor Upgrade I
| rig2typeID= 25936
| drone1name= Civilian Hobgoblin x5
| drone1typeID= 32465
| charge1name= Combat Scanner Probe I x16
| charge1typeID= 30028
| charge2name= Scan Resolution Script x1
| charge2typeID= 29011
| difficulty= 1
| version= 2018-02
| skills=
| notes= do NOT use this, it's a joke.
| showTOC= N
| showSKILLS= N
| showNOTES= Y
}}
</tab>
</tabs>
 
 
== Running ==
 
{{MessageBox|Example Fleet MOTD:
|
  <nowiki>
.
✫ ✫ ✫ ✫ ✫  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.
  </nowiki>
|collapsed=no}}
 
* 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. [https://pastebin.com/3YgitbSJ|Code here]. ('' '''IF''' you decide to use that one, edit accordingly and do not blame me for spaghetti'').
 
 
HF !
 
[[Category:Events]]
Retrieved from "https://wiki.eveuniversity.org/User:JohnPlayerNotSpecial/wildvelatorhunt"