Items cleaner#1143
Conversation
|
This looks much better, thanks for putting it up again. I think this should be enabled behind a config flag. |
| self.max_storage = max_storage | ||
| self.items = items | ||
|
|
||
| def check(self): |
There was a problem hiding this comment.
The entry points to all workers needs to be called work. You can have your work function call something else though if you'd like.
|
If its a item cleaner function, it should defintly use the already existing item_filter config @TheSavior don't you agree? |
|
Yes, if that exists, I definitely agree. Looks like in SeenFortWorker we have: We can probably use that logic, and by having a DropItemsWorker inside the event loop, we will be able to remove all logic about recycling items from the SeenFortWorker. That is very exciting. |
|
still some problems Traceback (most recent call last): |
because 311/350 = 0 in v2 and 0.888 in v3
| if self.items[Item.ITEM_REVIVE.value] > 25: | ||
| how_many = self.items[Item.ITEM_REVIVE.value] - 25 | ||
| items_to_remove.append([Item.ITEM_REVIVE.value, how_many, '{} Revive'.format(how_many)]) | ||
| self.items[Item.ITEM_REVIVE.value] = self.items[Item.ITEM_REVIVE.value] - (how_many) |
There was a problem hiding this comment.
This GIGANTIC block of IFs makes me wanna cry. Why are you not using the item_filter? It's easy to add support to item names there, instead of IDs to make it more simple to the user. There is no way this PR is being merged with this craziness here. Check my PR for a very very simple DropItemWorker (I call it RecycleItemWorker, but whatever): #1156
|
This branch has conflicts that must be resolved |
Revert "gevent hotfixes" (aka, hell naw gevent)


Short Description:
inventory cleaner and show more items at start