Open mmMarzban opened 4 months ago
TBH i don't really have a use for either one, but I could see instance_destroy_region()
being potentially helpful if it took into account sprite dimensions (rather than using mask-based collisions).
That said, it's kind of the issue i have with instance_deactivate_region()
or position_destroy()
- it's not really able to discriminate beyond what exists in a given region/position, instead destroying EVERYTHING there including system objects and instances like scenery and floors, and so to me it feels like shooting a bullet through your computer screen lol.
Is your feature request related to a problem?
It seems reasonable to me that just as we have instance_destroy(), we could also have
instance_destroy_region()
andinstance_destroy_tag()
. The former destroys all the instances in a region and the latter destroys all instances sharing the same tag.Currently you have to do it DIY and a lot of code and array checks are needed,
Describe the solution you'd like
Just kindly add these two functions to further enrich the GML code roster.
Describe alternatives you've considered
No response
Additional context
No response