-
-
Notifications
You must be signed in to change notification settings - Fork 456
Turns the AI into a computer #12262
Turns the AI into a computer #12262
Conversation
|
Soooo... who is going to do the installing? I am thinking maybe the sigtech or CE? |
Or Scientists Or Scientists handing it to the RD/CE for them to do it Or handing it to a borg Something like that probably |
|
RD has traditionally been the person in charge of the AI, although on most maps the AI sat is linked to engineering |
|
Great Idea, will need ALOT of fleshing out. Also.. Third time is the charm |
|
server AI sounds fun but having a delay when doing actions is going to be a massive pain in the ass, even if it gets upgraded (especially for malfs) Upgrading will also be a pain in the ass, as malfs will have to let people into their core servers to become more better at making organics deader, and this opens it up to retribution anyways heres some upgrade ideas
|
|
also how will building a new AI work |
Probably be simplified to having to go to the Sat, upload a posibrain/MMI digitally through a console, and boom, you have a new AI with no upgrades. You'd then need to distribute available processing power to the new AI so it could research stuff. |
A future idea would be to rework the malf AI so it's much more deeply integrated with this system. This would probably include turning the job in charge of the AI into a team-mate of sorts.
|
The CRT filter would be an alternative to greyscale, aka something you could upgrade to remove. |
|
I think making the AI core more than a single tile object is a great idea. The AI core room has always been kinda underwhelming. Definitely keep all it's primary "body parts" encapsulated within the core sat though (aside from backup units which should probably not exist at roundstart imo). I love the idea that disabling the AI can involve needing to disable multiple machines in series (e.g. Removing RAM cards). I think we're steadily getting closer to a 2001: A Space Odyssey "Daisy" situation lol. This is in general a fantastic idea but as other's have said will require a LOT of fleshing out and rebalancing, testing, more rebalancing. There'll probably be some initial kickback if it doesn't work perfectly first time around. I also like the idea of cameras having predictable blind spots. This adds in the possibility of some stealth gameplay. Perhaps some upgrades can be to improve the camera processing performance. Allowing AI to boost some cameras temporarily or add temporary motion tracking or even object highlighting (glowing auras around weapons or rare items, hazards, radiation, gasses, hot/cold, depending on upgrade) for a limited time. I think we can expand the job of SigTech with this too - do you think it might be possible to allow SigTech to program some special NTSL or similar code for the AI? Giving it special notices on AI Private if something happens or allowing SigTech to code in special visual filters for cameras? I dunno. Longshot idea but it could be cool to have our only IT role perform some work with AI components in tandem with the RD but with a much lesser amount of access. I think it also makes sense to have the AI have some amount of software as a component. Thought will also need to be placed as to the extent that borgs can involve themselves with upgrades. What if it's malf AI, and only borgs can help? Or if there's no crew with access on lowpop? My recommendation for this PR is to identify a set of core features which really make this feature tick. And then a set of reach goals which would be cool to have bpt aren't necessary. Prioritize and build the first prototype off the core featureset and add additional features in spbsequent PR's to keep the complexity down for the first rollout. |
|
On NTNet: If we're re-using PC parts for this feature (a fantastic idea) can we also involve the AI with per-existing NTNet programs. We have programs like the IRC that nobody uses, or SM Monitoring, etc. Perhaps if AI is using PC parts we can leverage the pre-existing NTNet programs to add some bonus features without needing to code too much. Some off-the-cuff (and probably bad) Examples:
And for all of these, allow NTNet windows to be opened with an AI action verb instead of needing to click a console. We can use this PR to tie together unused features like NTNet such that more of the game's pre-existing features are available and useful. |
|
make sure we can overclock CPUS to stupid high levels so the atmos tech can work on getting AI stupid cold |
I'm not fixed on the implementation of CPU's yet. They'll probably be tiered with increased efficiency(Less power + less heat) |
This reverts commit e594c6c.
I think an easy way would be that malf ais found out how to integrate station equipment to their cpu. They hack chem dispensers, protolathes, weapon rechargers, apcs, fire alarms, etc. Perhaps after a while they start being able to hook up live human brains (and perhaps bodies) to their cpu. |
|
I'm absolutely in love with this idea and have been thinking about stuff like this for awhile. Please continue thinking about this. |
|
Redoing the PR so I can properly formulate ideas. |
|
day 1 of waiting for new link |
|
I miss our old setup with AI core behind the bridge and telecoms on the satellite. Can you work the swap in, please? |
|
day 2 of waiting for new link |
Sorry matey |
|
Day... 4? I think? I'm basing this off of github's counter |
|
day 5 |

Document the changes in your pull request
Instead of being based on a singular core the AI is now an actual computer living through servers on the AI sat.
There is no core to kill, instead when an AI is created it's uploaded to the cloud and run through these servers.
Reduces round-start AI abilities.
CPU cards and memory cards can now be installed in the AI core.
These allow the AI to research upgrades(Using CPU cards) and enabling upgrades (Using RAM)
All AI actions on physical machinery now have a slight timer before the action is confirmed. Max 1 action being done at a time.
Upgrades to decrease delay + increase concurrent amounts of actions.
AI's can still be stolen by hacking into the AI satellite and downloading the AI onto an intellicard like normal. This time from a network admin console though.
AI camera movespeed is now affected by upgrades. (Jumping to cameras don't count, this menu is also replaced by the security console for easy searching + viewing)
The core itself requires cooling which is mapped in at roundstart. More cooling is potentially needed if enough additional CPU cards are installed. (RAM cards don't produce a noticeable amount of extra heat.)
List of available researches:
Ideas:
Malf Rework
TODO, give me ideas :)
Move malf abilities to research and allow hacked APCs to count as fractional CPU cores?
More radical change compared to current malf AI?
Wiki Documentation
maybe if I finish
Changelog
🆑
tweak: The AI development budget has been slashed considerably
/:cl: