Strange numbers in XDCC Klipper status window.

[a7mag3ddon]

Hi everyone, i have a question about klipper status window(s) where packs are listed from the channels.

I know that klipper hasnt been supported in a long time but hope some you your scripting guys can help me out, since upgrading to the new invision and mirc 6.35 the klipper status window has had an unusual column containing 13 digits for every pack listed, seems a bit random but as an example 000034900000

i used to use the old invision, with klipper and an older version of mirc.

Anyone know why ? or whats changed.

[Riamus]

Any help with other scripts should be directed to their site/forum. XDCC Klipper isn't something that we support and I've never used it, so have no idea how it works.

You say you have the new version of Invision and are using mIRC 6.35. The newest version (3.2) of Invision does not support mIRC 6.35. It requires mIRC 7.1 or newer. If you are using the older version (3.1.3) of Invision, it will still work on mIRC 6.35. But whether or not XDCC Klipper works on 6.35, I have no idea. If not, then that script would need to be updated or you'd have to use an older version of mIRC.

[a7mag3ddon]

Hi, thanks for your reply. I understand its not supported but did see that others had asked questions about klipper problems and thought it worth a shot. klipper forums/ site has been dead for a number of years now (i was an original beta tester).

My problems started when i upgraded invision from 3515 i think it was, and a very old version of mirc, it caused problems with sound so i then upgraded mirc to 6.35 which has now caused a problem with klipper

pain in the ass but i do love my klipper program

[Riamus]

I believe there are newer scripts that are similar to XDCC Klipper that you might check into. Otherwise, someone out there using it might have time to find the problem for you. It isn't a small script and with maintaining Invision, which is even larger, I just don't have time to figure out other scripts and fix them. It's possible someone here can look into it, but the forum has gotten less active over the past year or two and most posts are just questions that I answer. There isn't much discussion or help from other users on here these days even though the script is still used as much as before. You might ask in some #script or #scripting channels on various networks and see if anyone's worked on that problem yet. I'd be willing to bet that someone has fixed it for their own use by now.

If you know what the column should be showing (based on the heading), that might indicate why it's showing the wrong thing.