Bio Engineer Archive
Thread: Question to TH: Invalid pets, submitted 5/3/04
I'd like to see that changed to:
Scenario: Havingthe "Invalid pet code"in the datapad calling process results in BE customers getting "Invalid pet" calls where they need to adjust either stats or CL when they try to summon the pet from the pad. This leaves the BE clientwitha petwith stats/CL different to what they paid for and cancause bad feeling between the BE and his/her clients.
The question: Whyisn'tthe invalid pet check codemoved/added to the crafting process so the CL of the creature can be displayed as we make it, rather than it being left only in the datapad call process?
Short, sweet and addresses the particular issue head on...
NJ62 wrote:
When in doubt.. use the word when.
"Currently a bio-engineer pet which is crafted just now (for example today), can still get the "pet invalid" dialogue box when a customer tries to tame it. This means that a bio-engineer cannot sell pet deeds with any confidence that the pet he or she has created will be valid. When will a system be put in place in which either 1) the bioengineer cannot create an invalid pet or 2) the bioengineer is able to check the pets' validity pre-taming, as this is a game-breaking issue that needs to be addressed.
meroc wrote:I'd like to see that changed to:
The question: Whyisn'tthe invalid pet check codemoved/added to the crafting process so the CL of the creature can be displayed as we make it, rather than it being left only in the datapad call process?
Short, sweet and addresses the particular issue head on...
NJ62 wrote:When in doubt.. use the word when."Currently a bio-engineer pet which is crafted just now (for example today), can still get the "pet invalid" dialogue box when a customer tries to tame it. This means that a bio-engineer cannot sell pet deeds with any confidence that the pet he or she has created will be valid. When will a system be put in place in which either 1) the bioengineer cannot create an invalid pet or 2) the bioengineer is able to check the pets' validity pre-taming, as this is a game-breaking issue that needs to be addressed.
The problem with this question is that they might just give you an answer e.g. because if we moved it to the creation process it wouldn't catch any previously made pets, and we don't progress any futher. Sure you can counter "but I meant add it there as well" but of course we don't get a dialogue of this sort.
I like the "when" variation of the question I suggested as it kind of forces a good answer (of course if the devs are in a hurry they could just answer it "NEVER", I suppose).
Bar
NJ62 wrote:
When in doubt.. use the word when.
"Currently a bio-engineered (?) non-Creature Handler (?) pet which is craftedunder the current systemcan still get the "pet invalid" dialogue box when a customer tries to tame it, forcing the customer to change the creature's statistics or CL. This means that a bio-engineer cannot sell pet deeds with any confidence that the pet he or she has created will be valid. When will a system be put in place in which either 1) the bioengineer cannot create an invalid pet or 2) the bioengineer is able to check the pets' validity durring or imediately after its creation?To us, this is a game-breaking issue that needs to be addressed.
Its only one question
and a good one at that. I say run with it.
Hope you don't mind the edit, trying to see how it could be more clear if I didn't have a clue what was being disscussed. Is it necessary to detail that this is for non-CH pets or do we assume that will be understood?
meroc's question gives them less opportunity to give a cop out answer.
Xechran wrote:
NJ62 wrote:
When in doubt.. use the word when.
"Currently a bio-engineered (?) non-Creature Handler (?) pet which is craftedunder the current systemcan still get the "pet invalid" dialogue box when a customer tries to tame it, forcing the customer to change the creature's statistics or CL. This means that a bio-engineer cannot sell pet deeds with any confidence that the pet he or she has created will be valid. When will a system be put in place in which either 1) the bioengineer cannot create an invalid pet or 2) the bioengineer is able to check the pets' validity durring or imediately after its creation?To us, this is a game-breaking issue that needs to be addressed.
Its only one question
and a good one at that. I say run with it.
Hope you don't mind the edit, trying to see how it could be more clear if I didn't have a clue what was being disscussed. Is it necessary to detail that this is for non-CH pets or do we assume that will be understood?
I think that is a pretty good question. No question is guaranteed to generate a good answer but this question will lay out the subject to the devs and hopefully will raise the awareness of the issue. Unless someone comes up with something else you guys think is better I'll post the above questions for you guys later today when we are asked to submit the questions.
DocSavag wrote:
Xechran wrote:
NJ62 wrote:
When in doubt.. use the word when.
"Currently a bio-engineered (?) non-Creature Handler (?) pet which is craftedunder the current systemcan still get the "pet invalid" dialogue box when a customer tries to tame it, forcing the customer to change the creature's statistics or CL. This means that a bio-engineer cannot sell pet deeds with any confidence that the pet he or she has created will be valid. At what definitive date will a system be put in place in which either 1) the bioengineer cannot create an invalid pet or 2) the bioengineer is able to check the pets' validity durring or imediately after its creation?To us, this is a game-breaking issue that needs to be addressed.
Its only one question
and a good one at that. I say run with it.
Hope you don't mind the edit, trying to see how it could be more clear if I didn't have a clue what was being disscussed. Is it necessary to detail that this is for non-CH pets or do we assume that will be understood?
I think that is a pretty good question. No question is guaranteed to generate a good answer but this question will lay out the subject to the devs and hopefully will raise the awareness of the issue. Unless someone comes up with something else you guys think is better I'll post the above questions for you guys later today when we are asked to submit the questions.
Ok i was thinking this change might prevent the inevitable "soon" that will follow if we approch with "when"
That works for me ![]()
BTW Doc and NJ62 Thanks sooooo much for helping to keep our profession afloat right now![]()
NJ62 wrote:
HOw about "In which publish or mini-publish"?
Add that to the above question and it will be good for me. Of course we'll probably get an answer that's vague and doesn't really answer the question.