Ok,

Situation, Players got ahold of the KFang via various means. THrough endeavours and favors had someone slice the ID of the ship so it can be renamed and have a new ID.

Do docking facilites check for such things? Imperial check points? Do scanners have hull recognition?? that can cause a mismatch? Are ID's associated with a log or history of dock registrations whenver they pay a docking fee?

If i was to make some type of opposition roll to see past the re ID'ed ship.. what would i be rolling against?

The Slicers skill VS what?...

Docking facilities - depends on the dock how much scrutiny it might bring. In the Rim, may just be a name on a spreadsheet without a second thought. In the Core - if something looks weird, they may look closer. If things look good, they probably won't assume it isn't legal.

Imperial check points - if something looks weird, they may investigate. If things look good, they probably won't assume it isn't legal.

Do scanners have hull recognition - I mean, you probably don't want a ship ID matching a Nebulon frigate on a YT-1300, because it'd be weird. But considering ships are built in factories (much like cars) I'd say most things look the same except for the VIN number and cosmetic wear-and-tear or upgrades. It probably isn't practical to keep a log of what every ship looks like, because that could change as soon as it changes owners. The VIN number would probably stay the same even if the name and appearance change.

Are IDs associated with a log? Yes, there's an organization that has maintained ship records for millennia that not even the Empire controls because the Emperor knows it would be too much work to replace them. I forget the name though. Mayne not EVERY time they pay a docking fee. Just depends on reporting - common in the Core, less common in the Rim, etc.

Opposition roll? Probably make a note of the roll of the slicer who changed the ship ID number. Sux = difficulty; Advantage = Setbacks on the roll to "see through it." The person trying to see through it would probably also roll Computers.

I had exactly this with my group. There are supposedly transponders on each ship that identify it, but a hacker can change this ID, or create multiples. However, to do so they have create a transit history that isn't completely improbable.

I put it at Daunting (it can't be something any old geek could do), but they had a lot of time and plenty of equipment, so a couple boost die were added.

Once they arrived at Ryloth though, Trex was "expected" by some of his Trandoshan friends, plus an Imperial agent looking to offload some battle droids to Teemo. So there was plenty of "mistaken identity" social roleplay for the next couple days, until Trex found a way to Ryloth himself and all hell broke loose...

I like some of the above, but here's some junk to rattle around...

The transponder code is linked to the drive (might be the power core, but I'm pretty sure it's the drive) and then registered with the Bureau of Ship Services (a buracracy so big and nasty even the Empire said "yeah lets just leave that like it is").

BoSS has to update it's records regularly, so anytime the ship get's a new captain, has any major modifications made, or whatnot these must be submitted to BoSS (BoSS must be clogged with commercial short duration flight captain updates). So there's SUPPOSED to be a history on file with BoSS, how accurate and up to date this is... that's something else entirely.

Docking facilities and customs check these, but how closely they do varies. Some busy ports might do random inspections, and deep checks, while backwater borderline shadowport security usually have more important things to worry about.

Unless the ship had some kind of specific modification to it's hull that would be noted on it's BoSS record it would be very hard to do a match that way. (Alternatively if the PCs get into some Imperial entanglements they might end up on an intelligence report and update to regional commands, which is a bit better and more efficient then BoSS)

Most transponder mods attempt to tweak the transponder of a "dirty" ship to match the transponder of a "clean" one, combined with some forged captains docs to match. So THAT could cause problems if the clean ship isn't so clean (or it happens to already be docked three bays down).

for rolling I'd do something like this:

Mechanics or computers to mod transponder.

Negotiation or computers to jigger the BoSS documentation.

The results would then be used as a modifier toward Deception checks made by the players when trying to pass off their ship as another.

IFF Mod:

Advantage means the code is solid (boost to deception)

Threat means it's fuzzy (setback)

Triumph means you get a BOGO! Make 2 BoSS update checks!

Despair means the transponder is shakey and could die at any time (save that one for later...)

BoSS jigger:

Advantage would be good work (boost or auto-1-advantage depending on how many)

Threat would just be minor errors (setback or auto-1-threat)

Triumph would mean the "clean" ship in question was in especially good standing (upgrade Deception).

Despair would mean the "clean" ship was actually dirty, and it's only a matter of time before someone notices (Deception upgrade difficulty)...

I'd stop worrying about it after docking your ship a few times or a couple of inspections. At some point the ship begins to leave a paper trail with it's new identity and no one questions it anymore.

Then again, it could always be something a GM keeps in his back pocket for a rainy day.

Then again, it could always be something a GM keeps in his back pocket for a rainy day.

Oh yeah, definitely a good thing to have.

The basics From my game the players had to hire a forger to create the new BoSS documents on thier new ship, a slicer to get it in. And a mechanic to modify the baffles on the engines to make it a new. Ended up costing 10k credits. All would have been daunting skill checks if the players had to do themselves.