Small safety patch related to quests

When I fixed some quest problems long ago, I added some lines that would prevent a combination of trigger without prior response when this was already done. To pass this information outside the function, I set the last general response to none. This can theoretically cause side effects. As it only prevents one more check (my other changes already removed many more), it is safer to delete these lines.

No bug url, as old bug was in old bug tracker, and a new bug is hopefully prevented this way.

[Khaki, 2008-11-04 02:43:30]

Why remove only these lines and not the other lines containing
TestedWithoutLastResponse?

On 2008/11/03 20:18:15, Lanarel wrote:
>

[Lanarel, 2008-11-04 07:16:36]

That TestedWithoutLastResponse makes sure the combination of tested trigger with
no last response is only tested once within this function, instead as it was
before for each quest that had no last response. Certainly just after this
change, that would mean every quest :). Currently, that might be much rarer,
probably all quests at the beginning of a quest step. The lines I removed made
sure one more test outside this function was not done, by passing the value of
TestedWithoutLastResponse to outside this function in a way that is not really
100% good.