Bug report by MLGERROR (forum topic #2613)| Issue # | 823 |
| Issue | Supply drop doesn't spawn |
| Description | When MLGERROR Requested ammo supply ended up not getting it even after a while might be a server lag or internet problem |
| Script area | whetstone |
| Priority | Low |
| Logged by | Mazen |
| Assigned to | Mike |
| Status | New |
| Comments | No comment at this moment waiting to be confirmed |
and keep the notification for this post on If there is update on this Bug will let you know
Mazen wrote:
Thank you for the report MLGERROR,
i tested the bug but it's working fine for me,Might be a internet problem/server lagging for a second and ended up not getting the ammo drop i will be testing it more And please provide me with more evidence when it happen at the day exactly don't delay the video and stick with youtube videos for better Quality i will log the Report now for you
Sorry for any Disturbance happened to you.
I have no clue when it happened
I can't possibly debug this if I don't know what time or even DAY it happened..
I will be adding more debugging logs in the next version which will log every single thing regarding supply drops for every single player.
I have just discovered a bug that causes objects to be wrongly destroyed. A piece of code in the collectables script (specifically gang tags) is destroying objects without actually checking they are there. Another object (such as a supply drop or a treasure hunt box) might take their ID and be wrongly destroyed.
I've fixed this issue for the next update, but just in case the same issue happens elsewhere I have added detailed debugging info. After the next update when you call a supply drop it will tell you a unique ID for that supply drop. If you have an issue with a supply drop tell me the ID in chat and I can view the debug logs for that specific supply drop.
Mike wrote:
I have just discovered a bug that causes objects to be wrongly destroyed. A piece of code in the collectables script (specifically gang tags) is destroying objects without actually checking they are there. Another object (such as a supply drop or a treasure hunt box) might take their ID and be wrongly destroyed.
I've fixed this issue for the next update, but just in case the same issue happens elsewhere I have added detailed debugging info. After the next update when you call a supply drop it will tell you a unique ID for that supply drop. If you have an issue with a supply drop tell me the ID in chat and I can view the debug logs for that specific supply drop.
so the treasure hunt clue non-exsistant was because it was getting destroyed by this =)) yaay it got fixed!
