Author Topic: Characters are still detectable while in Time Stop.  (Read 832 times)

Anarcoplayba

  • Red Academy
  • Dark Power
  • ******
  • Posts: 1877
Characters are still detectable while in Time Stop.
« on: October 29, 2024, 12:45:12 PM »

Name: Characters are still detectable while in Time Stop.

Where: Everywhere

When: Casting Time Stop.

What: While in time stop characters still prompt hide and ms checks when interacting with doors, chests and generally grabbing stuff. Not only they prompt the detection checks but the penalties apply normaly and may even break invisibility and stealth, contrary to the spell description, which states that the caster is undetectable.

Recreate: Cast time stop and start to FaFo.

Ideas: Probably an oversight from before the invisibility nerf.
Noignar Huillen: Ilmater Cleric.
Hedien Gine: Arrow and Bow Artist.
Dolin Schneim: Dwarven Soldier

EO

  • Assistant Head DM/Developer
  • Head DMs
  • Dark Power
  • ******
  • Posts: 23406
  • The one and only, the one everyone wants to be!
Re: Characters are still detectable while in Time Stop.
« Reply #1 on: October 29, 2024, 07:40:32 PM »
Do the detection checks have any impact?

Anarcoplayba

  • Red Academy
  • Dark Power
  • ******
  • Posts: 1877
Re: Characters are still detectable while in Time Stop.
« Reply #2 on: October 29, 2024, 08:10:02 PM »
Do the detection checks have any impact?

They do: they break invis and stealth.
Noignar Huillen: Ilmater Cleric.
Hedien Gine: Arrow and Bow Artist.
Dolin Schneim: Dwarven Soldier

EO

  • Assistant Head DM/Developer
  • Head DMs
  • Dark Power
  • ******
  • Posts: 23406
  • The one and only, the one everyone wants to be!
Re: Characters are still detectable while in Time Stop.
« Reply #3 on: February 06, 2025, 09:46:58 PM »
I'll fix this.

EO

  • Assistant Head DM/Developer
  • Head DMs
  • Dark Power
  • ******
  • Posts: 23406
  • The one and only, the one everyone wants to be!
Re: Characters are still detectable while in Time Stop.
« Reply #4 on: February 15, 2025, 01:14:12 PM »
This should now be fixed.