Doing so affect the entire community by jamming the CF for a long period of time. Therefore, next VarAC version will introduce a new limitation:
CQs that will be fired on a CF without a SLOT-ID, will not be decoded and will not be shown by others. In other words - your CQ will not be heard nor replied.
Whatever the reason you are not using a SLOT ID, please be prepared for this change.
Upgrade your VarAC version to one that supports Slots, or enable the Slot system you have manually disabled under the settings menu.
Yes, it does make sense. The slot sniffer makes this easy.
It would be good to remove automatic beacon repeat too. It looks like many users leave their beacon on and leave the shack. The whole point of VarAC is that C stands for Chat, yet there are sometimes 10 times the number of beacon signals compared to CQ calls.
Well if you need slots use something like the Texas VHF Society setup 144.91, 144.93, ... 145.01 packet calling frequency, 145.03, ...145.09. In Houston we use 145.03 NE Harris, 145.05 SW, 145.09 NW for example. Our FLDigi folks seem to test on 144.91 and VaraFM on 03/05/09 mixed with packet 1200. Suggest 144.93 calling and hop to 144.95/97 for chats.
Not sure how this change will affect VarAC FM using digipeater.