Jumbo Cactpot Ticket Vanished

[Grimmel]

Try submitting a bug report

The problem with "Submitting a Bug Report" is that there is NOT enough information to explain a way on how this bug might be replicated as this has happened to me twice. I used to do Bug Reports for games as part of my Game Producer Degree and most of the time they ask you how or what you did to replicate the bug. There is simply not enough information, that we the users, know about how or why this bug might come about.

The only thing we can submit on replicating this bug is "buy a ticket" and "Wait till the ticket drawing is out."And would thus be moved to the "Insufficient data thread".

This type of thing needs to be figured out in a controlled environment where it would need a parser to scan for errors or abnormalities that might occur on multiple and simultaneously running instances in order to familiarize a pattern of what may be causing the issue. This is something normal players cannot do. Maybe a multi boxer with 8-10 accounts and the right program to scan all clients at the same time might be able to do it. But for a player to be doing it on one client alone: almost impossible to figure out a pattern.

The average joe players simply lack the equipment to give a thorough report on a bug like this.

[CGMidlander]

The problem with "Submitting a Bug Report" is that there is NOT enough information to explain a way on how this bug might be replicated as this has happened to me twice. I used to do Bug Reports for games as part of my Game Producer Degree and most of the time they ask you how or what you did to replicate the bug. There is simply not enough information, that we the users, know about how or why this bug might come about.

The only thing we can submit on replicating this bug is "buy a ticket" and "Wait till the ticket drawing is out."And would thus be moved to the "Insufficient data thread".

This type of thing needs to be figured out in a controlled environment where it would need a parser to scan for errors or abnormalities that might occur on multiple and simultaneously running instances in order to familiarize a pattern of what may be causing the issue. This is something normal players cannot do. Maybe a multi boxer with 8-10 accounts and the right program to scan all clients at the same time might be able to do it. But for a player to be doing it on one client alone: almost impossible to figure out a pattern.

The average joe players simply lack the equipment to give a thorough report on a bug like this.

Look at some of the threads in the "Accepted Bugs" section of the forum. You'd be surprised how little information you need to provide in order for SE to consider it.

You're submitting a bug report, not doing the debugging legwork.

[SecretCrowds]

It happened to me one of the weeks too.

[KaedrianLiang]

/op

I suspected this was happening but when i /sh inquiring if anyone else experienced the issue no replies. This has happened to me twice.

[Itseotle]

I had this happen to me too, twice actually. Part of me just concluded that I MUST have forgotten to buy this weeks ticket but I was sure that I had. The second time I happened I knew something was up. Haven't won anything above 4th prize though :P

[Catwho]

Question: Did you ever switch computers, or between PC/PS? I've lost completed ventures on my retainers, and the bug was traced to switching PCs. That data is supposed to be stored server side, but somehow the menu data got corrupted when I switched between my laptop and desktop, and my ventures completely disappeared.

[Grimmel]

Question: Did you ever switch computers, or between PC/PS? I've lost completed ventures on my retainers, and the bug was traced to switching PCs. That data is supposed to be stored server side, but somehow the menu data got corrupted when I switched between my laptop and desktop, and my ventures completely disappeared.

Sadly no, this isn't the case. I only have the PC version and and no other PC/laptop in our house can run FFXIV.

[Grimmel]

You're submitting a bug report, not doing the debugging legwork.

This type of thing needs to be figured out in a controlled environment where it would need a parser to scan for errors or abnormalities that might occur on multiple and simultaneously running instances in order to familiarize a pattern of what may be causing the issue. This is something normal players cannot do. Maybe a multi boxer with 8-10 accounts and the right program to scan all clients at the same time might be able to do it. But for a player to be doing it on one client alone: almost impossible to figure out a pattern.

The average joe players simply lack the equipment to give a thorough report on a bug like this.

My second half of my statement, that I linked above, was for you to understand how something like this should be looked into by the developer and the process in which it is handled by a team of developers.
It was to explain to you how we the users cannot give a valid report on something like this because there is not enough data for the users to give to the developer team and that the only thing we could feasibly manage to tell them was to buy a ticket and wait till the winning numbers were selected.

I was merely explaining the process of a debug team and what should be done and that the regular player does not have this at their disposal and the reason why our bug reports would be moved to insufficient data.

This bug is not like most bugs where if you were to fall through a certain part of the map, you can easily explain where, when, how, and why.

Where, when, how, and why are some of the basics a developer needs to know when looking through bug reports to determine a cause and seek out a solution. This vanishing ticket for the Jumbo Cactpot cannot be easily applied with "Where, When, How and Why"