| 1 |
Basically the nonhost players cannot issue orders to the group's constructors unless they issue rapid move orders in succession (taking 2-3s to unjam a single con).
|
1 |
Basically the nonhost players cannot issue orders to the group's constructors unless they issue rapid move orders in succession (taking 2-3s to unjam a single con).
|
| 2 |
\n
|
2 |
\n
|
| 3 |
This behavior lead me to remove the widget upon the user commsharing. However that was reverted due to a typo in the commshare gadget's improvements causing some errors to pop up when a spectator joined in. This is resolved in [url=https://github.com/ZeroK-RTS/Zero-K/pull/4088]this pr though[/url]. GBC also breaks with commshare for the same reason.
|
3 |
This behavior lead me to remove the widget upon the user commsharing. However that was reverted due to a typo in the commshare gadget's improvements causing some errors to pop up when a spectator joined in. This is resolved in [url=https://github.com/ZeroK-RTS/Zero-K/pull/4088]this pr though[/url]. GBC also breaks with commshare for the same reason.
|
|
|
4 |
\n
|
|
|
5 |
[q]Ideally I could improve caretaker behavior with a widget that is accepted as default on by the devs.[/q]
|
|
|
6 |
\n
|
|
|
7 |
Better for it to be a gadget imo. Though this could lead to state clutter.
|
modifying caretaker behavior