Warehouse capacity limits by type

[William one eye]

I consider part one of this implemented - player defined limits achieves the same goal


I would find the ability to place hard limits by cargo per warehouse by type very useful

By number of crates
Or by % percentage
Or possibly the abilty to select one or the other.

Percentage being more useful in a growing warehouse
And crate limit being more useful in a static size warehouse.

Total capacity. 10,000 crates

Cargo. Limit crates
Food. 3000
Tools. 150
Iron. 150
Cotton. 100
Tobbaco. 100
Rum. 200
Wood. 4000
Bar. 1000

Or

Cargo. %Limit of total capacity
Food. 20
Tools. 5
Iron. 5
Cotton. 5
Tobbaco. 5
Rum. 5
Wood. 25
Bar. 10


Part 2

Setting in trade routes to switch cargo type if warehouse
Limit is reached by incoming cargo.

So if you are bringing food from New land to Seaglory
And you hit the warehouse limit for food in seaglory. Your feet goes to a preset that you select

If limit reached sell to market
If limit reached change cargo type immigrants
If limit reached change cargo type gold bar.

Or it could even be taken 1 step further to preset an alternate route end or even multiple route ends by priority.

If limit reached change route. Select port select cargo


If limit reached for alternate route 1 change route. Select port select cargo


If limit reached for alternate route 2 change route. Select port select cargo

If limit reached for alt route 3 change route. Select port select cargo


If limit reached for alt route 4 change route.
Select switch cargo
Load immigrants

[Bomont]

Part 1 +10
Part 2 +1

I like both ideas, but would personally put a much higher priority on the warehouse capacity limits. There are a number of reasons I've wanted to do this and there isn't really a good work-around. Also, this seems like it might be easier to program?

Part 2 seems like it would go along with your previous idea for saving routes and if they are incorporated, coding both together makes sense?

[Sir frances drake]

Part 1: +1
Part 2: -1

I agree the first part would be very useful.

As for the second part, I think there should be a limit on how automated you can make your routes. Programming more and more so that you never have to touch them is a negative in my opinion. Part of having a large number of fleets is the downside of having to maintain that large number. It’s a give and take

[William one eye]

Part 1: +1
Part 2: -1

I agree the first part would be very useful.

As for the second part, I think there should be a limit on how automated you can make your routes. Programming more and more so that you never have to touch them is a negative in my opinion. Part of having a large number of fleets is the downside of having to maintain that large number. It’s a give and take

The second part becomes more relevant if the first part was implemented. As you may not be present at the time the capacity stop hits.
If you are managing a hideout and perhaps 1 facility this does not seem like a major issue. But if you are managing multiple facilities
and a hideout it is a lot more important.

This has more to do with ability to manage warehouses than the number of fleets you are running,
in fact this benefits those with fewer fleets just as much if not more than someone who has mass numbers of fleets.
For example if someone is running 8 trade fleets and 2 warehouse supply fleets and the warehouse supply fleets become ineffective due
to a full warehouse or a capacity limit, that is much bigger loss of resource use by percentage than someone who is running 80 trade fleets and 2 warehouse supply fleets.