when you try build the improvised leather backpack by adding sticks to the leather courier bag it gives a message "I have made a ." and disappears...
Description
Details
- Legacy ID
- 4045536702
- Severity
- None
- Resolution
- Unable To Duplicate
- Reproducibility
- Have Not Tried
- Category
- Inventory
Event Timeline
I can confirm this!
Tried it twice:
- Had the bag on my back, added sticks -> dissapeared.
- Put the bag on the ground (thinking that was the prob), added sticks -> dissapeared.
Annoying little bug :(
Hi,
Thanks for sending in your feedback regarding this problem. I tried reproducing the issue on the latest internal build without result (both cases with the bag on the ground/on the back).
Would it be possible for someone to create a video of the issue please? Also, is the repro rate 100%? Do you experience desync when the issue occurs?
Thanks,
JStewart
I will try to reproduce it tonight.
Like I said, tried it twice, both times it dissapeared.
Second time (on the ground) I was streaming, first time (on the back) not.
Will post video link here later on tonight.
sure, thats what I did, i was referring to my lousy internet connection :)
here you go: http://youtu.be/EqkXUJZEzns
I can confirm this as well. Tried several times. In several different servers. Also tried using a variety of hides (cow, boar, deer). Every time the sticks are added to the courier bag the message "I have made a ." pops and the bag disappears. I have been able to reproduce this with 100% chance of happening. Ive tried 10 times for 10 failures as of now.
Thanks for sending in the video guys! I just tried to reproduce the bug again on the latest internal build, and the bag does not disappear. However, I'll leave this issue open so that we can regress the issue once the next update is released.
When I add sticks to a 4x4 slot Leather Courier Bag, I get a 5x5 slot Improvised Leather Backpack.
Had this issue also two times. I also can confirm. One with cow leather and onw with pork.
Alright guys, I'll close out this issue, since it is not possible to reproduce the issue in the current internal build.
Regards,
JStewart