sorry, i wasn't very clear...
the process is just the same as cloning any other location - copy the definition of the location in the locationsinit folder and give it a new id, etc etc. (you don't even have to copy the model if you don't want to, you can leave the definition pointing to the same model file.) the only difference is that for shore locations, it looks for a 'foam' file in RESOURCEfoam.
if the path of the model of the location you're cloning is resourcemodelslocationsoutsideshore_ship, then the program will look for the foam file in resourcefoamlocationsoutsideshore_ship. <b>if you copied the model, you have to copy the foam directory (and give it the same name). if you're using an existing model, then you should use the existing foam directory.</b>
in that directory there is an .ini file and a .tga.zap file. copy them both, and give the copies your new location's id as their filename, obviously keeping the .ini and .tga.zap extensions.
then, it should work as normal <img src="http://www.piratesahoy.com/forum/style_emoticons/<#EMO_DIR#>/happy.gif" style="vertical-align:middle" emoid="^_^" border="0" alt="happy.gif" />