26.11.2015 Views

Star Trek Voyager RPG d20 System

ST-VO v23c

ST-VO v23c

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

16. PET PROJECTS<br />

Many people on board liked to do their own projects, e.g. Tom Paris and the Delta Flyer. Use the form<br />

below to track your progress on your own projects:<br />

The PC names the project, writes the abstract and decides what skills they will use (if any!).<br />

The GM will decide the level of complexity of the project, how long it will take and what requirements<br />

there are.<br />

The PC may then decide what corners to cut or if they require help. The PC may increase the times if<br />

they wish. (e.g. <strong>Star</strong>fleet guidelines state I should soak test new software for 48 hours, but I will do it<br />

for<br />

The PC may decide that they know what they are going to do and do not need any preliminary work<br />

and go straight into implantation. Without an FDS though you cannot present your wonderful idea to<br />

anyone else in the crew and will not be taken seriously.<br />

The PC may decide not to do any testing and go straight into using the thing they have made. There<br />

is a good chance the thing will not work though and this increases with complexity. Also, without a<br />

signed off test procedure your new invention will not be adopted by the crew.<br />

Note that at the ‘end’ of the project you may not have a success, but this will depend on various<br />

factors that the GM may or may not share with the player. Even something that has been tested may<br />

not work in the field. The more testing that is done the better and the higher the complexity of the<br />

project the more issues it is likely to have once it is finished.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!