Altering course:
In the beginning of this blog, I stated that I was going to do this hard mode. NPC stations in high sec and no real outside help. Well that was a fun exercise. Next?
Just a note: I have been up for greater than 24 hours at this point, so the stream of thought is tending to sputter more than it should.
POSsibilities:
I went ahead and dropped a POS in a quiet 0.5 system last week. I got it all setup and moved most of my production there. It's more expensive to have Red Frog ship out to me now, and I still have to cover an additional 2 jumps to get it into my POS. I need to train a character into an Orca to make these last couple of jumps in as few trips as possible. I still have a couple of copy jobs etc. hanging around my old home.
So now I have all this possibility. I am training up a component builder/BPO researcher for my own library and to support my invention toons. This takes advantage of the ME/PE research slots I get for free, and allows me to increase profit margins without reducing ISK/hr of my inventors.
I have thought about a lot. I thought about buying all the parts that I would need to start building Orcas. But with an initial buy-in of 10-12 billion and profit under 10% for a very well researched BPO, it just didn't seem worth while to me.
All of these possibilities have left me needing better tools. I find myself spending more time writing tools than playing most nights anymore.
I also need to find more time to spend in Faction Warfare with my main. Until I have a steady income with minimal work, I am not seeing a lot of time for it though.
Tool Development:
Overview:
While the main focus of this blog is not on my tools, they are part of my decision making process. I have chosen to write these tools in Java for several reasons.
- Cross-platform:
- Java is "natively" a cross-platform language.
- I needed/wanted to learn it for work:
- I work as a sometimes programmer, and was looking to write a cross-platform data extraction/analysis tool.
- I wanted a language with better libraries than Perl or C/C++.
- Perl libraries tend to be a little more unpolished and hap hazard.
- C/C++ support for things like XML and JSON, in the freeware department, Are lacking or non existent.
- Yes I will take flack for this, but after working on a project and compiling all the libraries using mingw through a cygwin terminal (for unix like commands needed by the make files) and realizing that cygwin adds a dll dependancy to your executables.
- Free tools, like Window Builder.
Rapid Assembly:
This was my initial tool idea, but a lot more complex. Lots of options here, but when you boil them all down, the only tool currently with a GUI is my shopping list editor. Lots of options to dial in manufacturing and invention costs. Has some functions to make historical and other graphs.
One of the issues using this tool is that the database holding its blueprint information only holds the current SDE release, so you can not automatically see the cost of change of materials.
Profiteer:
Command line tool to generate statistical information for T1 manufacturing over a period of time. Output is in the form of csv's with product name/date.
Groups blueprints by general market groups. Can be used to filter down the list to a single market group. Depth of the market group into tree does not matter (i.e. both Ammo & Charges and Cruise Missiles are valid.)
Invention Profiteer:
Much like Profiteer, but adds in all the variations of the invention process. It cycles through all available decryptors and meta items for each T2 blueprint in the selected market group. I need to find some better ways of estimating true velocity. I tried entering the Large Remote Energy Transfer Array II market, and am still holding onto ~300-500 M stock in sales orders. On paper, this product looked very good, but the velocity is turning out to be very low.
killPuller:
This is an attempt to pull kill data from zkillboard.com. All of the kill data, along with some related price information is stuffed into a giant database. From the database I plan to get item destroyed data to help with making market decisions.
killAnalyzer:
This is a tool that I have not yet started working on. I will need to finish killPuller enough to reliably extracts the large dataset for me before I can start working on this. This will be the second GUI tool.
Below is a list of desired functionality:
- ALOD finder.
- Battle finder / reporter.
- Should be able to search the kill data and find large battles.
- Should be able to create different battle reports.
- A per side isk lost over time graph, to give an idea how the battle progressed.
- Summary statistics
- Damage done
- Damage taken
- Kills
- Losses
- Item statistics
- Isk lost (destroyed)
- Isk salvageable (dropped)
- Galaxy Map graphs of various statistics
- Items destroyed
- Kills
- Pod Kills
- Gate camps
Industrial Accountant:
I need to design a smart application to read in API data to find actual buy/sell prices on a unit by unit basis.
- Trace the material from purchase through industry jobs and finally into the sell orders.
- Categorize other purchases, both automagically and manually.
- Ability to graph data in various was
Conclusion:
I need to get busy :). Faction warfare, industrial warfare, and programming. Lots to do, lets see if I can find the time to do much of this.
No comments:
Post a Comment