Skip to content
GuarDDog v. 5

Update Round : 6th August - 4:15pm (GMT +10)

A TG007 community discussion started by The Gate Keeper.

Closed discussion 11 posts
Page 1 of 1
Closed
Topic #7149 · 11 published posts · 2,346 views

Well this is just an update to fix up problems that have been reported in the last month, especially with changes to MSN's MySpace now taken over to Live! control.

 

In this update...

GuarD-Doctor

1. Made it capable to install mIRC 6.2 without being kicked off.

2. If on mIRC 6.2, flood protection auto enables (reduces the chance of flood out on 6.2, some weird reason it floods out if it isn't enabled, but doesn't on 6.17).

 

DogCollar

1. Corrected Profile Scanner, recoded, and removed 10kb of code (which should also fix a few of the "line to long" errors people were getting with dc.decode and the profile scan actions).

2. Removed the "picture" that appears in the profile scanner dialog because in mIRC 6.2 it causes it to freeze and crash.

3. Modified the auth section a little.

 

Basically, the new updates is just what was required to be done, not what i think should be done. The update to DogCollar will allow for your profile scanner to become fully functional again.

 

Unlike the previous update from version 5.0 to version 5.0a (when mIRC 6.16 jumped to 6.17) it is not manditory that you update your mIRC. It will be completely up to you. It runs effectively on both, provided you are using the most up to date of all scripts. So yea, to users who want to update, you do not need to do anything except install the new mIRC in it's place. For those that don't, you can stay on 6.17. I will not force (unlike last time) users to update their mIRCs, as i haven't had time to sit down and play with 6.2, and last time it was required cause the whole coding style changed, from what i've gathered there isn't any great change in the coding style.

 

Anyways, back to being on Hiatus... (ps. I'll check the forum over the next 48 hours to see if any complications occur, but that's it).

Hey bro. Great to see you again. As always, awesome work. :)

:fixed::jump::GD:

DC update +2 (so 1.4.0 [above] to 1.4.2), fixed up bugs in the profile scan when scanning for those "fake" guests, and also fixed up problems with the file writes for the profile scanner, and also fixed up a bug with the special characters. If this is not updated, you will experience problems with your script kicker nickname checker.

 

PLEASE NOTE: When installing mIRC 6.2, ensure that you have "Keep original settings" marked, otherwise you will lose data setups. It is also recommended that you update to 6.2 if you are experiencing freezing issues, or if the profile scanner isn't working 100%. The scanner should be fine, but i have noticed it stop working here and there, so it is only a RECOMMENDATION that you update to 6.2, but be aware, KEEP ORIGINAL SETTINGS!

Edited Aug 6, 2006 2:04 PM by The Gate Keeper

Hi TGK, hope you are well and your exams are going ok :D...ok.... i did the updates today and since then GD keeps freezing on me, just wondered if its a local issue (ie my pc) or if anyone else has the same probs.

A fine is a tax for doing wrong. A tax is a fine for doing well.

I havent had that problem, although, I did notice on 6.17, after doing the DogCollar update, the servers were slow to connect. I just restarted, and they worked fine.

i'm not to sure what would cause problems, i used it for like 2 hours yesterday and idled in thelobby, no problems. Perhaps update mIRC to 6.2.

ok i think it was a local issue...but im getting this and im not sure why "[03:19]  * Connect retry #7 127.0.0.1 (15936)

-

[03:19]  * Unable to connect to server (Connection refused)" that is constant in the status window

A fine is a tax for doing wrong. A tax is a fine for doing well.

that would be for reconnection...

yeah i see that but it connects to rooms added to auto join so all is fine there but i dont understand why its trying to auto connect to something else

A fine is a tax for doing wrong. A tax is a fine for doing well.

it's partly cause i messed up the code, but not to sure how to better it. Just close that status window.

 

When i come back from hiatus, i will look into these matters.