CallACS builtin is accessible from non-play scope

Forum rules
Please construct and post a simple demo whenever possible for all bug reports. Please provide links to everything.

If you can include a wad demonstrating the problem, please do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.

Please make a new topic for every bug. Don't combine multiple bugs into a single topic. Thanks!

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies
BBCode is ON
[img] is OFF
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: CallACS builtin is accessible from non-play scope

Re: CallACS builtin is accessible from non-play scope

by Graf Zahl » Mon Aug 13, 2018 12:29 am

Crap. And wanna bet that changing this will break several mods which use ACS to do some of their HUD work?

CallACS builtin is accessible from non-play scope

by argv » Sun Aug 12, 2018 8:54 pm

As of GZDoom 3.5.0, the builtin function CallACS (and, presumably, the other ACS_* builtins) can be used from outside the play scope. This is obviously unsafe.

The attached pk3 demonstrates that unsafety, by spawning an imp from ui scope. To use:
  1. Load it into GZDoom, along with a Doom-compatible IWAD.
  2. Start a game.
  3. Walk into an area where there's a decent amount of room above you.
  4. Press the Use key.
That'll spawn an imp on top of you—from StaticEventHandler.UiTick!
Attachments
misscope.pk3
(1.39 KiB) Downloaded 90 times

Top