Spring RTS Engine

Instead of disabling widgets in certain games, it might be worth exploring to just disable widgets from issuing commands/orders to unit. This could include state changes.

I think this could be done quite easily already by overriding the default functions that give orders directly in widgethandler, and forcing that widgethandler to be used.

there is a command already to block widgets to issue orders, it's called /nohelp

but i guess you want more fine control

Brain Damage wrote:there is a command already to block widgets to issue orders, it's called /nohelp

but i guess you want more fine control

A user has to issue that command afaik, I'm talking about the game controlling this behavior.

so the engine should support certain stuff (like customformations,...) instead of a widget

manolo_ wrote:so the engine should support certain stuff (like customformations,...) instead of a widget

Or the limit could apply only to outside-of-game widgets.

customformation occasionally crashes in gundam.

uncomment this in engineoptions.lua and it will be shown in the lobby as option

{
key = 'NoHelperAIs',
name = 'Disable helper AIs',
desc = 'Disables possibility for luaui to issue orders',
type = 'bool',
def = false,
},

Brain Damage wrote:uncomment this in engineoptions.lua and it will be shown in the lobby as option

Still needs a way to allow mod-side widgets to issue orders.

Regret wrote:Still needs a way to allow mod-side widgets to issue orders.

Maek them gadgets!

Regret wrote:Instead of disabling widgets in certain games, it might be worth exploring to just disable widgets from issuing commands/orders to unit. This could include state changes.

Many people claim that merely giving more info is already an unbearable level of cheatery.

And I don't want a new setting to break widgets. I can see plenty of people getting WTF over widgets not working and then blaming the widget instead of Regret.