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

Add a Stop AI cheat #4768

Closed
DorpsGek opened this issue Sep 12, 2011 · 6 comments
Closed

Add a Stop AI cheat #4768

DorpsGek opened this issue Sep 12, 2011 · 6 comments
Labels
component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) patch from FlySpray This issue is in fact a Patch, but imported from FlySrpay

Comments

@DorpsGek
Copy link
Member

duizendnegen opened the ticket and wrote:

Trunk version 22854

Attachments

Reported version: trunk
Operating system: All


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

duizendnegen wrote:

Removed the bool show_stop_ai in AIDebugWindow
Fixed reverted patch

Attachments


This comment was imported from FlySpray: https://bugs.openttd.org/task/4768#comment10350

@DorpsGek
Copy link
Member Author

duizendnegen wrote:

Increased save version
Replaced tabs with spaces

Attachments


This comment was imported from FlySpray: https://bugs.openttd.org/task/4768#comment10352

@DorpsGek
Copy link
Member Author

Zuu wrote:

I've skimmed through your code and have these comments:
- The function isAIStopable have to be renamed as IsAIStopable to confirm with the coding standards.
- I don't see why you have a cheat that enable/disable using of a debug action. If you want to have it as a sheet, I would think the stop AI action should be available in the cheat dialog (eg. a popup window that asks the user to pick a company). In the debug window it doesn't make sense to involve cheating.
- I think your patch don't disallow using the "stopai" console command even if your cheat is not enabled.


This comment was imported from FlySpray: https://bugs.openttd.org/task/4768#comment10457

@DorpsGek
Copy link
Member Author

Zuu wrote:

However, if one thinks that stopping AIs should require a cheat, then I would suggest that if the gui.ai_developer_tools setting is enabled, no cheating should be required. Then make it consistent so that a user needs to either use cheats or the ai developer setting to gain access to stopping AIs through both GUI and the console.

I would also be fine if you auto-cheat for me if I have the AI developer setting active in order to block that users use that setting to bypass the cheat mark. As long as it doesn't get in the way of AI debugging.


This comment was imported from FlySpray: https://bugs.openttd.org/task/4768#comment10458

@DorpsGek
Copy link
Member Author

DorpsGek commented Nov 8, 2011

Rubidium wrote:

In what was is the console command not sufficient? If it is for AI debugging, then reloading would probably be the thing you'd always be wanting to do, right?


This comment was imported from FlySpray: https://bugs.openttd.org/task/4768#comment10488

@DorpsGek
Copy link
Member Author

DorpsGek commented Apr 5, 2013

Rubidium closed the ticket.

Reason for closing: Won't implement


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

@DorpsGek DorpsGek closed this as completed Apr 5, 2013
@DorpsGek DorpsGek added component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) wontfix patch from FlySpray This issue is in fact a Patch, but imported from FlySrpay labels Apr 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) patch from FlySpray This issue is in fact a Patch, but imported from FlySrpay
Projects
None yet
Development

No branches or pull requests

1 participant