Well, still wasn’t able to run them. Sold my old laptop and bought new one, which has issues crashing, so now it is back at Gigabyte’s possession for few days. As soon as I get it back, will get on with updating the data.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
Opened as per topic starter’s request
2 Likes
i use a geddon with auto-target cruise missiles and sentries for those, everything else i use my caldari navy raven which is able to put up with anything and takes 5 of the elite serpentise bs to get in range and damage my tank, by than my mjd is charged for another jump anyways
1 Like
In theory yes, but I got double jammed a couple times. Which means you are thrown back to not being able to lock anything. But it’s much less annoying as before the ECM change.
1 Like
From my experience few days ago, 3 out of 5 cruisers managed to jamm me. I lost all the locks, but I could still retarget those 3 cruisers and blow them up
1 Like
Hmm, I remember differently … once I got jammed by two ships simultaneously I lost all locks and couldn’t retarget any of the jamming ships. Though I’m not 100% sure about, but was thinking that it is the expected behavior of being able to only lock the jamming ship.
You are not “only able to lock the jamming ship”
You are “only able to lock ships jamming you”.
Imagine it this way, any ship jamming you opens himself to be targeted back regardless of anything else (provided he is in locking range)
1 Like
I am looking into this, but I suspect that wiki is also wrong on some points.
Anyhow, rolling an update this weekend with all data actually generated from EVE api endpoints.
As long as the enemy ship types are correctly assigned to mission, the actual effects will be auto calculated, like web and scrams. The resistance profile is still manually assigned since some factions are hard to figure out from API and list of enemies.
1 Like
So new version is there. I hope this one is cleaner and nicer to use. Here is comparison of old vs new interface
As for changes behind the scenes, the following happen:
- Double checked all the data with eve survival and eve uni
- Pulled all 5131 entity from EVE API, sorry ccp, but I was good and throttled down requests so it takes about 20 minutes and once per week to rebuild my caches
- All the effects now are auto calculated from dogma effect fields, so as long as the enemies are correctly listed per mission and per wave there should be no human error in assigning correct ewar that ships can fire
Plans for future:
- Considering that I now have all the NPC information, there is some fun thing I could do, like max theoretical incoming DPS per wave, mission, etc, but since I started new job it will take a while
What I need from visitors:
- Please take care and double check enemy types when you have chance and note any differences. The types are listed in smaller font under ship size for each wave.
o7
2 Likes
yes its the new jamming changes because “ew is OP” so now you can only target the jammer when your jammed which makes 0 sense, but this is ccp we are talking about. pvp wise because than it will only be good to jam if your out of the targets range
1 Like
wrong. When you are jammed, you can only target ships that are jamming you.
Please parallel your requests. It takes me less than a second to grab all the entities -.-
Back when I was setting up first requests, it was mentioned somewhere that they don’t like to many request per seconds.
If I remember correctly I fire about 33 request per second, but I am scrapping
MarketGroups: ‘https://esi.evetech.net/latest/markets/groups’,
UniverseGroups: ‘https://esi.evetech.net/latest/universe/groups’,
UniverseCategories: ‘https://esi.evetech.net/latest/universe/categories’,
UniverseTypes: ‘https://esi.evetech.net/latest/universe/types’,
DogmaAttributes: ‘https://esi.evetech.net/latest/dogma/attributes’,
DogmaEffects: ‘https://esi.evetech.net/latest/dogma/effects’,
So overall I end up with lots of data to request, whole process takes about 15-20 minutes, the entities themselves are most likely a minute or something in that whole part. But once I scrape that I can calculate anything else on demand
Wow, unbelievable.
He stated it as Past Tense with a single entity and then you jump in, say he’s wrong and then state it as Present Tense with multiple entities.
3 Likes
Really I am not surprised you have no clue why I wrote this.
There is no hard limit of request per second.
What the ESI has is an error limit per time window, and if you reach that error limit you just are denied resources until the end of the error window.
Also it has a correct cache and you should not even consider your application request rate when hitting unauthed endpoints.
BTW you should create your own cache, for eg the attributes are likely to be shared among several entities, same for effects.
Interesting indeed, still no need to be that guy who bombards them, but could increase the number or requests
I do something like 1k requests at the same time and it’s okay. Note it’s not 1K request/s, it’s really just 1k requests at the same time. It’s useful eg for the market pages.
So, my next EvE goal accomplished … all 4 Empire factions >5.0 standing. 
5 Likes