+-+-

+-User

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?

+-Stats

Members
Total Members: 281
Latest: [FUN] JPS-1
New This Month: 0
New This Week: 0
New Today: 0
Stats
Total Posts: 22224
Total Topics: 7142
Most Online Today: 90
Most Online Ever: 249
(November 01, 2009, 02:50:51 am)
Users Online
Members: 0
Guests: 99
Total: 99

My brain was equipped with the following implants

Started by CCP, October 21, 2011, 05:44:03 pm

« previous - next »

0 Members and 1 Guest are viewing this topic.

CCP

My brain was equipped with the following implants
20 October 2011, 3:30 pm

 Killmails are great.  They serve as reminders of good fights (or dubious mistakes).  They let you measure losses inflicted on your enemy in cold hard ISK.  They also demonstrate some interesting choices in ship fitting, or cargo-movement attempts.  If you're so inclined, they provide a way to track your kill/death ratio, and measure it against your peers.  I especially like the ones where a pod gets squished.  But I’ve always felt that those pod-mails were missing a certain... something.

In the forthcoming Winter expansion, we’re adding a much-requested piece of additional information to capsule killmails:  They will now list the fitted implants of the unfortunate victim.



This poor pilot sure likes his implants, even if his mix-and-match style is a little worrying!

I’m keeping this short and sweet, as I want to get the information out early to the third-party developers.  That way, they can make sure your killboards will be ready to start counting up those Slave sets as soon as this goes live!

If you’re a killboard or application developer, you’ll want to pay attention to how the implant list is going to appear.  For killmails copied from the client, the format will be similar to the destroyed items list for regular ship killmails.  Each implant will be listed under the Destroyed items: section, with an (Implant) marker (similar to how some items in a ship kill have a (Cargo) or (Drone Bay) marker now).  This is to enable a clear distinction between implants carried as cargo in a ship, and implants fitted to a capsule’s pilot.

For killmails obtained via the API, destroyed items have a flag attribute, showing their location prior to destruction.  Currently this can be 5 (Cargo) or 87 (Drone Bay).  Fitted implants will have a flag of 89.

This change should be released on to the Singularity test server sometime next week, so that you can start generating some test mails for your tools.

I look forward to seeing how this new information starts showing up in the battle reports.

Fly safe.  And remember, don’t plug in what you can’t afford to lose.

CCP Masterplan

????????? ???? ???? ?? ??????? ????? Diesen Blog auf Deutsch lesen

 

New to EVE? Start your 14-day free trial today.

Returning pilot? Visit Account Management for the latest offers and promotions.



Source: eveonline.com | devBlog

[FUN] Hanius Valm

Finally, now people will really start loosing the rag at whoever fires on the pod before everyone is on it, especially if its a plus 4 implanted one  :D
array(6) { [0]=> array(3) { ["file"]=> string(48) "/home/ugvdmln/freelancerunion/Sources/Errors.php" ["line"]=> int(290) ["function"]=> string(9) "log_error" } [1]=> array(3) { ["file"]=> string(74) "/home/ugvdmln/freelancerunion/Themes/Lunarfall_v0.6.5/Display.template.php" ["line"]=> int(941) ["function"]=> string(17) "smf_error_handler" } [2]=> array(3) { ["file"]=> string(74) "/home/ugvdmln/freelancerunion/Themes/Lunarfall_v0.6.5/Display.template.php" ["line"]=> int(280) ["function"]=> string(20) "template_single_post" } [3]=> array(3) { ["file"]=> string(46) "/home/ugvdmln/freelancerunion/Sources/Load.php" ["line"]=> int(2498) ["function"]=> string(13) "template_main" } [4]=> array(3) { ["file"]=> string(46) "/home/ugvdmln/freelancerunion/Sources/Subs.php" ["line"]=> int(3279) ["function"]=> string(15) "loadSubTemplate" } [5]=> array(3) { ["file"]=> string(39) "/home/ugvdmln/freelancerunion/index.php" ["line"]=> int(154) ["function"]=> string(6) "obExit" } } Error loop.