Pilots who had been waiting in the wings now ship up and start warping to the grid… the fight becomes intense. Warping, I drop the bubble and comms became frantic. add Devoter!” I shout into the mic, decloaking just as they appear on grid with my Director. I immediately start smashing D-Scan again. I sat silently, the plan requiring me to wait for the Nestors we knew would come and then decloak to warp on zero. as an Alpha in a Caracal for a couple of months, but my hard work has paid out in the form of skill injectors and today, today I was flying a Flycatcher. Then, as I’m day-dreaming about cans of Intact Armor Plates, RedHand shouts, “Hello, Proteus!”. It was taking forever… and the time kept on ticking. We are a wormhole corporation, and everyone has some level of scanning under their belts, except our Jimmy. The timer I had set to monitor that Static’s end of life slowly ticks down and Jimmy has been chosen to hack the cans, which will spawn the second wave. The conversation on comms revolves around nothing else. The prey can’t possibly be so stupid as to fall for this, not with everything that’s happened in the last two weeks. Me though? I’m thinking about those cans going unlooted. Director RedHand has just landed after fetching more missiles from the Fortizar and the corporation waits, restless for the prey. My gaze shifted back to the direction scanner in my Flycatcher class Destroyer and then beyond to the Golem, now made minuscule by 150kms of distance. Beyond it waited a fortune in Relic and Data sites. By this time only three hours remained on the life of our C4 Static.
#Zkillboard redhand cracked#
I cracked my knuckles and stare again at the corporate intel channel. I formed up inside the Fortizar and we carefully executed “the plan”. As I came in my sensors registered our C4 static as end of life. Pings went out, plans were cemented and I was called in from the field. Charrette, the officer, started hunting down our guest’s perch and managed to decloak one of his scouting ships. I was several systems away and we didn’t have the members to deal with it so I went about my business. I had been running pirate exploration sites, as I usually do, when one of my officers called out on comms that he had been dropped by the Cloaky Bastard only moments ago and managed to escape.
Today, our guest’s welcome has officially come to an end. The Cloaky Bastard had clearly decided that he was going to hunt us down in our home system, one by one. People were on edge after we all read the article, but I just shrugged it off. by the perpetrator.Įveryone had been planning and discussing how and if we were going to deal with this. What was new this time though was the intel which came in from a friendly alliance who also resided in wormhole space. Word around the Fortizar was that it had happened before (and would again). It wasn’t entirely a new thing for Apotheosis when one of our members lost a Paladin. The corporation has been on high alert the last two weeks. allianceID: The alliance name for which you would like to be notified of kills.DATE: 2017.01.06 22:00 LOCATION: J130343 W-Space.corpID: The corporation name for which you would like to be notified of kills.
#Zkillboard redhand how to#
Info on how to make a Discord webhook can be found here: Intro to Discord Webhooks.discordHookToken: The Discord Webhook Token.queueID: A unique identifier for your Zkill RedisQ, so that you do not get duplicate or miss kills.There are very rarely failures due malformed or irregular Zkill data, so if you are running this on a server indefinitely, consider running this using a node process manager such as pm2.node node/index.js This will run infinitely until it is stopped or fails.
#Zkillboard redhand update#
Update the configuration file specific to your needs (see Config and Environment Variables).Navigate into the cloned directory cd zkill-to-discord.Updated from Crest to ESI formatted kills.Post kills from Zkillboard's RedisQ to Discord
0 kommentar(er)
