Scorchbeast
Admin
Posts: 60
Runescape Name: Scorchbeast
|
Post by Scorchbeast on Dec 17, 2020 15:58:11 GMT
As many of you have already seen, today's update changes ba in some big ways. I wanted to share with you what was changed, what impact it has on us, and what may happen going forward.
What was changed? In response to an item dupe exploit, jagex has changed the way interfaces work. Any number of stacked interfaces now resolve in 1 tick, and stalls cannot be chained together.
What impact does this have on us? This change massively impacts how we play the main attacker role. Forcing how we know it (1t note, 2t note, shields, and device) no longer works to force through penance deaths, reducing its effectiveness dramatically.
Traditional egg duping and extending with the shrink-me-quick no longer works. The only way to extend is with single animation stalls, namely skillcape emotes. Discussions are already underway on how best to utilize these. 1-egging with omega eggs still works as before.
What can we expect in the future? So is ba dead? No, ba is not dead. For the time being, expect run times to come up a bit slower than normal while we, as a community, find new strategies to overcome the patches. At worst, runs will only be a minute or so slower.
Jagex has made it clear to us that they're willing to talk about where to go with ba when the dust settles, and have already expressed interest in talking to a couple community members. On top of this, they have said they will be looking into replicating previous mechanics where possible. It may take a while, but we will see some positive change eventually. We will keep you all updated when we find out more information.
|
|
Whurse
Sergeant
Posts: 24
Runescape Name: Whurse
|
Post by Whurse on Dec 17, 2020 19:03:33 GMT
Damn this is a big hit - gonna be hard to work around.
For those interested in the technical details, most of the queued commands we're interested in can be "normally" queued or "strongly" queued. Normally queued basically means a command won't break through interfaces in order to execute. A good example of this is the scrawled note. The queued interface is normally queued and thus won't break through the note's first interface. Strongly queued commands include call changes, the cannon's egg count updating, the fixed device interface, and damage. Previously, strongly queued commands would break up to 1 interface per tick while trying to execute. The new change is that strongly queued commands now break through ALL interfaces immediately until they execute. It is actually still possible to queue multiple interfaces and hold them, close them 1 at a time, etc. so long as no command is strongly queued.
This is certainly a big hit to BA. The only immediate solution I can think of is trying to find ways to queue stalls instead of interfaces, but that is easier said than done. Very curious to see what Jagex does to try to appease the BA community.
|
|