Arelith

The GSF Illusion messenger goes on lock-out after using ESF Illusion (Clone)

Steps to reproduce
----------------------------
1. Send a message with -project_image <Name> to see the character can send messages
2. Rest to clear the timer
3. Use ESF Illusion (Clone) to create a character illuion
4. Try and send a message with -project_image <name>


Expected result
-----------------------
Message sends and starts a countdown regardless of the ESF clone, same behavior as the -teleport_create and -teleport working independantly


Actual result
-------------------
Observe the error message 'Character must be level 21 and have the GSF Illusion feat. Message not sent. '

Yes, this is not intentional. Allow me some time to fix this.

It's an awesome quality of life code change you made take all the time needed to fix this one erroneous little piece, as it still works in all other instances!

I just had it fail and give the same message without having made the illusion clone. The only thing I can think of causing it would be the FOIP -ward command against scrying which I had used in that rest cycle.

Now seems to be always only usable once per rest. I've not been able to succesfully send a second message in a few days.

Thanks for the report! I am currently investigating this.

monkeywithstick wrote: Fri Oct 04, 2019 5:59 pm I just had it fail and give the same message without having made the illusion clone. The only thing I can think of causing it would be the FOIP -ward command against scrying which I had used in that rest cycle.

The clone is, to my knowledge, still an Epic Spell Focus once per rest bonus.

The update decouples "sending an image" from "making a clone", with "sending an image" being the GSF cooldown bonus.

I am aware of this. The clone I was referencing was the one that delivers the message.

monkeywithstick wrote: Wed Oct 09, 2019 8:48 am I am aware of this. The clone I was referencing was the one that delivers the message.

Ah, fair play.

Sorry for the delay guys, this is a WIP now.

Phew, this has been a nasty one. I believe I made a fix for this and the update will go live soon!