Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I try to do a blockade for very first time on Norfolk.
And the harbour is not marked as blocked.
So what should i do ? because it seems my blocade does not work.
Suggestions are welcome.
https://steamcommunity.com/sharedfiles/filedetails/?id=2820327331
What do you mean by hit to trade ?
Looks like Norfolk is blockaded just fine there.
Norfolk itself doesn't have a port of the same name. Its port is Gosport, just to the south of it. Which is clearly blockaded in this screenie.
So it seems to be worth putting your fleet in places where you can get a high coverage but also heavily blockade a single high value port.
Obviously not a good idea to try that if there is a fort nearby though.
During last campaign, my Gosport was blockaded, but CSS Virginia kept building. I was also able to form a fleet of Frigates there.
I did notice that I was NOT able to form fleets at many other blocked smaller ports, including the nearby (West Point, Rocket Landing, Onancock) which were blocked by the same Union fleet. But Gosport was open for such.
So perhaps has something to do with blockade % and port tier?
Also occurred to me that CSS Virginia is already building at Summer '61 start. And of course Gosport is not already blockaded on Day 1. So maybe I wouldn't have been able to *start* another casemate ironclad under blockade, but already-started ships still continue?
lol or maybe it was just a bug...heh, it was beta version, after all. :-)