boynextdoor
Member
- Joined
- Feb 15, 2016
- Messages
- 79
- Reaction score
- 0
Hello Trinity team,
Another season, another thread of me asking someone to please make sure lon bombardment sader is up to date for the latest db / trinity release:
As it currently stands, the lon sader with coe timing doesn't work properly. Without CoE timing the bot knows to hit iron skin before casting bombard. With coe timing, the bot uses iron skin as a 'regular attack' instead of as a 'combo' to buff other abilities.
To run this build in the past we used some guys custom settings and files in season 5. In season 6 we used the beta playground from phelon. Phelon has disabled his previous work on the class from last season because his sader account was banned. I asked him about it and he replied with the following:
"I have decided I am no longer going to be playing Diablo 3. It hit me when I went to go watch streamers to find out how to play certain builds, that there just isn't enough people streaming to find the appropriate information to make quality class improvements. I am fighting with this and the direction they have taken this game with regards to shit balancing, and mandatory grouping. For the foreseeable, future Phelon's Playground will not be updated and I am going to ask XZ to remove it from the options in the Advanced tab. I apologize to those who use this on a regular basis, and I hope you enjoyed my work. I wish you all the best in Diablo 3, and happy Paragon farming!"
- Phelon
So as it currently stands, the only viable build for crusader and the highest xp/hr build for any class or any botting software is no longer supported.
Could we please get lon bombard working as a default trinity script? and if not, can we get the files from s5 or phelon's work from s6 to be updated to the latest release?
Just in case I bought "the other bot" in case this isn't fixed as my sole reason for using demon buddy is for lon bombardment coe timing. Without that there is no reason to charge money for this bot as "the other bot" is just better at pathing, simple builds, and its also free after the 4th week of a season.
Please don't lock this thread. the last time I posted about "db devs need to ensure that builds are preserved from patch to patch" got locked and I got a warning on the forums. However, the 4 lifetime licenses I purchased will be useless if this isn't fixed.
EDIT:
just now I updated trinity via svn, and set iron skin to 0. Works perfectly.
It was probably the iron skin slider. The wording is counter intuitive. "amount health must be below before casting spell" I figured if you set it to zero that would mean it would never cast teh spell ever because you can never go below zero. Instead I set it to 100 because regardless of my hp it would always have iron skin as an option.
Good lucking out guys. I'll edit my main post with this.
"tested on 2.50.228 in Grift with wait for convention elements option checked, bombardment units slider 1, all bombardments within acceptable timing of last 1/4 lightning or phys. iron skin was being synced properly before bombardment and with iron skin for survival slider set to 0 it was correctly waiting to use it for bombardment when it wouldn't be back up on CD by next bombardment.
If this is not what you're observing i need a log, settings export and detailed explanation of what its doing wrong."
TLDR: set bombard slider to 1, iron skin slider to 0
Another season, another thread of me asking someone to please make sure lon bombardment sader is up to date for the latest db / trinity release:
As it currently stands, the lon sader with coe timing doesn't work properly. Without CoE timing the bot knows to hit iron skin before casting bombard. With coe timing, the bot uses iron skin as a 'regular attack' instead of as a 'combo' to buff other abilities.
To run this build in the past we used some guys custom settings and files in season 5. In season 6 we used the beta playground from phelon. Phelon has disabled his previous work on the class from last season because his sader account was banned. I asked him about it and he replied with the following:
"I have decided I am no longer going to be playing Diablo 3. It hit me when I went to go watch streamers to find out how to play certain builds, that there just isn't enough people streaming to find the appropriate information to make quality class improvements. I am fighting with this and the direction they have taken this game with regards to shit balancing, and mandatory grouping. For the foreseeable, future Phelon's Playground will not be updated and I am going to ask XZ to remove it from the options in the Advanced tab. I apologize to those who use this on a regular basis, and I hope you enjoyed my work. I wish you all the best in Diablo 3, and happy Paragon farming!"
- Phelon
So as it currently stands, the only viable build for crusader and the highest xp/hr build for any class or any botting software is no longer supported.
Could we please get lon bombard working as a default trinity script? and if not, can we get the files from s5 or phelon's work from s6 to be updated to the latest release?
Just in case I bought "the other bot" in case this isn't fixed as my sole reason for using demon buddy is for lon bombardment coe timing. Without that there is no reason to charge money for this bot as "the other bot" is just better at pathing, simple builds, and its also free after the 4th week of a season.
Please don't lock this thread. the last time I posted about "db devs need to ensure that builds are preserved from patch to patch" got locked and I got a warning on the forums. However, the 4 lifetime licenses I purchased will be useless if this isn't fixed.
EDIT:
just now I updated trinity via svn, and set iron skin to 0. Works perfectly.
It was probably the iron skin slider. The wording is counter intuitive. "amount health must be below before casting spell" I figured if you set it to zero that would mean it would never cast teh spell ever because you can never go below zero. Instead I set it to 100 because regardless of my hp it would always have iron skin as an option.
Good lucking out guys. I'll edit my main post with this.
"tested on 2.50.228 in Grift with wait for convention elements option checked, bombardment units slider 1, all bombardments within acceptable timing of last 1/4 lightning or phys. iron skin was being synced properly before bombardment and with iron skin for survival slider set to 0 it was correctly waiting to use it for bombardment when it wouldn't be back up on CD by next bombardment.
If this is not what you're observing i need a log, settings export and detailed explanation of what its doing wrong."
TLDR: set bombard slider to 1, iron skin slider to 0
Last edited:
