lewandGitHub
11a9a2d644
Rewrites Saycode and Langchat to add support for multiple languages in one message, including audible emotes. <img width="1139" height="338" alt="image" src="https://github.com/user-attachments/assets/25e26932-7a6e-4c54-ab74-56fffb92ecad" /> Here's some samples to explain how to mix languages. <img width="422" height="26" alt="image" src="https://github.com/user-attachments/assets/e1b176cc-8625-4dc9-83c8-a053d3f310e6" /> `Languages ,2 can be mixed ,3 like this.` <img width="540" height="21" alt="image" src="https://github.com/user-attachments/assets/19156c67-4670-4d7a-84d7-26e527de2676" /> `!explains, ,2Emotes work too. ,0The text will get auto-quoted.` <img width="592" height="18" alt="image" src="https://github.com/user-attachments/assets/cfc31c5c-2383-41c8-82be-b36836339321" /> `,3Most languages ,0can be ,2mixed ,1arbitrarily, ,3any number of ,0times.` <img width="636" height="20" alt="image" src="https://github.com/user-attachments/assets/388b4f9d-192a-4374-ac31-bbd4e4e5dfe4" /> `,2Emotes. ,eAnd he nods. ,3They don't have to come first anymore.` There are some exceptions. The exceptions are currently anything with any of the flags `SIGNLANG`, `HIVEMIND`, `PRESSUREPROOF`, `KNOWONLYHEAR`. Exceptions work the same as current languages do: they must be the first language in the message. If so, they prevent switching into any other language mid-message; if they're not first, they just wont trigger. They're exceptions currently because there's not really a clean way that I or the people I asked for help on this one to make them look nice. `SIGNLANG` for example doesn't scramble text, it shows it's own ` gestures a lengthy message.` text for those that don't understand. Could we just replace every instance of sign language with that if somebody doesn't understand? Probably. It would look pretty awful though. e.g. `Alina Eskelinen says, "Hello." Alina Eskelinen gestures a short message.` This definitely needs testmerging because it more or less rewrites the entire pipeline surrounding `say`. The `say` code itself had to be rewritten to support the multiple languages, as well as all the existing plumbing for listeners receiving messages. In return though, it's significantly more straightforward and hopefully by extension easier for people to add to in the future. Primarily, instead of having four different `hear_say`, `hear_radio`, `hear_sleep`, etc., routes for messages to come through, every single audible message is received by `hear_message`, which is responsible for figuring out how clear the message is (is the radio damaged? is it a whisper we're eavesdropping on?), who needs to receive it in their chatbox, formatting it correctly for each listener, and finally if any npc or object within range needs to react to it in some way, like a parrot or a mech. changelog: - rscadd: "Adds code-switching: you can now speak in multiple languages in the same message." - rscadd: "Adds audible emotes to the language list. They can be triggered with ,e." - rscdel: "Removes SSrunechat." - refactor: "Rewrote langchat in order to support multiple languages and partial comprehension." - refactor: "Rewrote a vast majority of all saycode and the code responsible for displaying saytext to clients." - bugfix: "Sleeping mobs are no longer able to understand all languages." - bugfix: "Langchat now correctly shows the appropriate comprehension for all viewers rather than all viewers sharing the comprehension of the last viewer." - bugfix: "Languages which are supposed to be invisible when not understood no longer appear as scrambled overhead text." Forgive me whoever has to review this. Biggest areas that have room for error is stuff like a borer inside someone's head, and Dionae stuff. Old langchat had odd exceptions for those and I was forced to rewrite it entirely, but I think I got it all back to how it was working before.
Away sites
What exactly is an away site?
It's a kind of map template which:
- is placed in its own zlevel (or collection of zlevels),
- should only get placed once per round,
- can be randomly picked to be placed automatically during round setup,
- normally has an overmap presence and shuttle landmarks so ships can fly to it.
Er, what's a map template?
It's a datum you can define in the code (/datum/map_template) which points at one or more .dmm map files, and allows the game (or admins) to spawn those map files when and where they please, whether that's into an existing zlevel (like decorating exoplanets with ruins), or on a totally fresh one (like an away site!).
How do I make away sites?
tl;dr you make your .dmm files, then you write a new map template datum (/datum/map_template/ruin/away_site/insert_your_away_site_name_here).
BUT HEED MY RUMINATIONS
While mapping
Don't use map-specific types
Away maps are expected to work whether you're on the main map, Runtime, or anything else you might want to load as the server's main map. That means your map mustn't use areas, turfs, objects, mobs or datums that are specific to any main map.
e.g. you can use /area/space, or /turf/simulated/wall, because neither are specific to a certain map. They live out in the main codebase, are always compiled in, and are available to all maps. But you can't use items that may only be compiled with a certain map, because they only exists when said map is compiled.
Don't re-use area types from other maps
Except for, like, /area/space. That one's probably fine.
(Now that's just areas! Other stuff might be ok. Except very map-specific stuff as noted!)
Re-using areas is a shortcut, but it's bad for testability, and you can't guarantee that the area you re-use isn't loaded up and in active use on the server - in which case it'll hideously merge together with its brother in terms of stuff like air alarms, APCs, etc. Suddenly your derelict starship is randomly receiving power from another zlevel. Not good. Avoid. Make your own area types!
If you're doing multi-z, make a different .dmm file for each zlevel
Not exactly a technical requirement, but it makes things easier in terms of collaboration. See how it's done with runtime-1.dmm, runtime-2.dmm, etc.
Afterwards (or during, I'm not a cop)
Make sure you've got a .dm file for all your stuff
It's a pretty good place to put all your new types! #include other files here too. This file's going to be the hub of your map's wheel, to cack-hand a metaphor.
Make a map template datum there
The game will read this to learn about your new shiny away sites, including what .dmm files it needs to load, how much it 'costs' to spawn (usually 1, increase for more performance-heavy away sites). Ask devs or read code if unsure..
Some of the stuff I put in my map isn't behaving properly!
The map loader works best when everything it's spawning does all its initialisation work in Initialize, instead of in New. Most likely your misbehaving thing is doing more initialisation than is healthy in New. It's fixable! Often not even that hard. Go talk to a dev.