Locking interface = bad idea

[Regret]

Your current UI is terribly ugly, forcing people to use it is illogical.

[Jazcash]

Yes, I suggest you make Lol UI the default forcing CA's community to shrivel up in fear.

[SirMaverick]

Users have local widget like IceUI that will interfere with CA's interface. That leads to strange things like having 2 consoles etc. That's why blocking local widgets was considered.

It's only in testing version. That's what test is for. Testing new ideas etc.

In later versions it's planned to integrate a override flag for local widgets.

[Regret]

Users have local widget like IceUI that will interfere with CA's interface. That leads to strange things like having 2 consoles etc. That's why blocking local widgets was considered..

It is the problem of users that they installed said widgets, you can just make a widget to disable the new UI if it detects an already enabled instance of IceUI, it worked well in BA.

[Neddie]

This doesn't interfere with my use of the normal GUI with a custom ctrlpanel, does it?

[SirMaverick]

This doesn't interfere with my use of the normal GUI with a custom ctrlpanel, does it?

No.
EDIT: Just played first test game. The build menu is already disabled in test.

[Neddie]

Well, since nobody has offered anything better I'll just continue to use that. Problem solved.

[MidKnight]

Your current UI is terribly ugly

NEEDS MOAR SKINNING!

Go help jK with the skinning code please.

[jennington]

I don't see a reason to take options away. Props for adding a new one, I like where you're going with it, but let players choose. If you're so worried about something breaking because of that, you can always make a big red warning text appear when enabling a local widget, or something like that - whatever. The final choice should still be the players.

We just played a few games with the new UI enabled and other players had very similar opinions. I really think it will drive potential players away if they _have to_ learn something completely new just to play this mod, and even after learning it, some _will_ end up disliking it. You can't please everyone.

[Licho]

Its this way just in test. Stable is still the same and will be until chili is done and polished.

[Licho]

But in the long term we cannot really adjust for all the possible local widgets/configurations.

All sort of problems can be caused by widgets downloaded initially for BA that activate in CA..
Ranging from annoynaces to huge performance drops and complete freezes.

We just cannot manage it anyhow. And many even standard widgets (like custom formations, advanced players list) have to be modified specially for CA.

And menu is not compatible unless tweaked. Neither ice nor lol or redui support CA's lua buttons.

So in the end local widgets will be disabled unless you do soemthing special, like putting file called "i_know_what_am_i_doing.txt" containing your name into your spring folder.

[Neddie]

But in the long term we cannot really adjust for all the possible local widgets/configurations.

All sort of problems can be caused by widgets downloaded initially for BA that activate in CA..
Ranging from annoynaces to huge performance drops and complete freezes.

We just cannot manage it anyhow. And many even standard widgets (like custom formations, advanced players list) have to be modified specially for CA.

And menu is not compatible unless tweaked. Neither ice nor lol or redui support CA's lua buttons.

So in the end local widgets will be disabled unless you do soemthing special, like putting file called "i_know_what_am_i_doing.txt" containing your name into your spring folder.

Entirely reasonable, 1944 has planned for similar in the long term.

[Regret]

But in the long term we cannot really adjust for all the possible local widgets/configurations.

All sort of problems can be caused by widgets downloaded initially for BA that activate in CA..
Ranging from annoynaces to huge performance drops and complete freezes.

We just cannot manage it anyhow. And many even standard widgets (like custom formations, advanced players list) have to be modified specially for CA.

And menu is not compatible unless tweaked. Neither ice nor lol or redui support CA's lua buttons.

So in the end local widgets will be disabled unless you do soemthing special, like putting file called "i_know_what_am_i_doing.txt" containing your name into your spring folder.

Entirely unreasonable. Are you also going to scan users pc for software / downloads that might be slowing the game down?

Advanced player list does not need to be modified to work with CA, nor custom formations, ridiculous claims.

I have played CA with all those widgets enabled only locally and they work flawlessly, even now. And even using my custom menu / resource bars.

The buttons/menu compatibility that you speak of are area mex and other widgets which are totally unnecessary for playing.

You are making baseless shit up. And you are scaring away even more players with your idiotic approach.

[Licho]

Custom formations must be modified to allow marking menu.
Advanced lpayer list to integrate ceasefires/diplomacies.

[Regret]

Custom formations must be modified to allow marking menu.
Advanced lpayer list to integrate ceasefires/diplomacies.

You wrote they have to be modified specially for CA, yet those features you just mentioned are completely unneeded, in fact I played with them just great for several months. So where is does this "have to" come from?

And why are you even bothering to account for user stupidity for installing widgets on his pc? The user is responsible for installed components, not you as a developer of the game.

It's just completely senseless.

Actually I'm not even going to argue this anymore, you have again managed to find a way to alienate the players that you are targeting.

First by trying hard not to be like TA, then by using an outright hostile releasing / distributing method (downloader) and now by forcing users to use a halfassed unfinished interface. I am aware it's a test version, but CA games are rare, and when they are played they are most of the time on the test version.

[MidKnight]

Custom formations must be modified to allow marking menu.
Advanced lpayer list to integrate ceasefires/diplomacies.

You wrote they have to be modified specially for CA, yet those features you just mentioned are completely unneeded, in fact I played with them just great for several months. So where is does this "have to" come from?

And why are you even bothering to account for user stupidity for installing widgets on his pc? The user is responsible for installed components, not you as a developer of the game.

It's just completely senseless.

Actually I'm not even going to argue this anymore, you have again managed to find a way to alienate the players that you are targeting.

First by trying hard not to be like TA, then by using an outright hostile releasing / distributing method (downloader) and now by forcing users to use a halfassed unfinished interface. I am aware it's a test version, but CA games are rare, and when they are played they are most of the time on the test version.

WHAT.

If a feature isn't needed doesn't mean it shouldn't be there. How about I remove the juno, the advanced radar and jammer, the shiva, the razorback, the sumo, the annihilator, the podger, its counterpart, and the zipper from BA? All of those units have counterparts in the same faction that do the same thing' they just make your life a bit easier and make it easier to win the game. Same with marking menu.

Next point:
We can't keep picking at the *A playerbase. To grow, we must search for players from outside of our little, close-knit group. We are not only now trying to get players from within the spring community, but are making strides towards becoming a game people not previously initiated to Spring can play.

Indeed, CA isn't like most of the *A mods, but those themselves aren't very much like TA either. You may want to reword your post. I'll take it that by TA you mean *A.

We don't try hard not to be like the *A; we try hard to tell people that we aren't the *A and shouldn't be viewed or judged as such.

What do you have against the downloader? It makes life easier for the devs, helps users keep their CA updated, and provides generally useful services. In fact, there are some people who prefer TASClient over SpringLobby chiefly because of the former's SpringDownloader integration.

Thirdly, please, don't judge by appearances. Chili is already a very complex and versatile framework, and once skinning support is finished and implemented, it will prove to be a very nice and pretty GUI indeed.

[Regret]

If a feature isn't needed doesn't mean it shouldn't be there. How about I remove the juno, the advanced radar and jammer, the shiva, the razorback, the sumo, the annihilator, the podger, its counterpart, and the zipper from BA? All of those units have counterparts in the same faction that do the same thing' they just make your life a bit easier and make it easier to win the game. Same with marking menu.

Strawman. But nice try.

We can't keep picking at the *A playerbase. To grow, we must search for players from outside of our little, close-knit group. We are not only now trying to get players from within the spring community, but are making strides towards becoming a game people not previously initiated to Spring can play.

Indeed, CA isn't like most of the *A mods, but those themselves aren't very much like TA either. You may want to reword your post. I'll take it that by TA you mean *A.

We don't try hard not to be like the *A; we try hard to tell people that we aren't the *A and shouldn't be viewed or judged as such.

Then rename. No use calling the game *A when it has little to do with it.

What do you have against the downloader? It makes life easier for the devs, helps users keep their CA updated, and provides generally useful services. In fact, there are some people who prefer TASClient over SpringLobby chiefly because of the former's SpringDownloader integration.

It is terrible, freezes often, does lots of useless shit at start, it's invasive and tries to make you install TS with annoying popups.

Thirdly, please, don't judge by appearances. Chili is already a very complex and versatile framework, and once skinning support is finished and implemented, it will prove to be a very nice and pretty GUI indeed.

I will judge an UI by appearance any day. If I can't orient in a UI it is useless for me, if it gives me eye cancer it doesn't make me want to play. And if I can't even disable it even though I have a superior alternative now that is just plain stupid.

[ash2life]

ok its enough now Regret - let it be - stop the hate - we got your point

[reivanen]

I really hope the day won't come when CA has blocked widget setup. The beauty of the spring engine is its total flexibility via widgets.

I kinda see where you come from with the restriction, but before you put it in like it is (was?) in test version, implement some override method for users who know what they are doing.

[Regret]

ok its enough now Regret - let it be - stop the hate - we got your point

Hate? This is feedback.