>>95857231>Just remove the scalabilityAlright I see where you're coming from. The thing is, ACKS is intended to be scalable. The way you want it rewritten is the way it would've originally been written in something like B/X or Chainmail.
The thing is though, that doesn't tell you how to recalculate it if you want to. So if you change things then you're up shit creek.
Example, let's say my group wants to build a keep, rather than hiring a bunch of engineers they cut a deal with a local hill giant clan to buy some of their ogre slaves and hire a few giants to be their foremen.
I, as DM, rule that an Orge can do 5 sp worth of labour per day (Each Ogre being equivalent to 5 men) and that the Hill giants count as doing 2 gp worth of labour per day (Giant = 20 men)
One of my players points out to me that because they're bigger and doing the work faster the Daily construction limit should be higher as well, which is a completely fair point. It's not that there's a shitload of people working and getting in each others way, it's that they're using a different method of doing things.
I as DM make the ruling that using each Ogre only counts as 1 person for the cap limit, meaning the 'effective cap' for Daily construction when using ogres is different to that of humans.
Fine at the time.
Then one of my players decides he's going to seduce the Chieftainess of the Hill Giants.
6 levels later he's got an army of giants and ogres and wants to build a fortress fast as possible because the Local Lords have banded together and they're en route.
He turns to me and asks what's the cap if he pays all the giants in luxuries so they'll work through the night.
I turn to the book and:
>Increase by 125gp by paying extra 250 gp - Fuck, er, I->Reduce by 25% by paying 50% additional - Right so you were going to pay them 1000 GP per day, they'll get it done in 75% of the time for 1500 GP per day. DoneYou see the difference?