anything against removal of lualobby?

[smoth]

a step in the right direction would be to make an library(API only, not UI) which is similar to the lualobby thing

koshi (dev of springlobby) already did that, afaik its a c++ lib. its just not released...


EDIT: also imo it would be better to add the ability to load .so/.dll's for extending the unsynced part (and maybe synced part?) of the engine so it gets more modular...

By library I meant an implementation in Spring lua using luasockets, native lua or engine code is the way to go.

Definitely, that is what I am going to work on if someone else doesn't I am going to create a luafile that will have functions and stuff to cover basic lobby stuff that way people don't have to use chili to have access to it. Even though, obviously I WILL use chili. This is a chance for me to get something going that the engine needs so I probably will start on it soon.

[SpliFF]

I'm confused. I was under the impression LuaLobby runs in the START SCREEN and luasocket runs IN GAME. These are totally different engine and lua environments. Assuming I'm right then consolodating that discrepancy would be non-trivial. It would mean supporting at least one of the following changes:

A.) Widget/UI lua state starts in start screen not on game start
or
B.) Skip loadscreen entirely and have a "placeholder" game load on spring.exe start

Personally I'd go for B as the start screen is poorly maintained and only really used by devs (using a lobby client means you skip it anyway).

Supporting A would mean adding new callbacks like OnStartScreen to handle skinning the interface and running the relevant luasocket / custom lobby code.

[smoth]

b would be nice but who is going to code it?

[knorke]

A or B doesnt really matter.
You can just have empty mod+map. Start it by making the desktop shortcut for players not link to spring.exe but to spring.exe with some startscript.txt. Does not really skip loadscreen but fast enough.
Maybe later there is a way to run spring lua outside started game (in menu, in loadscreens) but it isnt really needed for this.

[smoth]

no doubt but hey, we might like get it

[SpliFF]

Come to think of it I left out:

C. Simply add LuaSocket to startscreen lua environment. Although a seperate lua state it could communicate with game scripts via prefs. It's less elegant than A or B but far easier to implement.

[knorke]

It is funny how some people always wanted (to make/to have) an ingame lobby. Now with abma's socket thing it is possible but instead loling over new side problems.

[smoth]

I am not worried about it, I am just discussing other options abma told me all I needed to know the other day in sy.

[abma]

@Spliff:

Kernel Panic already has B)

[smoth]

we still have to deal with the load screens. It is a side discussion really, but jk has plans to do some kind of lua load screens and that really should be a side discussion outside of this one