If the user imports a .fpk file, its contents should be imported into the project in the proper directory (i.e., with "Assets" at the root). In addition, it should create a "Archive Definition" asset which for now will be a placeholder, but which will eventually be used as the mechanism through which archives are exported.
The matching .fpkd file, if there is one, should also have its contents imported.
It does not currently appear to be possible to get the source path of an asset when importing it, so automatic importing of the .fpkd doesn't appear to be possible at the moment.
If the user imports a .fpk file, its contents should be imported into the project in the proper directory (i.e., with "Assets" at the root). In addition, it should create a "Archive Definition" asset which for now will be a placeholder, but which will eventually be used as the mechanism through which archives are exported.
The matching .fpkd file, if there is one, should also have its contents imported.