maurerit / abandapart Goto Github PK

There should be a global preference and a personal preference

The router maintains a list of available workers but when these workers disconnect the router doesn't take this into account and remove them as available workers. A request may come in that gets routed to said worker and by lost.

@industrybot: calculate Sleipnir

When items are shipped and land at their destination, inspect what was delivered and notify people that their tasks are ready

For invention salary, need to divide by the runs*batchSize instead of just runs.

Store these per user id in slack
Also have a global configuration to be used in case the user hasn't overridden them.

This also implies that it be used by the IndustryCalculationService.

A simple little process to tap into the forming bus and calculate builds for every single buildable item in EVE.

Upon completion of the build check several things should happen
1 The process will check profitability and save these items
2 The process will save the non-profitable items into a different 'bucket'
3 The process will publish the profitable items to the bus (right now, to the slackbot)

Once a corporate queue is built, plan out who is building how much of each queue item.

This should A: Be a preference, B: use the defaults for different things (2/4 for T2 and whatever T3 is).

Asked the industrybot to calculate build costs for a proteus and he sent:

{
"systemName": "Atreen",
"requestedBuildTypeId": 29988,
"requestedBuildTypeName": "Proteus",
"industrySkills": {
"preference": null,
"industrySkillLevel": 5,
"advancedIndustrySkillLevel": 5,
"industrySkillLevelMultiplier": null,
"advancedIndustrySkillLevelMultiplier": null
},
"inventionSkills": {
"preference": null,
"encryptionSkillLevel": 4,
"datacoreOneSkillLevel": 3,
"datacoreTwoSkillLevel": 3,
"encryptionSkillLevelMultiplier": null,
"datacoreOneSkillLevelMultiplier": null,
"datacoreTwoSkillLevelMultiplier": null
},
"meLevel": 10,
"teLevel": 20,
"decryptor": null,
"findPrices": false,
"useBuildOrBuyConfigurations": false,
"buildOrBuyConfigurationList": null
}

to a worker. Seems the type lookup is perfect but anything else... nothing :(.

The same symptoms are also affecting Tech 1, bumping this up in priority.

Show all preferences. Highlight user specific settings and don't highlight the settings that are merging in from the global preferences.

Right now the SlackBot can accept the very basic build request command. It still needs to be able to do the following (and this ticket will need broken up into multiple other tickets)

• Accept the calculation request to use BUY or SELL prices
• Use the built vs bought configurations (#7)
• Accept the skills to use (#18)

I can't think of anymore tonight... stay tuned!