News: Providence Bloc and Northern Coalition(dot) Continue to Fight over KBP7-G

KBP7-G system, Providence region. On the 28th of June, at 19:00 EVE Standard Time, Providence Bloc and Northern Coalition(dot) [NC] clashed once more over the fate of the KBP7-G system.

Providence Bloc went on the offensive in a bid to reclaim its lost systems. BK4-YC, Y-MPWL and KBP7-G systems were put into reinforced mode by Providence Bloc, with the KBP7-G Infrastructure Hub coming out of reinforced on the 28th.

Providence Bloc organized a full scale attack in order to reclaim the system. It had assembled a full Ishtar Heavy Assault Cruiser fleet with a Stealth Bomber wing and E-War Frigates, all told around 300 pilots. The force made its way towards KBP7-G in order to force the Infrastructure Hub into its second timer. 

[NC] wasn't sitting idle either and organized a fleet of its own to defend the system, a Loki Strategic Cruiser fleet reaching nearly 100 pilots. The force bridged into the system before Providence Bloc's arrival, settling on the XHQ-7V gate the only point of entry for Providence Bloc, in anticipation of the incoming hostiles.

Providence Bloc jumped into the system and the awaiting [NC] fleet, its bomber wing landing a Void bomb run, which drained the capacitor of most of the Lokis, switching off their armor hardeners. The Providence Bloc Ishtars then de-cloaked, dropped sentry drones and anchored up, starting the fight. 

At first, the Ishtars managed to volley Lokis and Logistic ships, seemingly winning the battle. However as time went on, this changed. The [NC] Lokis started tanking better, their Logistics getting on the ball. Providence Bloc on the other hand, was doing poorly. With all their fleet anchors webbed, the Ishtars remained in close proximity to the Lokis, which proved fatal

After a brief exchange with mounting losses the Ishtars finally managed to gain some distance from the [NC] fleet. Attempts to break the Lokis' tank with fresh sets of drones proved futile, thus the Providence Bloc Fleet Commander made the call to disengage, leading the fleet to warp off to an asteroid belt then to the XHQ-7V gate.

[NC] attempted to give chase, managing to snag stragglers but the main Providence Bloc fleet managed to jump out of the system and dock up, conceding the field. With Providence Bloc defeated, [NC] brought their Super Carriers and quickly removed the Providence Bloc Sovereignty Blockade Units in the system, securing it for themselves once more.

With this, both fleet safely extracted, ending large scale hostilities in the region.

The Battle from the Providence Bloc PoV, Courtesy of Mangraa Dementia

Battle report for the KBP7-G system can be found here.

All told, the system saw 400 pilots in local, with Time Dilation reaching up to 40% during the fighting. From start to end, the battle lasted 30 minutes.

Providence Bloc lost 83 ships, including 31 Ishtars, for a total of 9.04 Bil ISK damage. [NC] lost 9 ships, including 3 Lokis, for a total of 5.24 Bil ISK damage.

After the battle it became apparent that the [NC] fleet was prepared for Providence Bloc's Ishtar fleet, as the Loki fit was meant to counter the use of sentry drone damage, specifically Bouncer and Curator sentry drones. This allowed the [NC] fleet to tank the incoming damage from the Ishtar fleet and along with webbing their anchors, forced Providence Bloc to fight close range at first, where the Lokis had a clear advantage.

Reports from both fleets indicate that fire was split between targets, which allowed both Logistics teams to keep ships alive in their respective fleets far longer. This is another reason for the low damage output, especially on Providence Bloc's side.

Though Providence Bloc lost both the field and the strategic objective, with talks of [NC] deploying to a different region of space, it may be able to regain its conquered systems as [NC]'s Super Capital umbrella is expected to vanish. Without it, Providence Bloc may be able to field its main doctrines, which were abandoned due to the pervasive use of Super Carriers by [NC] during their deployment, granting them an actual fighting chance. 

The EVE Scribe will continue to update on the situation as it develops.

Special thanks Mangraa Dementia, of Blue Tridents, Sev3rance, for supplying the video footage

News: Providence Bloc Defeated in 9UY4-H

Disclaimer: Due to scarcity of reports, the numbers in the article are evaluations only. The events transcribed are based on the few witness accounts given, apologies in advance for any and all inaccuracies.

9UY4-H system, Providence region. On the 26th of June, at 18:00 EVE Standard Time, forces belonging to Providence Bloc clashed once more with Northern Coalition(dot) [NC] in the system, leading to a ruinous defeat.

[NC] forces had deployed Sovereignty Blockade Units in the system, in an attempt to provoke a fight from Providence Bloc. This worked, as Providence Bloc organized an Ishtar Heavy Assault Cruiser fleet, estimated at 120 pilots.

The force arrived in the system and worked on removing Sovereignty Blockade Units from the gates, managing to destroy one before [NC] forces showed, bridging a Tempest Fleet Issue Battleship fleet into the 4B-NQN system next door, estimated at 60 pilots with Triage Carrier support.

The [NC] force jumped into the 9UY4-H system, the Triage Archons de-cloaking first before the rest of the fleet. The [NC] fleet however, was greeted by Providence Bloc, who had reports on it and already prepared in advance on the gate.

The battle started with Providence Bloc managing to volley off a couple of Battleships before the [NC] fleet could anchor up properly. Once it did, it managed to stabilize, the Triage Carriers doing their job properly. 

In contrast, the Providence Bloc fleet was hemorrhaging ships. An attempt to warp off the field and back at zero on the [NC] fleet in order perhaps, to get below the Battleships guns and negating their tracking, miserably failed - Resulting in slaughter.

Quickly, the Isthar fleet decided to warp across the system, forcing the much slower Battleships to give chase, at the same time a Stealth Bomber wing was working diligently to remove one of the Sovereignty Blockade Units, thus securing the system.

To aid in buying time, Interdcitors kept the Triage Carriers under interdiction probes, sacrificing ships to force them to stay in place. Since the Triage Carriers were the backbone of the Logistics team of the [NC] fleet, this delayed their attempts to re-engage.

Managing to destroy the second Sovereignty Blockade Unit and thus secure the system, Providence Bloc retreated, conceding the field to [NC]. Thus, [NC] forces returned to the 4B-NQN gate in order to guard their last remaining Sovereignty Blockade Unit.

However, this was not the end of hostilities for the night, as the Providence Bloc fleet reshipped to Naga Battlecruisers and returned to the field. A second battle flared up, with Providence Bloc warping to the [NC] fleet on the 4B-NQN gate in close range an opening fire, managing to volley off Battleships but trading many Naga Battlecruisers in return.

As damage output decreased due to losses, Providence Bloc was unable to break the tank of the Battleships and once more retreated, leaving the field for [NC] to hold. Having gotten the fight they wished for, [NC] forces extracted safely, ending hostilities for the night.

Battle report for the 9UY4-H system can be found here.

The battle lasted nearly an hour, with the system hosting less than 300 pilots in local and Time Dilation not reported as a major issue.

Providence Bloc lost 84 ships including 29 Battlecruisers and 24 Isthars for a total of 12.38 Bil ISK. [NC] lost 13 ships including 4 Battleships for a total of 2.45 Bil ISK.

Providence Bloc managed to secure the system, its strategic objective, but at a cost. [NC], on the other hand, got the fight it wished for and managed to hold the field. 

As the two entities continue to fight, it remains to be seen how this war concludes. The EVE Scribe will keep you up to date on developments.

Update: KBP7-G Status

KBP7-G system, Providence region. On the 24th of June, the system fell to Northern Coalition(dot) [NC] forces unopposed.

Providence Bloc fought [NC] every step of the way, but after the station was taken and the Territorial Claim Unit destroyed, had to concede the system. 

 Click for Killmail

While there may have been a chance to delay the [NC] Territorial Claim Units from reaching online status, [NC] had them deployed on a heavily fortified tower (Also known as a deathstar). At the same time, a timer was coming up for a station in the BK4-YC system, and the Providence Bloc Fleet Commanders decided to abandon the KBP7-G system in favor of wrestling BK4-YC back.

At this stage 3 of the 4 systems connection the Providence region to Empire space have been taken over by [NC], for what purpose none but [NC] can tell. Regardless, Providence Bloc continues to fight [NC] forces daily, resisting their advance. The EVE Scribe will keep you posted.

News: Providence Bloc and Northern Coalition(dot) Clash over BK4-YC

MVCJ-E system, Providence region. On the 24th of June,  21:30 EVE Standard Time, forces belonging to Providence Bloc and Northern Coalition(dot) [NC] clashed in the system in a brawl that showed much effusion of blood and destruction.

The fight began with Providence Bloc attempting to regain the BK4-YC system, which it lost a few days before. The station was leaving its first reinforcement timer, and Providence Bloc forces were moving in to push it into its second timer.

Providence Bloc brought a 150 pilot Ishtar Heavy Assault Cruiser fleet, with a Stealth Bomber wing for support. [NC] forces were aware of Providence Bloc's attempts, and decided to use the timer to get a fight, the system itself holding little significance for them.

[NC] brought an estimated 70 pilot Loki Strategic Cruiser fleet and set up on the 2-TEGJ gate in the MVCJ-E system. The system is the only point of entry to the BK4-YC system, and the 2-TEGJ gate itself was the most probable point of entry for the Providence Bloc fleet, which was spotted in the 9UY4-H system clearing a hostile tower as it was slowly forming up.

Providence Bloc made its way as theorized to the MVCJ-E system, their Fleet Commander getting reports of the awaiting [NC] fleet. However, he made the decision to jump into the system anyway, starting the fight. The Providence Bloc Ishtars quickly anchored as they entered system, losing a few ships as they pulled range. Sentry drones were dropped in large clumps, making it hard for the [NC] Lokis to find a good spot to negate their tracking and optimal range.

The Ishtars started returning fire, managing to break the tank both of the Logistics and the Lokis themselves. For a while the two sides exchanged losses, Providence Bloc settling to an alternating rhythm of Logistic ship, then Strategic Cruiser, while [NC] busied itself with removing as many mainline ships as possible.

At some point the [NC] fleet was getting dangerously low on Logistics ships, and the call was made to bring Triage Archons. However, due to the distance of the system from the [NC] staging, the Carriers had to jump to a system a few jumps from the fight itself and make their way to the battle.

At this point the Fleet Commanders' opinions split. According to the Providence Bloc Fleet Commander, [NC] brought the Triage Carriers to the system via a cynosural beacon off grid, while the [NC] Fleet Commander stated that they jumped via gate from the LF-2KP system.

Regardless, both agree that the Triage Carriers arrived quite late in the battle, thanks in part to Providence Bloc Interdictors which deployed interdiction probes on them, preventing them to warp and join the [NC] fleet for quite a while.

With the [NC] Triage on field, the Lokis fared better, managing to stabilize, many saved entering deep armor. Realizing they couldn't be broken anymore, nor the Triage Archons themselves and sustaining continued losses, Providence Bloc decided to extract from the system, conceding the field to [NC] forces. [NC] itself decided not to remove the Providence Bloc Sovereignty Blockade Unit or repair the station, choosing instead to extract safely home, ending large scale hostilities for the day.

Battle report for the MVCJ-E system can be found here.

During the peak of the battle, the system saw less than 300 pilots in local, with Time Dilation not reported as an issue. The fight itself took nearly half an hour in total.

Providence Bloc lost 107 ships, 19 of which were Ishtars, for a total of 9.31 Bil ISK damage. [NC] suffered 28 losses, 12 of which were Strategic Cruisers, for a total of 11.37 Bil ISK damage.

Providence Bloc lost the field, but thanks to [NC]'s decision to leave the BK4-YC station unprotected, managed to later reinforce it, achieving the strategic objective. Special mention has to be made of the Providence Bloc Stealth Bomber wing, whose Void Bomb runs managed to help cap out Lokis, turning their shield off and stopping them in their tracks.

With a new timer for the station, it is quite possible the system will see further clashes soon by the two sides, as the war in the Providence region continues. The EVE Scribe will keep you posted.

News: Providence Bloc Fights Northern Coalition(dot) over Final Infrastructure Hub Timer in KBP7-G

KBP7-G system, Providence region. On the 22nd of June, 16:30 EVE Standard Time, Providence Bloc and Northern Coalition(dot) [NC] forces clashed for the third time in the system, over the final Infrastructure Hub timer, in a battle that saw Providence Bloc defeated once again.

Providence Bloc brought a 90 pilot Ishtar Heavy Assault Cruiser fleet to the system and quickly positioned itself on the Dital gate. Having arrived before [NC] forces, the fleet quickly set up to take down the Sovereignty Blockade Unit, thus securing the system and the Infrastructure Hub from [NC]'s aggression.

However, as the Providence Bloc force was busy applying damage to the structure, a cynosural beacon was lit at the edge of the grid, and an [NC] Loki Strategic Cruiser fleet bridged into the system, estimated at 50 pilots. The force attempted to warp on top of the Providence Bloc fleet, but defensive interdiction probes launched beforehand allowed Providence Bloc to keep range.

The two fleets then engaged each other, Providence Bloc managing to destroy [NC] Logistics ships but losing Ishtars in return. As the battle raged on, both the Providence Bloc anchor and the Fleet Commander were volleyed off the field (Though by mistake, as was later confirmed by both sides). This led to the Providence Bloc fleet losing organization and allowing [NC] forces to burn closer. With the Lokis now at their optimals, the battle became a one sided affair, Ishtars being destroyed left and right.

After regaining composure, Providence Bloc forces decided to retreat rather than risk the complete annihilation of their fleet, warping off to the B-WPLZ gate and jumping over, regrouping on the other side of the gate. [NC] forces chose not to chase, and brought 24 Super Carriers instead which made short work of the Infrastructure Hub of the system.

Click for Killmail

With the Infrastructure Hub destroyed, both sides departed, ending hostilities in the system.

Battle report for the KBP7-G system can be found here.

All told the system saw less than 200 pilots in local, with Time Dilation not reported at all. From start to end, the battle lasted 10 minutes.

Providence Bloc lost 46 ships, 11 of which were Ishtars for a total of 4.92 Bil ISK. [NC] for its part lost 7 ships for 1.32 Bil ISK.

Providence Bloc lost both the fight and the strategic objective, which allows [NC] to push forward with its conquest of the system. As the Station in the system is expected to exit its final reinforcement timer soon, Providence Bloc is in danger of losing another system to [NC], unless something drastic happens. The EVE Scribe will keep you informed.

News Bulletin: BK4-YC, Amarr, KBP7-G

A brief news bulletin for the residents of Providence covering the recent developments in and around the region.

BK4-YC system, Providence region

Curatores Veritatis Alliance [CVA] lost sovereignty over the system after downtime on the 21st of June. Sources claim the loss was due to unpaid bills by the corporation which owned the system at the time, The Ostrogoths. 

Logistics problems caused the system to remain unclaimed long enough for Northern Coalition(dot) [NC] forces to take notice. Attempts to reclaim the system were rebuffed by [NC] Super Carriers, with the station conquered by them as well. 

After a day of back and forth with Providence Bloc and [NC] destroying each others' Territorial Claim Units, [NC] managed to get out with its hand on top, taking the system. 

The loss of the system is further aggravating as it allows [NC] a safe staging in the middle of the Providence region, from which it can strike at the R3-K7K system, the last relatively safe gateway to the region.

Amarr system, Domain region 

The Burn Amarr campaign has concluded. From downtime on the 19th to downtime of the 22nd of June, Imperium forces (Formerly CFC) camped the space lanes leading to the Amarr system in Domain. For the 3 day period, no Freighter or Industrial were safe traveling to and around Amarr. Though the event officially ended, remnants may still linger, travelers are advised to exercise caution.

KBP7-G system, Providence region

 

Fighting continues over the system, as [NC] forces push to take the system and sever Northern Providence from Empire space. A battle occurred between [NC] and Providence Bloc over the final Infrastructure Hub timer, with Providence Bloc suffering defeat and losing the Infrastructure Hub. A full article covering the fight will be posted at a later date.

News: Northern Coalition(dot) Defeats Providence Bloc in KBP7-G

KBP7-G system, Providence region. On the 21st of June, 16:30 EVE Standard Time, Providence Bloc and Northern Coalition(dot) [NC] forces clashed over the Station's shield timer in the system, leading to Providence Bloc's defeat in a bloody and chaotic battle.

Providence Bloc brought a 171 pilot Ishtar Heavy Assault Cruiser fleet and reached the system first. The fleet quickly set up on the station, anchoring Mobile Warp Disruptors (Referred to as 'Bubbles') around the station. As it was doing this, a cynosural beacon was lit at a perch above the station, and [NC] forces bridged in, a 100 pilot Loki Strategic Cruiser fleet.

Providence Bloc managed to put an interdiction probe in time between the station and the [NC] fleet, thus forcing it to re-position on a different perch before attempting to land on the Providence Bloc fleet. By that time though, the bubbles were online, and the [NC] force was dragged by them quite a distance from the Providence Bloc fleet.

The Providence Bloc fleet quickly anchored on the station, orbiting it at zero. This was done as a precaution against Bombers, as both [NC] and Bombers Bar have been quite active with their Stealth Bomber wings in the past. With [NC] landing in the bubbles, Providence Bloc deployed sentry drones and the two forces engaged each other. 

The fighting itself proved to be fierce, with both sides exchanging losses as the two fleets brawled each other at close range. 

Early in the battle, Providence Bloc managed to destroy the Logistics anchor for [NC], which led to its Logistics being disorganized and too far from the main fleet. This was taken advantage of by Providence Bloc, focusing its firepower on the Strategic Cruisers. One by one Lokis and Legions were volleyed off by the Providence Bloc sentry drones, the [NC] fleet suffering several losses before their Logistics could catch up.

However, for each Strategic Cruiser Providence Bloc took down, it lost a few Ishtars. As [NC] bridged in reinforcements and the damage output of the fleet dwindled due to decreasing numbers, it became apparent it was time to retreat.

The Providence Bloc ships quickly burnt out of the bubbles and warped to the XHQ-7V gate, jumping out and re-grouping on the other side. [NC] for its part refused to give chase, choosing instead to bring in 25 Super Carriers to push the station into its second reinforcement timer.

Having lost the strategic objective, Providence Bloc performed an orderly retreat, reaching its staging system unmolested. There, its fleet disbanded. Once the station was reinforced again, [NC] safely extracted its forces form the system, putting an end to large scale hostilities in region.

The Battle from Northern Coalition(dot)'s PoV

Battle report for the KBP7-G system can be found here.

All told, the system held less than 300 pilots at the peak of the fighting, with Time Dilation noted, but having no impact on the fighting. From start to end, the battle lasted nearly 20 minutes.

Providence Bloc lost 96 ships, 54 of which were Ishtars, for a total of 14.9 Bil ISK damage. [NC] lost 14 ships, 9 of which were Strategic Cruisers, for a total of 6 Bil ISK damage.

Providence Bloc lost both the field and the strategic objective, with KBP7-G seemingly poised to fall to [NC]'s hands in a few days. Whether Providence Bloc is able to snatch a last minute victory or suffer another painful defeat, remains to be seen.

News: Providence Bloc Loses Infrastructure Hub Timer in KBP7-G

KBP7-G system, Providence region. On the 20th of June, 18:00 EVE Standard Time, forces belonging to Providence Bloc clashed with Northern Coalition(dot) [NC] over the first reinforcement timer of the Infrastructure Hub, only to see defeat.

The KBP7-G system serves as the last link between High Security space and the Providence region, especially for the North of Providence. [NC] had taken 2 of the Empire exists to the region and deployed Sovereignty Blockade Units in KBP7-G in an attempt to sever that connection as well, using their Super Capital fleet to reinforce infrastructure. Regardless, Providence Bloc attempted to mount a defense of the Infrastructure Hub.

Providence Bloc brought 141 pilots mainly in Ishtar Heavy Assault Cruisers. The force managed to make its way to the system unmolested and sat on the Infrastructure Hub, waiting for it to exit reinforced mode.

Just as Providence Bloc was settling in, a cynosural beacon was lit at the edge of the grid and in came a 90 pilot Loki Strategic Cruiser fleet, belonging to [NC]. Providence Bloc quickly aligned to the beacon and warped at range, dropping sentry drones and attempting to volley off ships before the [NC] fleet could organize.

Providence Bloc managed to score a few kills, but due to an anchoring mistake, burnt too close to the Lokis. This put the fleet in range of the Lokis' guns, causing Ishtars to quickly evaporate as the Lokis rained artillery fire on them.

Realizing the mistake, Providence Bloc quickly retreated from the field, warping to a perch above the B-WPLZ gate. However, [NC] followed it, landing on top of the fleet and quickly decimating ships left and right. 

Providence Bloc attempted to burn away and quickly docked up, losing more ships in the process. This allowed [NC] to push the Infrastructure Hub into its second reinforcement timer with no opposition.

With this, large scale hostilities in the system came to an end.

Battle report for the KBP7-G system can be found here.

All told the system saw less than 300 pilots during the fight, with Time Dilation not reported as an issue. From start to end the battle lasted 15 minutes.

Providence Bloc lost 36 ships, including 18 Ishtars, for a total of 5.9 Bil ISK damage. [NC] in comparison, lost only 3 ships, 2 of which were Logistics ships, for a total of 0.5 Bil ISK damage.

There is still debate whether [NC]'s ability to pounce on Providence Bloc was due to a lucky probe hit, or their scouts bookmarking a mobile depot one of the Providence Bloc fleet members dropped. 

Regardless, many believe [NC] would have reinforced the Infrastructure Hub anyways.

How things develop in the KBP7-G system is up to anyone's guess, but the EVE Scribe will keep you posted on the developments.

News: Providence Bloc and Northern Coalition(dot) Clash in 4B-NQN

4B-NQN system, Providence region. On the17th of June, at 21:00 EVE Standard Time, Providence Bloc forces clashed with Northern Coalition(dot) [NC], suffering a minor defeat while gaining a strategic victory.

[NC] in its usual fashion, attempted to provoke a fight from Providence Bloc by deploying Sovereignty Blockade Units, this time in the 4B-NQN system. Providence Bloc responded by bringing a 130 pilot Naga Battlecruiser fleet to the system.

[NC] brought a 60 pilot Loki Strategic Cruiser fleet with Triage Carrier support. The fleet parked on the 9UY4-H gate in the 4B-NQN system. Providence Bloc attempted to fight the [NC] fleet, jumping into it and quickly anchoring around the gate. However, the Triage support of [NC] was on the ball and kept most of the Lokis alive. Quickly losing ships and unable to break any of the Lokis' tank, Providence Bloc retreated from the gate.

At the same time, another Providence Bloc fleet was working on destroying one of the Sovereignty Blockade Units on the other gate. A 30 pilot assorted Cruiser fleet was diligently putting damage on it while the main fleet entertained the [NC] forces.

With the main fleet retreating, the Providence Bloc Stealth Bomber wing kept the [NC] forces at bay. The main fleet linked with the Cruiser force and quickly took down the Sovereignty Blockade Unit, thus securing the system. [NC] forces at the same time jumped into the 9UY4-H system, leaving behind their Triage Carriers.

Click for Killmail

Providence Bloc took the opportunity and quickly warped to the 9UY4-H gate. Once landed, the main fleet anchored up and quickly blasted the first Triage Archon Carrier, who melted fast before finally exploding. Encouraged by their success, the force shot the second Archon, who promptly entered Triage mode, thus tanking the incoming damage just as it dipped into low armor.

Click for Killmail

[NC] forces jumped back into the system, adding their fire while lighting a cynosural beacon to bring more Triage Carriers. Providence Bloc attempted to fight a bit longer, but it became clear they could not break the Triage Carriers or the Lokis' tank and the order was given to retreat.

After managing to get a fight from Providence Bloc, [NC] forces did not try to pursue further and safely extracted, allowing Providence Bloc to take down the remaining Sovereignty Blockade Unit later on.

Footage of the Fighting from Providence Bloc's PoV, Courtesy of Mangraa Dementia

Battle report for the 4B-NQN system can be found here.

During the peak of the battle, the system hosted around 250 pilots, with Time Dilation not being a noticeable issue. The battle from start to finish lasted 50 minutes.

Providence Bloc suffered the majority of the losses, with 51 Battlecruisers lost for an estimated 8 Bil ISK damage. [NC] lost only 1 Loki and 1 Triage Carrier, resulting in 4 Bil ISK damage.

While small scale hostilities continue in the Providence region, it seems that the conflict has ebbed away once more, resulting in only the occasional battle. Whether this is a sign of [NC] finally tiring from the region or merely the calm before the storm, is yet to be seen. The EVE Scribe will keep you posted.

Special thanks to corebloodbrothers, of Volition Cult, The Volition Cult for giving an interview, Mangraa Dementia, of Blue Tridents, Sev3rance, for supplying the video footage and ISD for providing the screenshots

News: Burn Amarr Confirmed, Date Set

Burn Amarr has been confirmed and is scheduled to go ahead from the 19th of June onwards, according to unnamed sources. The event will see GoonSwarm Federation [CONDI] and their allies using disposable ships in order to suicide gank ships in the Amarr system, Domain region.

Unlike the usual suicide gank which is after high value ships and cargo, this event will see ships targeted regardless of cost. Since the Amarr system is one of the busiest trade hubs in New Eden, the operation is certain to disrupt logistics across the region, as well as the South and South-East of New Eden, as the hub is used to supply these regions with the equipment and materials needed to maintain fleets.

This event is considered a precursor to the Imperium's invasion of the Providence region in order to uproot loyalists of the so-called False Empress. Pilots flying under the banner of Providence Bloc are advised to use alternative trade hubs and avoid the Amarr system entirely as long as the event continues. Stocking on ships and equipment before the event starts is recommended as well.

Below is the post released by [CONDI] leadership:

BURN AMARR STARTS 19TH JUNE

  

A Life's Work, Ending Lives

The Ministry of Love was founded three years ago, just after the original Burn Jita, an event so inspiring and powerful that it spawned a renewed and powerful passion for suicide ganking, well beyond that of past jihadfleets or ice interdictions or Hulkageddons. Each year, we've gotten cheaper and better at grinding Jita's freighter and jump freighter traffic to an utter and unequivocal halt - as evidenced by the following destruction figures:

- Burn Jita Classic: 518.47 billion ISK all up

- Burn Jita 2: 578.35 billion ISK all up

- Burn Jita 2014: 586.7 billion ISK in freighters, jump freighters, and Orcas alone.

And now, as the Imperium, we turn our eyes to that other trade hub, home of the false Empress (no, not the crappy 0.5 hub that would be a sheer joke to interdict). The Imperium will not tolerate heresy, and it is our duty to purge all unbelieving and unrepentant fools that choose to inhabit or otherwise utilize this apostate bed of false idols. And, with Amarr burned to the ground, we will move on to the next great victory - Providence, where Unbeliever moneychangers toil and hoard their measly specks of property.

Preparation for the Second Coming

The God-Emperor needs you ready to spread his wrath. Take careful heed to these directions (seriously read this shit it's really crucial to our success).

 -Staging, Security, and Other Preparation-

Staging: Our fleets will be running out of Amarr VIII (music) - Moon 4 - Expert Distribution Retail Center. Ensure that you have a jump clone at that station far in advance of the 19th, and ensure that you set your medical clone there before you begin spreading the Word. (This is crucial - you will get podded. Non-implanted clones are welcomed and advised).

Security Status: I give not one half a flying fuck what your security status is. Miniluv has, in the past year, adapted to leading fleets composed mainly of -10 security status pilots. If you feel you need the shield of a good security status, feel free - but leaving because "oh my sec is too low" will not be a thing.

Other Prep - Skill Training: Extremely important - ensure that you train this brief skillplan IMMEDIATELY in order to participate in Burn Amarr

Other Prep - Overview: Download this overview pack and put it into your c:/Users/{username}/My Documents/EVE/overview folder. You will want to import it and activate it before Burn Amarr.

Other Prep - Instadock bookmarks: If you warp to the staging station at 0 normally, you will die - trust me. While you are setting up your medclone/jump clone, undock from the staging station, and make a bookmark where you are in space - name it Burn Amarr Staging Instadock. When you need to get into the staging station, warp to that bookmark instead of the actual staging station, then manually dock.

-Date/Time-

We will be running from June 19th (Friday) after downtime (1100) to downtime on June 22nd (Monday), or, more likely, until we run out of Catalysts.

-Ships and Training (*important*)*-

You will be provided as many Catalysts as you can use, free of charge. The Ministry of Love, my SIG and the premier highsec ganking entity in all of EVE Online, has prepared over 15,000 fitted Catalysts for your use.

Extremely important - ensure that you train this brief skillplan IMMEDIATELY in order to participate in Burn Amarr

You are welcome to bring your own stock of ships! We recommend any of the following:

- T1 or T2 blaster Catalyst

- T1 or T2 autocannon Thrasher

- T1 artillery Thrasher

- Coercers of any flavor (because Amarr supremacy - watch out though, faction crystal cost per suicide is somewhat prohibitive)

- T1 artillery Tornados for the extra-rich

Fits for some of these can be found on the extremely helpful Miniluv wiki link).)

Reimbursement is:

Reimbursement for Burn Jita Amarr is posted to the affordable care app.  Reimbursement for GSF is as follows:

- Catalyst: 10mil

- Brutix: 50mil

- Tornado: 60mil

- Talos: 85mil

Given the fact that we are handing out 15,000 catalysts for FREE, yes, you can get paid for showing up and shooting bads.

 

Support Roles and a Call for FCs-

As with every year, Ministers and non-Ministers alike playing support roles are key to the success of any Burn event. We ask you to consider providing the following support:

Handing out ships: We have more than 15,000 hulls that will need handing out over the Burn Amarr weekend. A single player can only hold about 1000 per hangar. Ya dig? SP requirement: None

Cargo/ship scanning: We would like to know what cargo we're ganking and what fits our victims have - that's where you come in. Recommended scanner fit here. SP requirement: 1-day train's worth of SP Requires non-wardecced, non-killright character

Bumping: Just what it sounds like. Grab a Typhoon, Panther, Machariel, or whatever suits your fancy, and knock some freighters around until we're able to nail them. SP requirement: Small, 20-day train Requires non-wardecced, non-killright character

Hauling: Grab a Deep Space Transport (sample fit here), get a ton of Mobile Tractor Units, and help us scoop delicious loot. SP requirement: Small, 20-day train Requires non-wardecced, non-killright character

FCs: If you know it, you can do it. If you can do it, we need your support. RSVP with me and let me know when you can do fleets (CLEAR YOUR CALENDAR). SP requirement: butt

Intricacies of Amarr's Geography

Amarr is a trade hub, but it's also a transport hub - there is a lot of movement out to a lot of more minor local hubs that goes through Amarr. Jita, by comparison, is where EVERYTHING flows to. That means that Amarr will provide for interesting route interdiction.

On Amarr's security: the 1.0 CONCORD response is very much like the 0.9 Jita CONCORD response. Dunna' worry.

On "lawd the Goons is dead can't even burn jita:" Really, Goons and the Imperium put out more actually fun events like this one than anyone else in EVE Online. If we are dead, then we are dying laughing.

That's it. Get ready. Fuck 'em up.

Providence Bloc leadership responded to the news with the following link: You are Provibloc