Give the AI pAI-like features/data resource. For Points, you can buy pre-set do-it-for-you Telecomms scripts, Med/Sechud overlays, always-open auto-refreshing crew monitoring console, a selectable list/window dedicated entirely to all the air alarms and APCs. You can buy flashlights on cameras (Flares instead?), or you can convert a camera to Motion/X-Ray for a fixed cost per camera.paprika wrote:when
I'm fairly certain most, if not all cameras actually have lights on them, Unless I'm losing my mind here.Psyentific wrote:You can buy flashlights on cameras.
That's terrible. I wanna see dim, emergency-red lighting on all cameras.Remie Richards wrote:I'm fairly certain most, if not all cameras actually have lights on them, Unless I'm losing my mind here.Psyentific wrote:You can buy flashlights on cameras.
Edit: The Camera the AI is looking through can be toggled for lights, but it's only that camera, and only when the AI is in it.
But then I can't smash every bulb on the station in five minutes and be super spooky!Psyentific wrote:That's terrible. I wanna see dim, emergency-red lighting on all cameras.Remie Richards wrote:I'm fairly certain most, if not all cameras actually have lights on them, Unless I'm losing my mind here.Psyentific wrote:You can buy flashlights on cameras.
Edit: The Camera the AI is looking through can be toggled for lights, but it's only that camera, and only when the AI is in it.
Yes. That is a REQUIRED change should this be wanted. Otherwise it's far too much code duplication.Gun Hog wrote:I figure simply making the Medical and SecHUDs part of "Silicon" instead of inside the pAI code itself is better, so both AIs and pAIs can run on the same proc without duplication. The example provided does NOT currently include this change, but if people actually want this, then I will code this to standard, to the best of my limited ability.
I really like this idea, so I put a bit more work into it: Please see here!Remie Richards wrote:Yes. That is a REQUIRED change should this be wanted. Otherwise it's far too much code duplication.Gun Hog wrote:I figure simply making the Medical and SecHUDs part of "Silicon" instead of inside the pAI code itself is better, so both AIs and pAIs can run on the same proc without duplication. The example provided does NOT currently include this change, but if people actually want this, then I will code this to standard, to the best of my limited ability.
Gun Hog wrote:I really like this idea, so I put a bit more work into it: Please see here!Remie Richards wrote:Yes. That is a REQUIRED change should this be wanted. Otherwise it's far too much code duplication.Gun Hog wrote:I figure simply making the Medical and SecHUDs part of "Silicon" instead of inside the pAI code itself is better, so both AIs and pAIs can run on the same proc without duplication. The example provided does NOT currently include this change, but if people actually want this, then I will code this to standard, to the best of my limited ability.
Code: Select all
regular_hud_updates()
if (src.hud_mode == SEC_HUD)
src.securityHUD(src.eyeobj)
if (src.hud_mode == MED_HUD)
src.medicalHUD(src.eyeobj)Because the regular_hud_updates() is one of deletion. It clears the hud of previously drawn elements, in preparation for the next. Here is a more polished version that I feel is perhaps ready for testing and putting up to PR. Let me know what you think! https://github.com/GunHog/-tg-station/c ... nsors_BetaRemie Richards wrote:Gun Hog wrote:I really like this idea, so I put a bit more work into it: Please see here!Remie Richards wrote:Yes. That is a REQUIRED change should this be wanted. Otherwise it's far too much code duplication.Gun Hog wrote:I figure simply making the Medical and SecHUDs part of "Silicon" instead of inside the pAI code itself is better, so both AIs and pAIs can run on the same proc without duplication. The example provided does NOT currently include this change, but if people actually want this, then I will code this to standard, to the best of my limited ability.My only gripe is this, Shouldn't regular_hud_updates() be called BELOW the secHud() and medHud() Calls? because what's the point in updating the Hud, if the state of the hud may change right after the update?Code: Select all
regular_hud_updates() if (src.hud_mode == SEC_HUD) src.securityHUD(src.eyeobj) if (src.hud_mode == MED_HUD) src.medicalHUD(src.eyeobj)
Besides that, It looks nice.