looting blacklist #18
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When "loot every item" is off, it will loot everything in the loot list. When "loot every item" is on, it will loot everything that is *not* in the loot list, effectively making the loot list a blacklist when "loot every item" is on.
Author
|
This will allow you to loot all the super-rare items even if you don't know the ID, or even if you didn't know the monster could drop it. |
divinity76
added a commit
to opentibiabr/otclient
that referenced
this pull request
Jan 5, 2026
vBot upstream has been abandoned, last commit was in 2022, PR's are being ignored (for example Vithrax/vBot#18 has been ignored since 2024) and the check may cause network failures. resolve #1544
divinity76
added a commit
to divinity76/otclientv8-otacademy
that referenced
this pull request
Jan 10, 2026
When "loot every item" is off, it will loot everything in the loot list. When "loot every item" is on, it will loot everything that is not in the loot list, effectively making the loot list a blacklist when "loot every item" is on. Related upstream issue: Vithrax/vBot#15 I have tried submitting this upstream too, but it seems vBot upstream is unmaintained: Vithrax/vBot#18
divinity76
added a commit
to divinity76/otclientv8-otacademy
that referenced
this pull request
Jan 10, 2026
vBot upstream has been abandoned, last commit was in 2022, PR's are being ignored (for example Vithrax/vBot#18 has been ignored since 2024) and the check may cause sporadic network failures: ``` WARNING: [BOT] [vBot updater]: Unable to check version: HttpSession timeout after 2 seconds ERROR: TCP connection failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ERROR: HttpSession unable to connect https://raw.githubusercontent.com/Vithrax/vBot/main/vBot/version.txt: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ```
divinity76
added a commit
to OTAcademy/otclientv8
that referenced
this pull request
Jan 20, 2026
vBot upstream has been abandoned, last commit was in 2022, PR's are being ignored (for example Vithrax/vBot#18 has been ignored since 2024) and the check may cause sporadic network failures: ``` WARNING: [BOT] [vBot updater]: Unable to check version: HttpSession timeout after 2 seconds ERROR: TCP connection failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ERROR: HttpSession unable to connect https://raw.githubusercontent.com/Vithrax/vBot/main/vBot/version.txt: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When "loot every item" is off, it will loot everything in the loot list.
When "loot every item" is on, it will loot everything that is not in the loot list, effectively making the loot list a blacklist when "loot every item" is on.
resolves #15