Gawd Mode

[onerose2au]

Is there any chance that Gawd Mode will ever work again for new YM?

I was using the latest YM 11.5 and too many jealous that am running a Trivia bot. They keep booting my Trivia and my YTK E did not protect my triviabot from being booted in any way. The group just laughed at my triviabot being booted over and over. Then I decided to uninstall my YM 11.5 and install YM 9. There Gawd Mode is working 100% and the only thing that saved my triviabot from being booted over & over. My triviabot become blind but it didn't got booted again even once and the last laughed was mine.    After that, noone attempt to boot my triviabot again. Thanks to YM 9 and the Gawd Mode feature.

[Clusterphuck]

Nope, the inactive alias ability is removed from YMSGv18 and YMSGv19 so no, it can't be brought back.

[mutilation]

sorry if  this is off topic, when will ignore messages be back in ytk-enhanced

[Adam X]

Custom ignore messages definitely will be brought back. The previous problem which resulted in it's removal in the first place was the font tag and formatting being identified as spam-like by the chat servers. This caused the ignore messages to sometimes not be seen by others in the room except yourself (since it's echoed back locally in both cases by YTK). This won't be a problem going forward and it will be 100% compliant with Yahoo! Messenger's own text formatting.

Addressing the Gawd Mode concern. Gawd Mode is pretty much obsolete these days. I would like to know how your trivia bot is giving out points for correct answers for it's questions when Gawd Mode blocks all inbound (received) YMSG packets. Are you using another name in the room to give out points manually yourself or?

Gawd Mode these days is not as cool as the original and all it really is obviously is profile alias name account inactivation after chat has been entered. With the release of Yahoo! Messenger 11.0 and 11.5 (YMSGv18 and YMSGv19 respectively) you're not able to use it anymore because the chat servers simply don't support it when these protocol versions are used. To get around this you can use Messenger 11.0/11.5 and simply use YMSGv15-17 or version 102 instead, some features being limited of course but Gawd Mode will function. You'll need to enable Auto-Reconnect and select 15, 16, 17, or 102 in the control panel. There's no need to downgrade to a lower Messenger version when YTK can support them all to begin with.

In case anyone is wondering about why Yahoo! took away alias name inactivation (Gawd Mode) in YMSG protocol versions 18 and newer (19 is currently the newest), it's because of the new ability for multiple simultaneous account sessions being logged into multiple computers and different devices (mobile phones, other PC's, Yahoo! Mail Messenger etc). If any of these session instances sent an alias inactivation packet request then the server would have to block all chat communications (packets) sent to that alias and that would result in a potential problem for the global system of "never missing a message". They don't want you to be able to affect all session instances of a logged in account from a single session's decision to globally affect all other active sessions for the particular aliases. This is the answer I've come up with and it's pretty logical.

[onerose2au]

Yes Adam I just add manually...I just watch who's the first to type the correct answer. Hard but it's ok. Gawd mode still bootable but I guess if my booter has a slow net, he can't easily boot my trivia. Or what I do I login the trivia bot to supra and let him keep continue booting pretending am still using YM and I just sit there in laughed. Supra YMSG/HTTP yet he never boot me. Then 20mins later I go back login on YM again and run my trivia. Somehow I think he's IP got banned from booting because booting just stop or his bots got banned. Anyway, I get used to it. Thanks for the responds.

[SomeGuyFromCanada]

Gawd Mode is useless really.

Right now there is a way to find a persons main ID. So they could boot the main ID which is why Gawd Mode gets booted.

[Adam X]

Yes, that main id grab exploit is public now and it's one I've had on hand for a while (I didn't discover it). I don't have the time or patience to report this stuff to Yahoo! anymore and when they do patch it (like they just did) it almost always is revived (which it has been). The public version still works because of this neglect or care to fix something correctly. Yahoo! will fix it on a single server or single set of servers and leave a giant hole for it to crawl back through. Their loose server infrastructure is a nightmare for getting these kinds of issues correctly (meaning thoroughly) patched properly.

[Allen]

I am still pretty much unbooted on YTKE these days. I am looking forward to the next update, but for the most part it is still working well on my end.