What if… what if…
SS14 worked on the steam deck, and could have a console-friendly graphical interface.
How much effort would it take to implement such a thing, and is it even practical?
I feel like typing dialog would be pretty slow without a keyboard. Maybe with voip?
1 Like
I mean goob tried it, adding a simple proximity voice chat and comms VC into SS14 natively could be an option
2 Likes
The user interface would have to be heavily modified, we would probably have to set up convenient default controls for controller support, Annd add voice chat to SS14 since typing on those “virtual keyboards” sucks ass
2 Likes
Im not sure this is a good idea. Yeah, might be work, if your server is looks something like mmorpg with less typetexting.
But it doesn’t work with heavy roleplay server, where you need typing-typing-typing, with less gameplay or controls mostly based on UI + Keybinds.
Space Station should be only accessable on PC, FOR EVER
Not every server is heavy RP, limiting SS14 to PC only harms community participation. HRP servers can adopt hybrid input method support (voice, typing + optional virtual keyboard)
Going “PC forever” is fundamentally exclusionary and ignores accessibility and platform diversity. Which I feel goes against everything SSMV was made to solve. Expanding to console/controller friendly setups will improve the experience for everyone, including PC users, which gives people more chances to play, therefore leading to more server activity, feedback and content.
Also you took two months to reply, only to boast a PC supremacy mindset on a thread about future console support, which isn’t exactly productive or helpful to this thread.
I can see space station being playable over VOIP/voice instead of text, but you’d have to lose some mechanics like syndies being able to impersonate someone. Otherwise you’d know who they are as soon as they speak.
Continuing the discussion from SS15: Console edition (idea):
I think there’s another way to do it.
We don’t necessarily have to use voice, as long as the keyboard supports voice recognition and allows for manual input. Players can choose which works for them.
Instead, we can split servers into two separate types: classic and optimized.
Classic servers follow the current standards thst upstream has. Console players can still join these servers, but they’ll be expressly notified it may be less convenient
Optimized is a new upstream which deviates from wizden in terms of UI and certain functionality. Some objectives will be modified, voice chat is added, and the big chat box is removed.
These servers will likely need panic bunker enabled with the expectation that one admin online. An admin will need to listen to all comms channels at once to discourage really annoying mic behaviour.
Console-focused upstream could also adjust certain features, like shifting stealth mechanics to prioritize a focus of invisibility over text-based deception.
This way, PC players keep the classic experience, while console players get a tailored version designed around their hardware, without either group losing anything.
It’s up to the server to choose which category they wish to cater to. We will most likely see the optimized version hosted on networks of servers. Rather than individual servers.
Additionally, other features currently being discussed, such as How will MV integrate upstream permissions requests?
might further improve the experience for console and PC users and allow them to play multiple servers while maintaining the same playtime and data, making their experience consistent across servers regardless of the hardware they’re using.