Skip to content

Lasombra tech bane and other tech interactions#654

Open
FalloutFalcon wants to merge 10 commits intoDarkPack13:masterfrom
FalloutFalcon:my-puter
Open

Lasombra tech bane and other tech interactions#654
FalloutFalcon wants to merge 10 commits intoDarkPack13:masterfrom
FalloutFalcon:my-puter

Conversation

@FalloutFalcon
Copy link
Member

@FalloutFalcon FalloutFalcon commented Feb 8, 2026

About The Pull Request

Readds most the old tech bane interactions. Though uses apoc's edit for the computers that means its just a do_after rather then a hard lockout pending a more interesting implementation.

image image

Why It's Good For The Game

Changelog

🆑
add: Readds old interactions of Lasombra's tech bane
balance: Computers require at-least 1 dot in computer to not have a do_after
qol: Candles last a full hour
/:cl:

Comment on lines +112 to +116
/* V20 p. 108
This Knowledge represents the ability to operate and program computers, including mobile devices.
Most Computer use also imparts a degree of Internet awareness (if not savvy).
*/
description = "Affects your ability to use and interact with computerized devices."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add in init something like if config_flag punishing zero dots description += "If you have computer skill 0 you wont be able to use computers" so that players know

Comment on lines 748 to 768
// DARKPACK EDIT ADD START - STORYTELER_STATS
// Likely worth making a dice roll after #633
if(isliving(user) && skill_required_for_use)
var/mob/living/living_user = user
var/bad_at_device = FALSE

if(living_user.st_get_stat(skill_required_for_use) < skill_dots_minimum)
to_chat(user, span_warning("[src] requires atleast [skill_dots_minimum] dots in [skill_required_for_use::name] for proper use."))
bad_at_device = TRUE

/* I cant verify the lore accuracy of "rejection past your embrace age" and we dont have a invention date for tech to represent it either
if(skill_dots_minimum > 0 && HAS_TRAIT(user, TRAIT_REJECTED_BY_TECHNOLOGY))
if(skill_required_for_use in list(STAT_COMPUTER, STAT_TECHNOLOGY))
bad_at_device = TRUE
*/

to_chat(user, span_warning("You start interacting with [src]. Confounded device..."))
if(bad_at_device && !do_after(user, 1 TURNS, src))
to_chat(user, span_warning("Bah! You didn't need [src] anyways."))
return TRUE
// DARKPACK EDIT ADD END
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Punishing zero dots conditional pls

Copy link
Member Author

@FalloutFalcon FalloutFalcon Feb 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So my reason for putting punishing zero dots behind config was specifically due to them hard-locking you out of content. This is just a annoying do_after, so it densest have the same issues as we talked about to me. If you want it behind a config still just thumbs up this lol.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants