Out of the spreadsheets and into the fire! I have always been interested in the ebbs and flows of power in nullsec and as such, I have a subcapital character in TEST for participation in the pony giggles.
I saw a Jabber announcement go out for a fleet that worked perfectly for me — after US dinner, before bed.
A lot of firsts happened on this fleet. It was my first official non-kitchen sink/random home defense subcapital fleet, the maiden voyage of my T2 Alpha Maelstrom (finally have Large Projectile Turret V), first time using optimized overview settings, and my first nullsec final blow.
(don’t laugh all you PVP’ers — I’m going to try to do a battle report)
Alpha > Scimitar > Huginn formup in Fountain. 140 in fleet mainly consisting of a Maelstromball with fast tackle support that headed into Delve. We encountered and played catch-up/evade/backtrack with a Nulli Secunda AHAC/T3/Dictor gang of about 100. Now blue’d Pandemic Legion joined us on a few jumps as we played around with the Nulli Secunda gang.
Three major encounters resulted in us blapping their ships as they came through gates while being tailed.
Once we jumped through, our Alpha Maelstroms pulsed MWDs and sat at optimal using Depleted Uranium L (1.2x tracking) ammo while fast tackle stayed on gate to lock down targets.
After a few T3s, some Guardians, and all their Dictor were down, they retreated home while we reinforced a few structures with the help of PL.
This was also my first time using Liberty Prime’s UI Generator settings and I have to say, their standard theme is quite nice.
I was easily able to flip between friendly/hostile/warp points and the color highlighting really helped when identifying targets. I recommend trying this theme out if you have any issues with your current Overview setup.
So watch out, this industrialist is growing teeth!
Test builds are being deployed. I will attempt to keep a master list here so bookmark and refresh this post.
Patch Notes [link]
Patch Size: ~1.04 GB
Game of Drones:
Revamped the Inventory:
– Managing corporation items in a station
– All item management from POS structures done in space on grid
– All Inventory management in space (wrecks, opening other ship locations, etc)
– All Inventory management in stations (items, ships)
– This change does NOT affect the ASSETS window
– LP for kills
– Bunkers are now infrastructure hubs
– LP for all FW actions (capturing complexes, capturing infrastructures hubs, etc)
– New FW front page
– Consequences for capturing systems/regions (benefits for you, grief for your enemy)
– Capturing FW system affect SOV ownership
– Map filters for FW have been revamped
• New missile launchers and launch effects
• New missiles, trails and explosions
• New Stealth Bombers
• Amarr V3
o All sub capital Amarr ships, excluding T3 cruisers.
“14 different skintypes have been added to the Character Creator. This allows all bloodlines to have a wide range of skincolors.
These skintypes replace the previous skintones that allowed players to modify their skincolor a little bit.
A character can keep his/her current skintone, but as soon as a skintype has been applied and the character saved, one of the new skintypes has to be used.
The skintypes can only be applied with full recustomization, that is when you also have the option to resculpt your character, but the plan is to give everyone an optional full recustomization when this goes on TQ.”
• Updated Kill Reports (aka Kill Mails)
• Different war cost
• Corp CEO/Director declares wars, no voting required
• Alliance wars transfer to corps leaving
• No automatic war retraction by aggressor
• Wars last for week by default
• Either side can offer surrender in a war
• The defending side can get allies to help
• There is a place for people to find prospective allies/clients
• Players can now more easily track the war in the War Report
• All corps have publicly viewable war history
• Drone Damage module (Extrinsic Damage Amplifier)
• CPU Rigs (Small/Medium/Large Processor Overclocking Unit)
• Fueled Shield booster (Small/Medium/Large Ancillary Shield Booster), using Cap Boosters as charges
• Light and Medium Web drones
• Resistance shifting armor hardener (Armor Adaptive Hardener)
1. Frigate Rebalance [link]
Tormentor, Punisher, Merlin, Incursus, and Rifter changes.
2. New Modules
From Soundwave’s presentation at Fanfest, it sounded like the following modules are going to be included in Inferno. So far we only have this slide from FanFest and a long forum posts. [44:24]
Micro Jump Drive — Perhaps soon:
Drone Damage module (Extrinsic Damage Amplifier)
CPU Rigs (Small/Medium/Large Processor Overclocking Unit)
Fueled Shield booster (Small/Medium/Large Ancillary Shield Booster), using Cap Boosters as charges
Light and Medium Web drones
Resistance shifting armor hardener (Armor Adaptive Hardener)
3. Missile Effects [link]
Youtube video starting at 3:30.
4. Missile Launchers [link]
For a while, we’ve been talking about global killboards and all the awesome stuff that comes with it (leaderboards, weekly contests etc). Linking killmails in chat to other players means that you’ll effectively have access to that data, making our global killboard project slightly problematic. That, coupled with some security concerns means that we’ll have to withdraw linking killmails ingame.
Just to make it clear, we’re not pulling this feature because we don’t want you linking killmails, we’re pulling it because we have concerns about the impact on our global killboard project and making this massive amount of data available in a more graceful manner in terms of security etc.
6. Unified Inventory UI [devblog]
7. Amarr v3 Ship Updates [preview youtube]
8. Updated Ship Models
[unofficial renders on youtube]
Overview Fading [link] Included in Escalation
10. War Mechanic Updates [devblog]
11. FW Changes [devblog]
Without going into exhaustive detail:
1. Cannot dock in stations that are in systems controlled by an enemy
– Example: Minmatar cannot dock in stations in a FW system controlled by the Amarr/Caldari
– You also cannot use station services if you docked before system flipped
– Ninja Edit: This does not affect neutrals
2. There are 5 levels of discounts for a number of different things – if you own the system and have upgraded it
– Medical clone discounts (from 10% in increments of 10 up to 50% discount)
– Number of assembly lines increases by 1 for every level
– All broker fees discounted (from 10% in increments of 10 up to 50%)
– NOTE: You only get these discounts in the FW system
– ADDENDUM: These discounts apply to neutrals not in FW
3. Militia store LP prices are affected by faction wide performance (discounts in increments of 10%)
– Note that Datacores have been split and moved in FW LP stores
– Pending implementation, LP gain increase for all ways in which LP can be gained in FW – FW Kills, FW Missions, Complexs etc
12. War Costs
1. Drake Rebalance
2. Titan Rebalance
3. Technetium Rebalance
1. Destroyer and Battlecruiser Skill Rebalance
There will be no skill change for Inferno. Your destroyer and battlecruiser skills are safe for now. Battlecruisers will have to wait until we have rebalanced frigates and destroyers to have something clean to compare them with.
CCP Ytterbium link
2. Armor and Shield Rig Rebalance [link]
In conclusion, this is just too much controversial / poorly thought to be a first step to anything, we need to take a step back, breathe, and have a look at the whole passive versus active tanking situation through modules and ships as well as changing rigs before committing to more changes.
CCP Ytterbium link
The Inferno market is open and with it comes the addition of Faction/Deadspace/Officer items. I expect module prices to mimic Faction ship prices and slowly go down as more traders enter the market and the 0.01 war begins.
Here are some early predictions.
CN Invuls will go down in price due to competition and the desire for the recently added higher Meta Deadspace variants. In January these were trading at 524M.
We’re going to see the sheer scale of some module empires now that we have increased visibility into the market. For example there is a 34.89 B order up @ 66.979 M for Republic Fleet Gyros.
I expect common Faction items like Sisters Expanded Launders to drop in price and then rise as people manipulate this high volume item.
This is a great time to be a trader and I expect the market to reach an initial stable period in a few weeks as existing contracts expire.
The Procyon Holdings (PROHD) name is expanding again as we push out into another development area — the Android framework. When I abandoned my BlackBerry, the choice to move to the Android platform was an easy decision. Market saturation, the development community, and fluidity between devices make this platform shine.
I’ve been having a few end user problems with the current iteration of our trading website. First, the native Android Gingerbread browser lacks SVG support, an issue that has bewildered me since I read about it. I can solve this issue by using another browser such as Opera, but I would like to use the native one.
Also working with a HTML + Ajax website on a device with a touch interface feels like you are not getting the full user experience. I want to scroll down lists with my finder, click and hold to expose options, and speed around menus.
We had to expand our design and create a few new pieces to get data to the mobile world. New items include the creation of a daemon to simply database population, exposing data via XML, and working with an existing library to enable Push notifications.
Our previous design was that you would have to hit the transactions webpage and it would trigger an update. Getting a page to refresh on a desktop connected via broadband versus a mobile phone is quite the different experience.
Android has a framework called C2DM (Android Cloud to Device Messaging) which enables you to send lightweight push notifications to devices.
Our vision is that when a sell order clears, a large/special sale has occurred, or a significant milestone has been reached, we send a notice. This will be visible on phone’s Status Notification Bar and cause me to act if deemed important. I have been forgetting to buy or trade a particular item after the sell orders have cleared. Forget things — lose profit.
Getting data out of our database required the creation of a webservice to produce XML output from our wallet table.
Here is an example of the sale of one item in our XML feed:
<?xml version="1.0"?> <TransactionList> <Transaction> <transactionDateTime>2012-04-19 06:21:04</transactionDateTime> <typeID>21096</typeID> <typeName>Cynosural Field Generator I</typeName> <quantity>1</quantity> <price>1948939.91</price> <profit>147803</profit> <stationName>STATION</stationName> <icon>21096_32.png</icon> </Transaction> </TransactionList>
This screenshot is our first proof of concept. We’re able to get information from an XML feed, display it, and get/cache images from the Eve image server. Major credit goes to my trading and corporation partner James, who has been doing the development work and educating me on the Android framework.
There is a lot we want to do with the mobile version. Menus, tabs, charts, reports, and the ability to add items to a shopping cart/wish list are all things on the drawing board.
This project is our first exposure to the Android framework and after the initial learning curve, we might perhaps coolabrate with the Aideron Robotics team on Aura. So maybe some of our trading mechanics will make their way into the Aura application.
More Power to the People
The propose of this short guide is to empower a person that has limited or no experience working with the Eve dataset to perform queries and extract useful information.
Eve has two main data sets. The first is the static data that is published by CCP and updated with each expansion. This set contains information that doesn’t change such as stargate coordinates, number of Moons in VFK-IV, type of research agents in the Forge, or the minerals requirements for a Drake.
The other set is the dynamic data, which is exposed through the API. This data contains the types of assets you own, wallet transactions, or kill statics for a particular system — things that change and things that go boom.
More Data, More Problems
With every new release, CCP publishes a Microsoft SQL database backup file of their static data. You can find the most up to date file on the Community Toolkit website.
Along with the database backup, you will find other useful downloads such as images for every item in Eve — very important when trying to create something presentable out of boring database tables if you are designing a 3rd Party application.
Some people do not use Microsoft SQL and opt to run their database with MySQL, the most popular opensource database package. This format is not released by CCP and thus enterprising players routinely convert the data from Microsoft SQL to MySQL format. Nothing is lost, just converted.
Usually a few hours after a new file has been posted on the Community Toolkit site, people have conversions up for download. If you hang out in the Eve Technology Lab sub-forum, people will usually post links once available. I have been getting my releases from this site: http://zofu.no-ip.de/.
Noise. has written an excellent guide on how to install the free version of Microsoft SQL Server and work with CCP’s database backup file in order to get to a point where you can run a database query.
Table Prefix Nomenclature
The naming format of the tables is very intuitive and can be picked up fairly quickly.
|agt||all about agents both mission and research|
|chr||character information such as bloodlines, factions, and races|
|crp||NPC corporation divisions|
|dmg||damage attributes, effects, dogma (attribute system)|
|eve||basic information for icons and units|
|inv||market groups, item details, item reactions. I do a lot of work with these tables|
|map||xyz data, landmarks, regions, solar systems connections, and general universe data|
|planet||planetary interaction schematics|
|ram||industry, manufacturing, refine|
|sta||station services, xyz docking locations|
Tips and Tricks
An item’s typeID is a very important thing to know. This is a unique number that identifies a type of object in Eve.
Keep in mind that referring to a Drake (typeID 24698 in the static dataset) will be different than referring to your Drake (unique itemID 1002615059065 in the API feed). The itemID value is a unique number that identifies every object in Eve (1).
Eve Queries 101
SELECT * FROM [dbo].[invTypes] WHERE typeID = 24698 GO
List all Battlecruisers
SELECT * FROM [dbo].[invTypes] WHERE groupID = 419 GO
Eve Queries 201
PI Schematics are contained in the planetSchematicsTypeMap self referencing table. This means that the build requirements for P0, P1, P2, and P3 are all contained in one table. The isInput column is used to list build requirements when set to 1.
1. Listing all P0 items using the isInput value set to 0.
SELECT planetSchematicsTypeMap.*, invTypes.typeName FROM planetSchematicsTypeMap JOIN invTypes ON (planetSchematicsTypeMap.typeID = invTypes.typeID) WHERE planetSchematicsTypeMap.isInput = 0 AND invTypes.marketGroupID = 1335 ORDER BY invTypes.typeName
2. Listing items that go into Construction Blocks, a P1 with typeID 3828 and schematicID 74.
SELECT planetSchematicsTypeMap.*, invTypes.typeName FROM planetSchematicsTypeMap, invTypes WHERE planetSchematicsTypeMap.typeID = invTypes.typeID AND schematicID = 74 AND isInput = 1
Eve Queries 301
CCP’s dataset does not contain a table with Tech2 build requirements. We have to create a new table that combines information from a number of tables and then work off the new table.
1. Run this pastebin query once to create your new typeBuildReqs table. If successful, you will get a message like this:
(15791 row(s) affected).
2. Find the build requirements for a Cap Recharge II with input typeID of 2033 (Cap Recharge II Blueprint). The NOT IN statement excludes the skills required to build the item.
SELECT typeBuildReqs.*, invTypes.typeID, invTypes.typeName FROM typeBuildReqs JOIN invTypes ON (invTypes.typeID = typeBuildReqs.requiredTypeID) WHERE typeBuildReqs.typeID = 2033 AND invTypes.groupID NOT IN (268,269,270) AND activityID = 1
If you want some more example queries, comment or find me on twitter.
(1) If you remember that old Devblog post about Drake missile lag, one major component to the lag was that every missile fired had to have a unique itemID created and destroyed after it exploded. This database operation ate up a lot of time, which is critical to a simulation trying to play through a battle.