 |
Here's a list of all known bugs in TuxServe that have yet to be fixed.
TuxServe-0.0.10alpha ::
-- When adding or changing a "trigger_dir", you must include the finaly slash (/)
- despite what the docs say.
-- TuxServe will only work (eg, show adverts, respond to triggers) on the currently focused/active
server. So, for example, if you were connected to 2 networks at the same time - #fishsticks on dalnet, and #thissucks
on efnet (not real channels) - and you'd set up TuxServe to work on both of these, it'd only work on the server you
are were looking at. If you were chatting in the dalnet channel, TuxServe would ignore everything from efnet, and
vice-versa. I've been trying to fix this for a long time, but I'm uncertain on how to fix it - so it could take a while -
sorry.
-- When a user logs out of the fserve by either killing the DCC session, or by typing "exit", or "quit" in
the fserve's DCC chat window, it is sometimes impossible for the user to log back in again whilst
a dialog window with them is focused. Just change the focus of the window.
-- After all sends and/or queues have finished, the sends/queues files will sometimes
still contain the first letter of the last send's/queue's nick.
-- If someone is browsing your fserve when you change the idle timeout setting, it will not take effect
until that user either logs out, or the old idle timeout gets reached.
|
|
 |
