I Have To Do WHAT? Fix Mission Text!

[Aurora_Girl]

6 hours ago, Take One said:

 

Bug reports already creates a list of bugs that needs to be fixed in a place where the devs are more likely to see it.

 

It's. Not. A. Bug. 

[Cancrusher]

I don't know if it qualifies as a bug or not, but I would also like to see this corrected.  If I take a mission to steal the McGuffin, then I also have to murder everyone in the place after stealing the McGuffin, it no longer feels like a heist/theft to me.

[Rudra]

9 hours ago, Take One said:

 

Bug reports already creates a list of bugs that needs to be fixed in a place where the devs are more likely to see it.

A bug is deficiency in the code. That deficiency in the code causes the problems.

A geometry error is a deficiency with the map or other objects. That deficiency allows examples like players getting under the map to attack up through the ground, which happened in CoX, for instance.

A text error is not part of the working code but is provided data to the user/player that is in error. This most often includes typos, but also includes poor grammar, bad word choice, and incorrect instructions to the user/player.

 

If a mission is coded for goal A, says player needs to accomplish goal B, but does not complete until player accomplishes goal A, that is not a bug. That is a text error. That is incorrect instructions provided to the user/player. The code itself, the mission, is working correctly.

 

If mission is coded for goal A, says player needs to accomplish goal A, player accomplishes goal A, and mission still does not complete, that is a bug. That is a failure of the code/mission to complete for requisite task.

 

Edit: Now if you were saying you think this would be more appropriate as a running set of entries in the typos section, that would make more sense. Unless the typo is in the code causing the program to not run correctly, it is not a bug. Bug = code problem.

Edited March 22, 2022 by Rudra

[Aurora_Girl]

4 hours ago, Rudra said:

A bug is deficiency in the code. That deficiency in the code causes the problems.

A geometry error is a deficiency with the map or other objects. That deficiency allows examples like players getting under the map to attack up through the ground, which happened in CoX, for instance.

A text error is not part of the working code but is provided data to the user/player that is in error. This most often includes typos, but also includes poor grammar, bad word choice, and incorrect instructions to the user/player.

 

If a mission is coded for goal A, says player needs to accomplish goal B, but does not complete until player accomplishes goal A, that is not a bug. That is a text error. That is incorrect instructions provided to the user/player. The code itself, the mission, is working correctly.

 

If mission is coded for goal A, says player needs to accomplish goal A, player accomplishes goal A, and mission still does not complete, that is a bug. That is a failure of the code/mission to complete for requisite task.

 

Edit: Now if you were saying you think this would be more appropriate as a running set of entries in the typos section, that would make more sense. Unless the typo is in the code causing the program to not run correctly, it is not a bug. Bug = code problem.

 

Aaaaaand if we're being all-time pedantic:

 

"Thwre" is a typo. 

 

"There was a mass of soggy eagles on top of scooter ice cream crow" is shitty writing. 

 

There's a difference. 

[Cancrusher]

Quote

"There was a mass of soggy eagles on top of scooter ice cream crow" is shitty writing.

 

Hey, you don't have to bag on Robert Jordan, okay?  The guys dead.  He can't defend himself.  😛

[TheZag]

Its not a bug but a sticky in bug reports for reporting wonky mission objectives could do it.  Similar to the typos thread but for keeping inconsistent mission objective reports in 1 place.  If the devs fix any would be great but they could at least be grouped up until then.  Would need that sticky thread for it though.