Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Fleeting Frames]

Ambitious, I wish you good luck.

[MoonyTheHuman]

Yup, Necro time. This has been dead Forever, but dont loose hope. Im working on a DFhack plugin that can fake multiple GUIs. C++ is the bane of my existence, but i might as well try.

[Fleeting Frames]

As in, multiple players viewing and ordering around different sections of fort at same time?

If you do, that's going to be magma awesome.

[MoonyTheHuman]

As in, multiple players viewing and ordering around different sections of fort at same time?

If you do, that's going to be magma awesome.

Ideally, yes
Issue is, i have to write tons of GUI code by hand. Im probably going to use the C++ plugin for direct access, and offload the work onto an external script.

[Fleeting Frames]

Hm, since it's going to be web interface anyway, Warmist has some interesting work with early notes on Multiplayer [mostly for devs] and it's relatively recent implementation (Dwarf fortress multiplayer). I think mifki made some of the general interface he used to create mobile DF open too, as well as earlier just tile-by-tile display in Web Fortress.

But you probably know more than me on this topic atm.

E: Oh yeah, since it's going to be used for succession/multiplayer, perhaps ditch the vanilla labours interface and use just labor-manager/autolabor for that.

[MoonyTheHuman]

I'm going to be ditching most vanilla interfaces in favor of more complete ones.
I.e. manager will be replaced with workflow if possible.
Writing the map renderer itself will be a hilariously huge job.
Now that I've looked at that, i'll probably write the socket implementation in C++, and the rest in Lua, because that seems more sane. (Map Renderer will likely still be C++ tho, due to requirements)

[Fleeting Frames]

Well, you might want to look at /hack/lua/gui/dwarfmode.lua, maybe - it's mostly useful for modding, tbh, since you can't run game unpaused while lua viewscreen is up.

I'm not sure if others have done map renderer in the sense you mean, not having descended into it, but at least warmist's multiplayer is an example of multiple simultaneous different viewscreens. I'd ask about this in dfhack thread first, to be honest; others likely know more.


But more importantly, I'm not sure where the display would go, if you write it entirely in lua and C++?

And yeah, it's a bit ...daunting.

[MoonyTheHuman]

Looks like i dont need to write the renderer after all! Thanks for the pointer, Warmist.
I'll begin work on the core a little sooner now

[Spriggans]

Wow ! Multiplayer df would be awesome !

Keep on going !

[0rion]

As in, multiple players viewing and ordering around different sections of fort at same time?

If you do, that's going to be magma awesome.

Ideally, yes
Issue is, i have to write tons of GUI code by hand. Im probably going to use the C++ plugin for direct access, and offload the work onto an external script.

How are you going to manage the pause? Placing orders makes the game paused for everyone playing?

[Fleeting Frames]

When DF together was running, we handled that by discord and laughing at the control fight.

But most input screens, definitely including designation and building (and labours, obviously, given the plethora of external tools), can be abstracted away to not need pauses. I think liaison talk is a sticking point of a stop.

[MoonyTheHuman]

I'm likely going to make pausing the game vote based (2/3rd of players wanting it paused, maybe?)
For the liaison talk, I'm likely just going to skip that (as in, have it autoexit so it doesn't ruin gameplay, or cancel it via other means with minimum side effects)
All other GUIs will avoid pausing at all costs. If it needs to pause for a update to take effect, it will, but for a very short period of time.

[Fleeting Frames]

Also maybe when there's nobody active, pause it. Or perhaps just use a custom announcements.txt.
I can definitely see situations where temporarily only one player knows that e.g. there's werebeast on the surface. Maybe just have that part of the ‼fun‼, with good community (if game is paused can investigate the cause in chat or log; OTOH we got at least one vandal last time). Though regarding voting, have to consider idlers.

There's no perfect solution, so what would cause least hurt feelings? Maybe everyone can pause with cooldown+optional zoom hotkey/link being given to other players?

Liaison would be nice if multiple players could put in orders, even at different times, but it's pretty superfluous.

[MoonyTheHuman]

Maybe they could put in the orders beforehand, and have them entered when it actually arrives (allowing beforehand planning, and minimizing pauses)
Announcements and player logs will be separate, but they will be accessible.
Pause with cooldown would work. Zoom hotkeys will be a clientside thing.

I'm considering making a little 'lever control' GUI as a assistance tool. Basically allows you to label and interact with levers remotely, to allow quick control of fort levers. (Pulling is done by dwarf, toggling pull is done by you)

Also, I'm (almost definitely) not going to use the vanilla GUI style, I'm going to use a custom GUI system instead. Complete with assistive tools to make lives easier.

[Fleeting Frames]

So, all-new GUI.
Very ambitious.
I assume you've read previous user interface threads?

Maybe discuss it on old discord?