mirror of
https://github.com/Bubberstation/Bubberstation.git
synced 2026-01-30 11:01:35 +00:00
ff6b41aa07
## About The Pull Request - Afterattack is a very simple proc now: All it does is this, and all it's used for is for having a convenient place to put effects an item does after a successful attack (IE, the attack was not blocked)  - An overwhelming majority of afterattack implementations have been moved to `interact_with_atom` or the new `ranged_interact_with_atom` I have manually tested many of the refactored procs but there was 200+ so it's kinda hard ## Why It's Good For The Game Afterattack is one of the worst parts of the attack chain, as it simultaneously serves as a way of doing random interactions NOT AT ALL related to attacks (despite the name) while ALSO serving as the defacto way to do a ranged interaction with an item This means careless coders (most of them) may throw stuff in afterattack without realizing how wide reaching it is, which causes bugs. By making two well defined, separate procs for handing adjacent vs ranged interactions, it becomes WAY WAY WAY more easy to develop for. If you want to do something when you click on something else and you're adjacent, use `interact_with_atom` If you want to do something when you click on something else and you're not adjacent, use 'ranged_interact_with_atom` This does result in some instances of boilerplate as shown here:  But I think it's acceptable, feel free to oppose if you don't I'm sure we can think of another solution ~~Additionally it makes it easier to implement swing combat. That's a bonus I guess~~ ## Changelog 🆑 Melbert refactor: Over 200 item interactions have been refactored to use a newer, easier-to-use system. Report any oddities with using items on other objects you may see (such as surgery, reagent containers like cups and spray bottles, or construction devices), especially using something at range (such as guns or chisels) refactor: Item-On-Modsuit interactions have changed slightly. While on combat mode, you will attempt to "use" the item on the suit instead of inserting it into the suit's storage. This means being on combat mode while the suit's panel is open will block you from inserting items entirely via click (but other methods such as hotkey, clicking on the storage boxes, and mousedrop will still work). refactor: The detective's scanner will now be inserted into storage items if clicked normally, and will scan the storage item if on combat mode /🆑
59 lines
2.6 KiB
Plaintext
59 lines
2.6 KiB
Plaintext
/**
|
|
* ### envenomable caseless element!
|
|
*
|
|
* Non bespoke element (1 in existence) that lets caseless bullets be dippable.
|
|
* When you fire the bullet, it will gain venomous. The casing itself isn't venomous to prevent bullshit
|
|
*/
|
|
/datum/element/envenomable_casing
|
|
element_flags = ELEMENT_BESPOKE
|
|
argument_hash_start_idx = 2
|
|
/// how much reagent can you dip the caseless in?
|
|
var/amount_allowed
|
|
|
|
/datum/element/envenomable_casing/Attach(datum/target, amount_allowed = 5)
|
|
. = ..()
|
|
if(!istype(target, /obj/item/ammo_casing))
|
|
return ELEMENT_INCOMPATIBLE
|
|
src.amount_allowed = amount_allowed
|
|
RegisterSignal(target, COMSIG_ITEM_INTERACTING_WITH_ATOM, PROC_REF(handle_interaction))
|
|
RegisterSignal(target, COMSIG_ATOM_EXAMINE, PROC_REF(on_examine_before_dip))
|
|
|
|
/datum/element/envenomable_casing/Detach(datum/target)
|
|
. = ..()
|
|
UnregisterSignal(target, list(COMSIG_ITEM_AFTERATTACK, COMSIG_ATOM_EXAMINE))
|
|
|
|
///signal called on the parent attacking an item
|
|
/datum/element/envenomable_casing/proc/handle_interaction(obj/item/ammo_casing/casing, mob/user, atom/target, click_parameters)
|
|
SIGNAL_HANDLER
|
|
if(!is_reagent_container(target))
|
|
return NONE
|
|
var/obj/item/reagent_containers/venom_container = target
|
|
if(!casing.loaded_projectile)
|
|
user.balloon_alert(user, "casing is already spent!")
|
|
return ITEM_INTERACT_BLOCKING
|
|
if(!(venom_container.reagent_flags & OPENCONTAINER))
|
|
user.balloon_alert(user, "open the container!")
|
|
return ITEM_INTERACT_BLOCKING
|
|
var/datum/reagent/venom_applied = venom_container.reagents.get_master_reagent()
|
|
if(!venom_applied)
|
|
return ITEM_INTERACT_BLOCKING
|
|
var/amount_applied = min(venom_applied.volume, amount_allowed)
|
|
|
|
casing.loaded_projectile.AddElement(/datum/element/venomous, venom_applied.type, amount_applied)
|
|
to_chat(user, span_notice("You coat [casing] in [venom_applied]."))
|
|
venom_container.reagents.remove_reagent(venom_applied.type, amount_applied)
|
|
///stops further poison application
|
|
UnregisterSignal(casing, COMSIG_ITEM_INTERACTING_WITH_ATOM)
|
|
RegisterSignal(casing, COMSIG_ATOM_EXAMINE, PROC_REF(on_examine_after_dip), override = TRUE)
|
|
return ITEM_INTERACT_SUCCESS
|
|
|
|
///signal called on parent being examined while not coated
|
|
/datum/element/envenomable_casing/proc/on_examine_before_dip(obj/item/ammo_casing/casing, mob/user, list/examine_list)
|
|
SIGNAL_HANDLER
|
|
examine_list += span_notice("You can dip it in a chemical to deliver a poisonous kick.")
|
|
|
|
///ditto, but after it's been coated
|
|
/datum/element/envenomable_casing/proc/on_examine_after_dip(obj/item/ammo_casing/casing, mob/user, list/examine_list)
|
|
SIGNAL_HANDLER
|
|
examine_list += span_warning("It's coated in some kind of chemical...")
|