fresh install: /info and advanced playerlist both active

[knorke]

Via weblobby I installed spring and BA on a computer that had never before seen Spring. (so it is no old configs etc)

The engine playerlist (toggle with /info command) and widget playerlist were both active and on top of each other.

[Silentwings]

We could include a script that does /info and disables the engine default; the problem is determining accurately if it is the first time that this BA version has been run on that particular Spring install. I could do it in hacky style by leaving notes in the file system but I don't want to do that - got any ideas?

[Funkencool]

Why only first time? Couldn't you just include spring. Sendmessage("info 0" in the widget so they can't exist at same time?

[Silentwings]

Since advplayerlist is loaded by default that would mean probably new players never saw the /info option. But I do know that some people like and use /info over advplayerlist, so I wondering if there was a way that gave people an obvious choice between the two.

That said, what you suggested is clearly the easiest option and would be better than what we have now.

[Silentwings]

Done - ShowPlayerInfo is unloaded if it is active when advplayerlist initializes (and only when it initializes)

[zwzsg]

With /info 0 in the widget:Initialize
and /info 1 in the widget:Shutdown
the player doesn't need to know the /info command, but only how to toggle a widget
Which he has to know anyway to disable the widget.