Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Foundations should not be placed on the water #6184

Closed
DorpsGek opened this issue Dec 6, 2014 · 6 comments
Closed

Foundations should not be placed on the water #6184

DorpsGek opened this issue Dec 6, 2014 · 6 comments
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

DorpsGek commented Dec 6, 2014

McZapkie opened the ticket and wrote:

Foundations of bridges, roads/tracks are placed on water if coast is diagonal,
and therefore very high payment is deducted due to forced water clear function, see images.
I consider it as a unwanted feature/bug, because (in case of road/tracks) it silently drain money from unaware player.
Especially harassment in case of high water clear base costs.

The solution is to disable foundations on water and let players to terraform coast manually if they really need.

Attachments

Reported version: 1.4.4
Operating system: All


This issue was imported from FlySpray: https://bugs.openttd.org/task/6184
@DorpsGek
Copy link
Member Author

DorpsGek commented Dec 7, 2014

planetmaker wrote:

The manual terraform is not an option as that is even more expensive: when you raise a corner of a tile, you change all 4 adjacent tiles. Building a bridge head only changes the one you build the bridge head on.

If you don't want to be caught unaware, use the cost estimation via shift+build before you actually build.
-1 to any change to this as it only adds to the burden to build what one desires and makes doing so more lengthy.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6184#comment13650

@DorpsGek
Copy link
Member Author

DorpsGek commented Dec 7, 2014

McZapkie wrote:

In case of bridge on diagonal coast, you can lower one corner and it cost same money as foundation (one tile is affected).
In case of above screenshots with road foundations on the corner of the coast,
which are a main issue because of stealthy money draw (shift is not an option for checking ordinary road costs if somebody don't know about described problem), raising corner manually draw also same money as foundations.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6184#comment13651

@DorpsGek
Copy link
Member Author

DorpsGek commented Dec 7, 2014

frosch wrote:

You cannot solve the problem by lowering corners.
Consider the 2c screenshot at https://www.tt-forums.net/viewtopic.php?p=1138198# p1138198 . You would need to terraform a long strech of tiles if lowering.

Raising corners would always solve it, but it would be very expensive.

Anyway, I tend to just not charge for clearing water when building foundations. As far as I can tell it cannot be exploited for bigger areas of sea, since the diagonally neighboured tile will always remain full water, so you cannot raise the corner without cost.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6184#comment13652

@DorpsGek
Copy link
Member Author

DorpsGek commented Dec 7, 2014

Alberth wrote:

Clearly there is a lack of understanding what "high water clearing costs" mean. Maybe make a page that shows the implications?

People go in here knowing that water clearing is expensive. Apparently, they assume they understand what it means, or they would ask about it.
The graphics show you're going to touch water, in case of bridge you're having a high cost value. There is a cost estimate available if you are not sure. The game is making all information available. There is nothing hidden or silent, the game reports it all if you're careful enough to actually get or read the information. If you instead decide to ignore everything and don't care, yeah you get hurt.
It's not different from experiencing that you need to take care what routes you make or you'll go bankrupt, and trains can crash if you play with signals on a live track.
You only learn that by trying it anyway, and getting hurt by the game.

If you add an extra hurdle, you are hitting all players that knowingly do the action because they want to build it. An extra hurdle won't stop people that don't understand, since they fail to understand why the game refuses the action as well (ie it plays like not-normal, but that gives no clue why it behaves like that).

Maybe the problem is that the costs aren't high enough? If you make them sufficiently high, a user doesn't have enough money to do it. Another option is to make a map that does not have these edges.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6184#comment13653

@DorpsGek
Copy link
Member Author

DorpsGek commented Dec 8, 2014

McZapkie wrote:

Above attached examples were shown, for definiteness, with standard base costs.
This thread resulted from high terraform costs, which are often necessary, but have negative drawback in case of accidental water clear procedure.

Because above arguing against my proposal seems to be relevant, moreover bridges/road foundations are not the only possibility of accidental huge money draw, I'm convinced that this task should be closed as rejected.
There should be different, more general mechanism for accidental money loss protection.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6184#comment13654

@DorpsGek
Copy link
Member Author

Rubidium closed the ticket.

Reason for closing: Deferred

As requested by the creator of this ticket.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6184

@DorpsGek DorpsGek added Core flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) labels Apr 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Development

No branches or pull requests

1 participant