| Attachment | Size |
|---|---|
| jamjar202_1188.pdf | 143.93 KB |
I'm James and I'm just looking to help out any way I can really
Last edited by jamjar202 on 17 Sep 2017 - 09:01.
| Attachment | Size |
|---|---|
| jamjar202_1188.pdf | 143.93 KB |
I'm James and I'm just looking to help out any way I can really
I am most often tasked with bug testing quests. Essentially first playing through questlines and finding anything that seems broken or any spelling errors, then going through the quests in the construction kit to see which scripts are not functioning.
I then cross reference that with established bug lists to discover if the issue also occurs elsewhere/there is a common theme. For example there was trouble with some books not updating the journal due to an improperly written script used in TR_data, meaning it was used across many quest books.
Obviously also reporting anything else that also seems off whilst playing, such as invisible walls or missing textures

Hi James, when testing for TR
Hi James, when testing for TR rebuilt, what tools or process did you use when reporting bugs/features? If you can give me about a paragraph of info on that, that'll give me a sense of if you've got a good sense of what to report/not report, if you used staged testing (only looking at particular elements) etc.