I've just realized that Invison rarely manages to create an FServer Caché File.
Those are the files: FSdir1 for Trigger 1, FSdir2 for Trigger 2 and so on
When creation of those caché fails, Invision shows inside server window the following message:
* /run: unable to open 'command' (line 811, ifsmgr.mrc)
That one above is for EFnet Trigger 1
When I change trigger's name or folders, at most, 2 of triggers might work, but generally, none trigger creates its respectively caché file at all!
Please, is there some workaround for this bug?!!? Or at least, what provokes a trigger setup create a caché or not?!?!!?
Thanks in advance!