yes thats what i have done with my ships. Also changing the promotion of naval trade to increase cargo while removing firepower makes all transport ships usefull. Change withhdraw chance, higger (30%) for small ships and lower (5%) for large bulk ships makes all viable. Change prices of ships to make a big difference from small to large, and remove the idiot restriction of making treasures only fit in galleons... all naval ships carry all cargo back in the day of sailing ages!
Yes, and any other player tune it to their views. thats the beauty of modding single player games. Everyone wins!
Actually internal version (to be WTP 4.1) is very stable.
Thats why developers should call those bugged versions as BETA!!! so players test the game and report bugs!Actually internal version (to be WTP 4.1) is very stable.
It is just not yet public.
------------------
Guys, it is normal that every new release is a bit more instable after a big feature release ... and WTP 4.0 was extremely big.
Then all the players play, people report bugs, modders fix bugs and it gets stable again ... until the next feature release.
It is just that magically people seem to forget which bugs we had directly after publishing WTP 2.8 or WTP 3.0 ...
But you cannot compare a situation fresh after release (before bugfixes) with a release that is already mature (having had bugfixes) ...
Is software development really that hard to understand ?
Major Feature Release --> You will have bugs ---> Bugs get reported and fixed --> Bugfix Releases get published --> It gets stable again --> Next Major Release ...
So if you really do not want to risk playing with bugs, then wait half a year after the major release until the bugs were fixed ...
That is e.g. the reason I personally also buy most of the major titles only about 2 years after release ... because then there are already patches and DLCs.
-------------------
So please, I am really a bit tired of hearing with every new release that it is more buggy than the previous.
That comparison is simply nonsense ... because it depends on the software lifecycle of the release (young release vs mature release).
Actually in WTP 4.0 we had fixed massive amounts of bugs that were reported over the years in WTP 3.0.
WTP 4.0.x is simply still a young release but WTP 4.1 (3 months later) will / should have made it much more mature already.
---------------------
So please relax a bit - it is unnecessary to repeat the obvious that a young feature release does have a few bugs ...
Because basically community is complaining that we are actually doing software development and creating new content ...
It is like shouting at a cook when he brings you a freshly cooked soup out of the kitchen:
"It is HOT ! ... That old soup over there that is 15 minutes old is not as hot !"
--------------------
Maybe try to understand a bit how software development actually works.
In a young major release will always have more bugs than many months later in the bugfix releases ...
And please nobody tell me there were no bugs in WTP 3.0.1 ... I know how often people complained about CTD.
Or why did people otherwise always ask for bugfix DLLs from internal development for WTP 4.0 ?
--------------------
Have some patience and wait until WTP 4.1.
Or get the internal development builds - like half of community meanwhile does anyways ...
Being frustrated at us modders that a young major release is not as mature as an old bugfix release is a bit irrational.
That is the nature of software development and the reason why most non-hardcore-fans also wait for a few months before they buy a game.
We did have beta testing, but for for whatever reason despite it being played, crashing bugs were not reported before we finished the beta stage.
Calling a public release a "beta" only makes sense if there is something like a "final release" planned - which is not how we see this project.
Silence wont help this awesome mod get better! its just opinions, nothing personal.Actually internal version (to be WTP 4.1) is very stable.
It is just not yet public.
------------------
Guys, it is normal that every new release is a bit more instable after a big feature release ... and WTP 4.0 was extremely big.
Then all the players play, people report bugs, modders fix bugs and it gets stable again ... until the next feature release.
It is just that magically people seem to forget which bugs we had directly after publishing WTP 2.8 or WTP 3.0 ...
But you cannot compare a situation fresh after release (before bugfixes) with a release that is already mature (having had bugfixes) ...
Is software development really that hard to understand ?
Major Feature Release --> You will have bugs ---> Bugs get reported and fixed --> Bugfix Releases get published --> It gets stable again --> Next Major Release ...
So if you really do not want to risk playing with bugs, then wait half a year after the major release until the bugs were fixed ...
That is e.g. the reason I personally also buy most of the major titles only about 2 years after release ... because then there are already patches and DLCs.
-------------------
So please, I am really a bit tired of hearing with every new release that it is more buggy than the previous.
That comparison is simply nonsense ... because it depends on the software lifecycle of the release (young release vs mature release).
Actually in WTP 4.0 we had fixed massive amounts of bugs that were reported over the years in WTP 3.0.
WTP 4.0.x is simply still a young release but WTP 4.1 (3 months later) will / should have made it much more mature already.
---------------------
So please relax a bit - it is unnecessary to repeat the obvious that a young feature release does have a few bugs ...
Because basically community is complaining that we are actually doing software development and creating new content ...
It is like shouting at a cook when he brings you a freshly cooked soup out of the kitchen:
"It is HOT ! ... That old soup over there that is 15 minutes old is not as hot !"
--------------------
Maybe try to understand a bit how software development actually works.
In a young major release will always have more bugs than many months later in the bugfix releases ...
And please nobody tell me there were no bugs in WTP 3.0.1 ... I know how often people complained about CTD.
Or why did people otherwise always ask for bugfix DLLs from internal development for WTP 4.0 ?
--------------------
Have some patience and wait until WTP 4.1.
Or get the internal development builds - like half of community meanwhile does anyways ...
Being frustrated at us modders that a young major release is not as mature as an old bugfix release is a bit irrational.
That is the nature of software development and the reason why most non-hardcore-fans also wait for a few months before they buy a game.
What distincts a Beta from an Alpha, is that a Beta is feature complete but not bugfixed (completly), while an Alpha is open for adding features and not bugfixed at all...(bc its in its development phase)Calling a public release a "beta" only makes sense if there is something like a "final release" planned - which is not how we see this project.
Also let us please not overexagerate with "bugged versions" like the mod was not playable at release ...
The concept of betas may apply to commercial products, but seriously what is a beta supposed to be in a mod project where development is ongoing since 15 years ?
Can we please stop discussions in "consumer attitude" again before we get all the modders pissed and annoyed again ?
---------------------
Should we call every major release "beta"?
And when do we stop calling it "beta" - in 10 years ... in 15 years ... or when ?
We simply still develop new content with every major release.
And when you do you may simply have bugs in it.
That is the nature of modding ... as it is just continous development ... for which we sometimes have releases so people can play without compiling a development branch themselves ...
Continously new stuff is being added and continously existing stuff is being improved or fixed ... until at some point modders run out of motivation ...
There is no single point which grants the performance boost. It's the sum of many unrelated changes. Yes using tbb.dll to enable more CPU cores is indeed a significant boost. However the old fashioned approach to boosting performance is rewriting code to do the same as the old code, but using fewer CPU instructions. Since we have done both, it's not really possible to tell how much of the performance boost comes from each approach to improve performance. Luckily it really doesn't matter because what matters is the perceived performance.
Currently just +1 Health as City Location.
