((Advertisement))
((Advertisement))
Patch 3.1 made fishing even faster, by reducing the average cast time even lower than patch 2.1.

Changes as Documented

The official patch notes list the following changes:

The first two changes are potentially very important, and are dealt with by the rest of this article.

Changes as Observed

Nobody knew precisely how much time was available for the angler to successfully click the bobber after it splashed - "several seconds" would be my best estimate. Consensus suggests that that time has been reduced, making it far more important to react immediately to the bobber splashing.

Many posters at the official forums have cited two related changes as "bugs":

  1. If the bobber splashes and is clicked in the final 1-2 seconds of the progress bar, no fish are caught, and no error message is displayed. This is different from the previous behaviour, where one could often click the bobber after the progress bar had faded and still catch a fish.
  2. There is a greater delay between the cast and the bobber appearing. Vorchyldr writes, "It no longer appears the instant you cast, it waits that one second for your line to appear with it." This is a particular issue for pool fishing, where several casts may be required before the bobber lands correctly. There always was a small delay due to lag (time delay between information being sent between client and server), but the time delay seems to have increased.

Neither of these can be attributed to excess lag.

Stornetta queried the first problem with a GM, and was told that it is now possible for a "bite" not to catch anything:

Commentary

Prior to the patch a complete cast cycle (from cast, catch/retrieve fish or wait for no bite, to recast) would take me an average of about 23 seconds. That's about 8 seconds more than simply half the duration of the timer. There are a couple of reasons for that:

In theory the patch's reduced fishing timer could turn a pre-patch average of 2.5 catches a minute, to almost 4 catches per minute. But the reality will be less dramatic for most players.

Pool fishing gains little benefit from the reduced timer because often far more time is spent moving between pools than physically fishing them. This is particularly true for rare pools with low numbers of fish per pool, such as Highland Mixed School, although avoiding enemies may become easier with the shorter timer. If the additional delay on casting is a genuine feature, pool fishing may yet have become slower.

Prior to the patch, about 5% (one in twenty) casts would run its duration without a fish biting. That figure was an average, and variable. So all casts biting will only cause a small change to the overall speed of fishing: Its main benefit is to make fishing feel less frustrating, since now you are guaranteed a catch, so long as you meet or exceed the skill requirements.

Unfortunately, the "none-event" catches - the observed failure to catch anything if the bobber splashes in the final seconds - will also cause a proportion of casts not to catch anything. But with more frustration: The angler has to actively click, rather than just letting the timer run out; and there is no visual feedback to tell them they have lost the mini-game.

Fortunately, the logical workaround works - click on the bobber just before the timer runs out (thanks Smoke and Opie301).

Perhaps the whole art of fishing just became more "twitch" orientated - and consequently a less social activity?

Postscript

WoWInsider reports that patch 2.2 made the following (undocumented) changes:

So hopefully the two main annoyances for many anglers have been fixed.

Learn More

There are no comments on this yet. If you would like to comment, start a new topic on the Fishing Forum or Contests Forum: Either use the page's name (Faster Fishing with Patch 2.1.0) as the topic title, or tag the topic with that name. Comments take a few minutes to appear here.