I am trying to understand GSE more. I am just baffled at how this performs fairly well when the sequences seem full of blocks that donāt do anything. I guess it just boils down to making the timing work out by skipping over those.
Hand being cast only by the SBA at the bottom actually makes sense, since thereās no penalty for spells with a cast-time longer than GCD, it just didnāt seem like that block would fire frequently.
Anyway, I apologize for my repeated posts. I was really just looking for some explanation from Vin about how/why he built the sequence the way he did.
Looking over the sequence, it does seem that people are getting extremely lucky with the SBA firing off Hand of Gulādan. I tried it on my level 80 warlock, and I saw Hand of Gulādan getting fired off as well. It looks like it really just comes down to that situation.
The thing is, I have not played warlock in such a long time that I do not know the correct rotation or when each spell should be used. If Hand of Gulādan is an important spell that needs to be cast frequently, then having it in the rotation is obviously a good thing. But then it all comes down to how it impacts the current sequence if another spell is added. Would it deplete more crystals? I think they are crystals. Things like that.
So I think it is really just down to luck when it comes to whether the SBA is proccing more often for some players than others. You may simply not be getting as many casts of that spell as possible.
That is why I said the best course of action is to add an additional block to the current sequence. Literally add a block, copy the modifiers, and then add /cast Hand of Gul'dan to see what happens.
That is why I said the best course of action is to add an additional block to the current sequence. Literally add a block, copy the modifiers, and then add /cast Hand of Gul'dan to see what happens.
Yeah, I have my own sequence that Iāve made but Iām looking at and trying others because Iām trying to get a good balance for Shard generation (shadowbolt/demonbolt) vs spending (hand of guldan).
Itād be very nice if the GSE builder simulation worked for soul shards but it doesnāt currently. Also, since Demonbolt is a modifier cast it wouldnāt be able to simulate those gains anyway.
1 Like
I apologize, it did seem the one I had above was old and not my most up to date one.
I have updated to the one Iāve been testing lately while using the CDM from Blizzard.
Should be a lot less reliant on SBA and has its own block to fire off Hand of Gulādan
2 Likes
Iām not trying to be a disruption, and hopefully I donāt get muted againā¦but this updated sequence (both copying here and 1.0.4 from wago) seems to be almost identical to the previous one? Specifically, I donāt see a new Hand block. Maybe a copy/paste error?
1 Like
I can also confirm there is indeed no sign of a hand of gulādan block.
Are you guys deleting and reimporting the macro? I double checked, are you sure you are using the correct talents?
In the GS:E builder it will show as corruption, no idea why, but in game it shows as Hand
Oh thatās true, there are sometimes when I make a sequence and something is something up as another skill due to talents or something.
I will have to test it out later and double check.
I was specifically copying it into the GSE builder website to look at. I copied it into GSE in game and it does show as Hand of Gulādan. thatās odd. Iāll try this one out. Thanks!
1 Like
That would most likely be because one procs into the other iirc. Most likely why it appears that way.
Corruption isnāt even a spell that Demonology has (anymore). Hand of Gulādan procs into Ruination, but Hand is the base spell. Must just be something weird with GSE. You can (probably) fix it by using the spellID for Hand of Gulādan in your sequence instead of the name or ID youāre using currently. Hand is 176725, Corruption (which your GSE import shows) is 172.
not sure why GSE reads spellID 172 as Hand of Gulādan though.
No idea why it does that, but I dont use the builder here because its honestly bad and gets more wrong than it does right in terms of sequences.
Also it seems to lead to macro corruption in game so i tend to avoid it.
If your expecting to parse 100 with a macro then im sorry your living in crazy town. This helps with your game play or it helps people who cant really play. These arenāt meant to be 100 parse. This works completely fine. Got 3k with 0 issue using it but I did my own cd mods and used demonbolt on mod. Vini did great job.
2 Likes
I assume this is directed at me. I wasnāt attempting to criticize or lessen the work that Vinās done. I also didnāt suggest parses at all. Outside of being surprised that you could get to 3125 running it, but that was my misunderstanding due to reviewing the sequence in GSE Builder which is apparently buggy.
I was mostly asking questions because itās a well-regarded sequence and I wanted to understand what looked odd to me. The majority of that has been answered by Vin since then.
In short, weāre all good here, thanks again to Vin for his feedback and efforts.
2 Likes
ęēäøå°GSEåŗååē¬¦äø²emphasized text
brotha. this sequence is amazing for someone like me. i play with a foot pedal because my hands dont work well, and im blasting through 12s-13s with this sequence. Its worth noting that it even though the sequence is named for soul harvester, it works even better on diabolist. Thanks for this! genuinely!
3 Likes
Part of that is due to the recent tuning soul harvester is only ahead in ST by like a 1k but diabilist is way ahead in aoe and cleave so happy warlocking
2 Likes
Guys which settings I have wrong where my Mod keys when pressed they pause sequence?
This Macro is great, no issues leveling and it continues to improve as you level up. Fantastic work!
1 Like
means you have keybinds on the modifiers for whatever key you have it bound to