I'm having a very similar experience right now, with both the 'LoN Wave of Light' and 'Classic One Punch' Trinity combat routines.
RebornBuddy Forums
Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
[REQUEST] Sunwuko WOL 2.6.1
- Thread starter dreblin
- Start date
I am posting this here, after having already posted it on the discord, for those of you not on the discord. Any help or wisdom would be appreciated.
I think I know how to fix 2 problems in the WoL builds, but I don't have the know how to make it work. I have been staring at the code for hours trying to figure out how to 'talk' to DB to no avail. So. Other than navigation, I only seem to find 2 problems with the bot that I believe can be solved with 1 fix. If it is stuck between mobs it doesn't always realize it needs to cast WoL, this mostly seems to happen in doorways. If it can't gain proper targetting (im assuming this is what is happening) on a mob, usually because they are located in doorways or on map edges, it does not cast WoL. In the code, using dashing strike is described as casting at (CurrentTarget.Position), however, WoL is described as (CurrentTarget). I assume by simply changing to current target position it should fix the problem, as it will often still dashing strike under the same conditions that are prohibiting it from using WoL.
So long story short, can someone find a way to make WoL accept (CurrentTarget.Position), as when I simply try to substitute that in, I get errors in DB and the routine will not run
Compiler Error: C:\Users\Stephanie\Desktop\Dandelions\Plugins\Trinity\Routines\Monk\WoLEdited.cs(198,26) : error CS0029: Cannot implicitly convert type 'Zeta.Common.Vector3' to 'Trinity.Framework.Actors.ActorTypes.TrinityActor'
This is the error when attempting to sub in CurrentTarget.Position for WoL
The problem in mine appears to not be target distance, but rather, targeting issues involving the environment, wether it be doors, map edges, especially large environmental objects, etc. These are the only things that keep it from using WoL. But it continues to use Dashing strike in most cases. When it does, sometimes it causes the mob to follow just ever so slightly, allowing the bot a targetting path, and thus a successful cast of WoL.
I ran comparative tests for 3 hrs last night using identical build (https://www.d3planner.com/406131377) with the LoN WoL, One Punch, and my own version of One Punch with minor edits regarding kiting distance that I am not even entirely sure are used. Here are the results (https://docs.google.com/spreadsheets/d/15SGdZ-bfId1Fg6MBR2_xF7z7APFCQfUmhLvEWvxwmnc/edit?usp=sharing). From them, I can conclude that there is a negligible difference in speed between the 3 builds. However, I find LoN WoL to be unreliable to be left alone, it must be baby sat in case it resets game or it will not reapply initial Sweeping Winds. I still must test the 3 using augmented ancient gear at higher GRS, using WH instead of Kyo's soul belt, and with the generator build as Fuzio0 has mentioned having success with.
If anyone knows how to code, take a swing at the WoL targeting issue and see if you can't get it to attempt to cast 1f in different random directions from target, if it cannot cast WoL on target or target.position (if you can get that working too).
I think I know how to fix 2 problems in the WoL builds, but I don't have the know how to make it work. I have been staring at the code for hours trying to figure out how to 'talk' to DB to no avail. So. Other than navigation, I only seem to find 2 problems with the bot that I believe can be solved with 1 fix. If it is stuck between mobs it doesn't always realize it needs to cast WoL, this mostly seems to happen in doorways. If it can't gain proper targetting (im assuming this is what is happening) on a mob, usually because they are located in doorways or on map edges, it does not cast WoL. In the code, using dashing strike is described as casting at (CurrentTarget.Position), however, WoL is described as (CurrentTarget). I assume by simply changing to current target position it should fix the problem, as it will often still dashing strike under the same conditions that are prohibiting it from using WoL.
So long story short, can someone find a way to make WoL accept (CurrentTarget.Position), as when I simply try to substitute that in, I get errors in DB and the routine will not run
Compiler Error: C:\Users\Stephanie\Desktop\Dandelions\Plugins\Trinity\Routines\Monk\WoLEdited.cs(198,26) : error CS0029: Cannot implicitly convert type 'Zeta.Common.Vector3' to 'Trinity.Framework.Actors.ActorTypes.TrinityActor'
This is the error when attempting to sub in CurrentTarget.Position for WoL
The problem in mine appears to not be target distance, but rather, targeting issues involving the environment, wether it be doors, map edges, especially large environmental objects, etc. These are the only things that keep it from using WoL. But it continues to use Dashing strike in most cases. When it does, sometimes it causes the mob to follow just ever so slightly, allowing the bot a targetting path, and thus a successful cast of WoL.
I ran comparative tests for 3 hrs last night using identical build (https://www.d3planner.com/406131377) with the LoN WoL, One Punch, and my own version of One Punch with minor edits regarding kiting distance that I am not even entirely sure are used. Here are the results (https://docs.google.com/spreadsheets/d/15SGdZ-bfId1Fg6MBR2_xF7z7APFCQfUmhLvEWvxwmnc/edit?usp=sharing). From them, I can conclude that there is a negligible difference in speed between the 3 builds. However, I find LoN WoL to be unreliable to be left alone, it must be baby sat in case it resets game or it will not reapply initial Sweeping Winds. I still must test the 3 using augmented ancient gear at higher GRS, using WH instead of Kyo's soul belt, and with the generator build as Fuzio0 has mentioned having success with.
If anyone knows how to code, take a swing at the WoL targeting issue and see if you can't get it to attempt to cast 1f in different random directions from target, if it cannot cast WoL on target or target.position (if you can get that working too).
I have managed to fix the issue of running into packs of mobs, getting stuck, and not casting WoL.
In the MonkSunwukoWaveOfLight.cs file, navigate to line 172.
Comment out lines 172 through 178.
It should look like this:
Code:
// if (!Skills.Monk.WaveOfLight.CanCast())
// {
// return false;
// }
// if (swStacks <= 1)
// return false;Save the file, and completely restart DB.
Cheers
Last edited:
icotulookin
Member
- Joined
- Jan 26, 2012
- Messages
- 149
That's because it isn't there. You have to have some basic understanding of code/the program to find these and edit. @fazio0 I'll break it down for you.
Open your DB folder should look like this: DBFolder>Plugins>Trinity>Routines>Monk
Use Notepad to open the file. Hit CTRL + G line 172 Delete 172-178 and save.
Close and restart DB
Open your DB folder should look like this: DBFolder>Plugins>Trinity>Routines>Monk
Use Notepad to open the file. Hit CTRL + G line 172 Delete 172-178 and save.
Close and restart DB
mate, ctrl+g doesnt work in notepad...
From line 172 to 178 or line 172 and 178?
icotulookin
Member
- Joined
- Jan 26, 2012
- Messages
- 149
I'm currently working on a solution for the routine I've mentioned above.
I am attempting to extend the default WoL attack range, as well as default to casting WoL when stuck/trapped by mobs. These seem to be the two biggest issues with this routine.
Any other suggestions? Let me know. I will post my solution here as soon as it's ready.
Tyvm for explanation man..
1. u can see this build https://www.icy-veins.com/d3/monk-sunwuko-wave-of-light-build-patch-2-6-1-season-12 ,
Focus and Restraint is more better taht coe unit see top ppl - se we need good avoid
2. Dashing Strike - need betetr avoid dengerouse, Crippling Wave - need to use pasive from Kanai's Cube
3.Okulus to use ?
4. he muse attack range to use Zei's Stone of Vengeance
srry my english is bad ;q
Sunlounger
Member
- Joined
- Feb 27, 2015
- Messages
- 32
yeah everyone works ok, cept for when he stands under the RG and does zero damage or gets caught on 1 trash mob and takes 20secs to kill
I attached my current version. Works pretty good for me.
I will now check for Sweeping Winds and rebuff if necessary. It should also handle blocked situations much better.
Collecting globes / shrines is a mess, so i deactivated both options.
I will now check for Sweeping Winds and rebuff if necessary. It should also handle blocked situations much better.
Collecting globes / shrines is a mess, so i deactivated both options.