How do these interact when coming from different sources? IE the Modder and Rigger specs.
Must the character pick two different ships for the Signature Vehicle, will it apply twice to the same ship, or will the better of the two apply?
Could the character skip the second Signature Vehicle and choose to just take more than the original 2 of Larger Project, allowing for ships larger than Sil5 to be used as a Signature Vehicle?
From what I understand, talents stack unless they say otherwise, but I could be easily wrong, which would seem to imply at least the Signature Vehicle of 6 or 7 could be possible.
Larger Project/Signature Vehicle
I would say that sil 6 and 7 are definitely allowed, as the talent is ranked. But the character can only get signature vehicle once, since it is not ranked. On the second tree, you would skip that space.
I would say that sil 6 and 7 are definitely allowed, as the talent is ranked. But the character can only get signature vehicle once, since it is not ranked. On the second tree, you would skip that space.
That's kinda what I was thinking but wanted to hear from some people on it
The description says you upgrade your ship or vehicle "once", not "once per rank" as it does in the talents meant to stack. I would think they have to be different vehicles.
Notice that in the Modder talent tree, you can get to the talents that build onto Signature Vehicle without taking the actual Signature Vehicle talent. You could theoretically take Know Somebody and then move to Fancy Paint Job and then take the Larger Project talents. If someone did that I think it would be fair to have talents from both trees apply to the same vehicle.
Notice also that Fancy Paint Job is a side talent in the Rigger tree and doesn't lead to any other talents, making it easy to skip if you're doubling up on these trees. The wording of Fancy Painf Job is similar to that of Signature Vehicle in that it implies that the talent doesn't have stacking ranks, so you wouldn't want that talent twice with only one signature vehicle.
It almost looks like the designers did that on purpose... ![]()
ETA: Letting the player skip redundant talents also seems fair as suggested above.
Edited by AtamaThe description says you upgrade your ship or vehicle "once", not "once per rank" as it does in the talents meant to stack. I would think they have to be different vehicles.
Notice that in the Modder talent tree, you can get to the talents that build onto Signature Vehicle without taking the actual Signature Vehicle talent. You could theoretically take Know Somebody and then move to Fancy Paint Job and then take the Larger Project talents. If someone did that I think it would be fair to have talents from both trees apply to the same vehicle.
Notice also that Fancy Paint Job is a side talent in the Rigger tree and doesn't lead to any other talents, making it easy to skip if you're doubling up on these trees. The wording of Fancy Painf Job is similar to that of Signature Vehicle in that it implies that the talent doesn't have stacking ranks, so you wouldn't want that talent twice with only one signature vehicle.
It almost looks like the designers did that on purpose...
ETA: Letting the player skip redundant talents also seems fair as suggested above.
So another vote on "Larger Project stacks, the rest does not"?
Time to go make Scotty and make him the CEO of a cruiser somewhere~
If you read the full description of Larger Project in the Talents portion of Stay on Target (not just the spec tree), you'll see it say that Larger Project is ranked. Fancy Paint Job is not ranked. Signature Vehicle is not ranked and thus you can only have one Signature Vehicle. The CRB also states that if you own a Talent that is not ranked, you count as having it on any other tree that the talent exists on.
What that guy said. I could only have said it wordier myself!
Unranked talents of the same name (ie Signature Vehicle) can only be purchased once. If a PC later reaches the same talent in another tree they may immediately tick that instance of the talent off for no XP cost.
But you have to reach the talent from the top of the new tree, it doesn't let you start half way down.
I honestly can't stress how valuable the Talents chapter of each book (CRB and sourcebook) is. So much confusion can be avoided if one reads it as they read over each specialization. The Talent descriptors in the spec trees only have so much space and the Talents chapter will tell you if a given Talent is ranked or not.
I honestly read its description in the talents chapter, in each book even, and missed the word ranked both times >.< I'm sorry for that incredibly noobish mistake.
Thank you much though!
If you want a visual using my character generator, create a new Ace/Rigger, then check Gearhead and Signature Vehicle. Then, add the Modder specialization. If you notice, looking at the Modder tree, Signature Vehicle, at the top, is automatically selected. That's because, as a few people have mentioned, non-ranked talents only need to be purchased once. If you come across them in another tree, they count as being purchased as soon as you get access to them.
So... only one Signature Vehicle (its unranked), but the ranked talents that go with it, from whatever tree has them, will keep upping their effect the more ranks you purchase.
This raises a related question. So let's say you're a Modder, you get the Signature Vehicle talent. It lets you choose a vehicle of silhouette 3 or lower so you select a starfighter craft your group has. A few sessions later you have enough XP to buy the Larger Project talent. Can you "trade in" for that YT-2400 the group is flying around in? The book implies that you can't, and only gives you the opportunity to do so if the original vehicle is "lost or destroyed". How would you handle that?
Personally I'd warn a player choosing this talent that they'd better think ahead before deciding on a vehicle because they're making a commitment to it. If they really want a larger ship then hold off until they can afford the Larger Project talent.
I went through something similar lately with Jury Rigged on my PC. I used it originally to make a vibroblade critical cost 1 advantage. Which seemed handy at the time but I ended up almost never using it. Later I wanted to "reinvest" the talent in a new blaster I'd bought. I disposed of the vibroblade by gifting it to an NPC friend, with the in-game justification that the knife was originally a gift from a Hutt who had become an enemy (which is true, the knife was a reward for a job in one session) and he hated carrying it as a reminder. By giving it away, I considered it "lost" and my GM was okay with that.
I was wondering how others felt about this sort of situation.
I would require some campaign downtime to transition. All the benefits are lost by the old signature vehicle, and passed onto the new vehicle. Perhaps a week would be enough, either in Hyperspace, or just hanging out waiting for the next part of the story. so yes i would allow it, but not something to swap back and forward on a regular basis.
I would require some campaign downtime to transition. All the benefits are lost by the old signature vehicle, and passed onto the new vehicle. Perhaps a week would be enough, either in Hyperspace, or just hanging out waiting for the next part of the story. so yes i would allow it, but not something to swap back and forward on a regular basis.
I would expand on this and say a week per Sil of the new vehicle, unless they are somehow similar, which if they're changing Sil I'm not sure how they would be, but in that case at least a week per difference in Sil? Otherwise I agree with this.
I would just consider the "lost" part super super vague, to the point where "I've lost the desire to mod this ship" would count in the case of a RAW lawyer lol But coupled with the above transition time, I think the book actually suggests it may take time to implement anyway.
But coupled with the above transition time, I think the book actually suggests it may take time to implement anyway.
It does. Per the description of Signature Vehicle, "The process of modifying and acclimating to the new vehicle may take some time at the GM's discretion."