Fred
Retired Staff
Rrrk.
Wes, I'll admit that it seems like a very nice article, but there's a lot about it that I also don't like.
1. Inconsistency with the nekovalkyrja's digital mind
2. Quantum computing
3. Overpowered in many respects:
I like Yamatai being the top state-of-the-art thing too... but if you push it too far, it just ends up looking silly and impractical for those arbitrating the narrative... then the system won't look all that credible because GMs will no doubt force the devices to be faillible/not use it to its full (actually undesirable) potential (like it is now with most of our ship/power armor sensors).
Wes, I'll admit that it seems like a very nice article, but there's a lot about it that I also don't like.
1. Inconsistency with the nekovalkyrja's digital mind
- The neko's digital mind is capable of a whole lot of things that have kind of made communicators a bit redundant, which is why they aren't really all that proemminent in the Yamatai-roleplays. With good reason. This device just seems to continue the trend of covering up the inconsistency, rather than usefully addressing it.
2. Quantum computing
- Putting a small quantum computer in such a device qreatly cheapens the meaning of having a quantum computer on a larger platform.
For example, putting on a power armor greatly enhances the neko soldier physically, but it also places at the neko's disposal the AIES - not only perception/informational/communicative tools, but also a quantum computer.
IES-units have an characterized identity in SARP. Allowing quantum computers in a purely handheld devices kind of slaps that in the face.
Also, if you get a quantum computer to be this small... what's stopping you to make neko brains that includes quantum computing? It'd set a precedent for even more power creep in the future, simply because it'd make sense then.
3. Overpowered in many respects:
- Like most of Yamatai's computers, sensors and communication systems... this is really more powerful than it needs to be. It furthers the tradition of putting big-words and big-numbers to make Yamatai look impressive... when in truths it's typically really dang inconvenient for the GMs of your faction to create believable scenarios with relateable limitations.
This applies to ship sensors, power armor sensors - practically everything. It's been like that since the Ayenee days where you had to write stuff that'd allow the Grand Star Army to compete with the other guys... but we're still hurting from the many ridiculously overblown possibilities they offer, especially when players sit down to see what they have at their disposal, and that the GM tries to make it relatable and have these system compete against each other.
In several ways, the MIKO computers were a step towards trying to fix this, except that Andrew kind of snatched the concept away from me by deciding to complete it for me, and then snatch it away with the UOC. Still, those were better researched, and a whole lot reasonable.
Beyond that, there never was any sitting down to place yamataian units in different crisis and ask "how much do we actually need", "how much is indesirably too much". But I won't go into that here. I'm just going to go for that Type 36 communicator.
- a) If I need serious computing, I want to route demands to a more important PANTHEON node (power armor -> shuttle -> spaceship)
b) If I want people to communicate, I don't want it to be to unlimited distances. I also want them to be able to reach whomever it makes sense to be reached (planet to orbit, and not planet to Admiral). Longer distances can be routed through more capable communication relays - like a communication tower on a planet, or a ship sending the message through hyperspace signal.
Seriously ask yourself in a single communicator is supposed to reach a starship in orbit (and if it is, will the transmission be strong? or the messages more rudimentary?) Do you want it to reach that far, or is it just enough for the communicator to be able to contact someone in the same city? Would it make sense to have the communicator rely on another base like a shuttle to route the message to the farther away ship? Would that be so bad, considering that an away team would come downplanet in a shuttle anyways?
Mind you, the same could go with power armor and shuttles/transport. Right now, Yamataian power armors don't really need transports because they're in general too good. But being unable to make atmospheric entry/escape could be one dependency. Relying on the transport for long-range communications could be another. Limiting running time (Daisy-style battery) could be yet another.
If you design things too well, you lose out on those dependencies, and why it makes sense to have many units at a commander's disposal.
c) if I want people to communicate, I want it to be dependable, but not to the point of infallibility. Making things too good break opportunities to engender problems, chaos, uncertainty and encourage complacency rather than more gritty alertness, cleverness and professionalism.
Situational conditions like weather/being underground can worsen matters, and demand trying to contact people later on (story material). Jamming can require people to move out of the area to be able to contact allies... or move into such an area to rescue a unit that contact was lost with and might really need relief.
d) Making the device too high-tech (it's display mode) equals that being state-of-the-art also makes it hard to service in the field. Sometimes the best engineering solution is the simpler and rugged ones, rather than the most technological ones.
Being field-serviceable gives techs the opportunity to repair broken devices. Tweaking encryptions to be more slippery should be more something a person good at communication achieves that the device would give the proper tools to provide such, rather than being done all conveniently automatically.
e) mental backup recording being tied to such a device is -- gah. Don't do it. It's bad. For obvious reasons. Retain the value of the medlab in a mothership/homebase, and the present "as long as my unit survives, I might be restored to life" condition Yamataian soldiers presently face. Making it more convenient than that greatly cheapens the consequences of death.
(and arguably if a small communicator can do it, larger non-medlab facilities like power armors could manage it. Reaaly REALLY bad)
f) I'm okay with a lot of the apps being available on the device, but I think several of those which have far longer range should depend on an uplink to a more powerful 'server unit' (i.e.: shuttle). Again, inter unit dependencies - which is, I might add, kind of the point of PANTHEON networks.
- a) If I need serious computing, I want to route demands to a more important PANTHEON node (power armor -> shuttle -> spaceship)
I like Yamatai being the top state-of-the-art thing too... but if you push it too far, it just ends up looking silly and impractical for those arbitrating the narrative... then the system won't look all that credible because GMs will no doubt force the devices to be faillible/not use it to its full (actually undesirable) potential (like it is now with most of our ship/power armor sensors).