'Check the bait' action provides an empty message every 2 to 4 attempts. Checking the bait twice is not optimal as it scares away the fish, forcing you to start from the 'beginning' of the fishing mechanic. Additionally, a single session of fishing takes up to 3-4 minutes, and as a result this bug is very wasteful should it interrupt a prolonged attempt.
Description
Description
Details
Details
- Legacy ID
- 2202099019
- Severity
- None
- Resolution
- Fixed
- Reproducibility
- Always
- Category
- General
Steps To Reproduce
- Start fishing with an Improvised Fishing Rod.
- Press 'Check the Bait' at different intervals(between 20 and 40 seconds each).
- Observe messages such as "I sense no movement near the bait" etc.
- Notice no message provided at varying intervals(every 2 to 4) when pressing 'Check the Bait.' Forcing you to check it again and scaring away the fish as a result.
Additional Information
Related to http://feedback.dayzgame.com/view.php?id=17278.
Same results regardless of ping.
Event Timeline
Comment Actions
Here is a video better demonstrating the effects of this bug. Fishing was done at three servers with varying ping (30, 80 and 280). The bug occurred at similar intervals regardless of ping.
http://www.twitch.tv/tiredminer/b/581641378
<<< 2:00 - 9:00 - '90 ping Fishing'.
[ 2:57 - First empty message.
[ 5:51 - Second empty message.
[ 8:40 - Third empty message.
<<< 12:00 - 20:42 - '280 ping Fishing'.
[ 16:02 - First empty message.
[ 18:05 - Second empty message.
[ 20:32 - Third empty message.
<<< 24:00 - 34:30 - '30 ping Fishing'.
[ 26:38 - First empty message.
[ 30:23 - Second empty message.
[ 33:03 - Third empty message.
No fish was caught during the 34 minutes. Check the Bait action was triggered every time the previous 'Check the Bait' message has faded in chat.
Comment Actions
Hi TiredMiner,
firstly, thanks for your continuous cooperation and dedication! It is highly appreciated.
Secondly, we have confirmed the issue and it has now been scheduled for a fix.
Thanks again,
Andy
Comment Actions
Hi TiredMiner,
this has been fixed on our internal version and should be fixed on Steam soon.
Regards,
Andy