Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ship browser does not distinguish between Tech 1 and Tech 2 ship bonuses. #76

Closed
lps1975 opened this issue Sep 2, 2018 · 2 comments
Closed

Comments

@lps1975
Copy link

lps1975 commented Sep 2, 2018

For most of it's life, the EveMon ship browser would distinguish the difference between a ship's basic skill bonuses and the "advanced" bonuses (for lack of a better term) for the Tech 2 aspects of the ship.

For example, before this bug, the Golem (Caldari battleship) would be described as follows. (Important note: there are three skill categories, indicated with ---

--- Caldari Battleship bonuses (per skill level): ---
10% bonus to Cruise Missile and Torpedo max velocity
5% bonus to Cruise Missile and Torpedo explosion velocity
--- Marauders bonuses (per skill level): ---
7.5% bonus to Shield Booster amount
10% bonus to Target Painter effectiveness
--- Role Bonus: ---
100% bonus to Heavy Missile, Cruise Missile and Torpedo damage
100% bonus to Tractor Beam range and velocity
70% reduction in Micro Jump Drive reactivation delay
• Can fit Bastion modules

Unfortunately, at some point in the recent past, EveMon now collapses the first two categories together. It is now more difficult to understand what bonuses come from where:

--- Traits --- 
Golem bonuses (per skill level):
10% bonus to Cruise Missile and Torpedo max velocity
5% bonus to Cruise Missile and Torpedo explosion velocity
7.5% bonus to Shield Booster amount
10% bonus to Target Painter effectiveness

Role bonus:
100% bonus to Heavy Missile, Cruise Missile and Torpedo damage
100% bonus to Tractor Beam range and velocity
70% reduction in Micro Jump Drive reactivation delay
Can fit Bastion modules
@peterhaneve
Copy link
Owner

This bug existed from before the ESI conversion according to evemondevteam#88

peterhaneve added a commit that referenced this issue Sep 3, 2018
While this made few meaningful changes to the data, issue #76 is fixed, without even requiring a version up.
@lps1975
Copy link
Author

lps1975 commented Sep 4, 2018

So am I to understand that you are not necessarily taking over the maintenance and development of EveMon, correct? You are only doing an ESI fork that you hope gets merged back into the main development effort?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants