Author Topic: Org. Msg. channel (Read 3794 times)

Wolfbiter · « **on:** December 08, 2005, 01:08:41 pm »

As far as I can tell, bebot doesn't see this channel.
Anyone managed to fix it?

Zacix · « **Reply #1 on:** December 08, 2005, 02:47:00 pm »

Not that I've checked it, but I would assume that "Org. Msg" channel is a group channel. If you want to monitor anything on this channel, your code should use gmsg function to do so.

Code: [Select]

$newmodule =& new NewModule($bot);
$commands["gmsg"]["Org. Msg"][] = &$newmodule;

Any code in gmsg in NewModule should receive Org. Msg messages.

Shelnaria · « **Reply #2 on:** December 08, 2005, 03:00:12 pm »

Please be sure to log in with the toon account that the bot uses and selece the channel in chat config. It worked fine for me after doing so.

Wolfbiter · « **Reply #3 on:** December 08, 2005, 03:19:15 pm »

Zacix: The problem is that the bot doesn't see it at all, not that I can't get a script to process the information.

Shelnaria: I tried that, but still doesn't work. I logged in and selected it for the "default window". Not sure if it's something I'm missing...?

Zacix · « **Reply #4 on:** December 08, 2005, 03:33:56 pm »

The org msg messages are in the new format, make sure that the packets are decoded in the proper way.

Edit: Also....might be that bot character have to have some special rank to see org messages.

And as I said, never really tested this...just giving you some clues on what it can be ^^

Shelnaria · « **Reply #5 on:** December 08, 2005, 04:35:57 pm »

I made sure my bots tooon was at Squad Commander rank or its equal. I havent had the issues since then.

Wolfbiter · « **Reply #6 on:** December 08, 2005, 04:55:17 pm »

It has the rank of veteran, should be able to see things.
I have patched for the new format, so that shouldn't be an issue.

Blondengy · « **Reply #7 on:** December 08, 2005, 05:43:56 pm »

Log on and make sure that the toon can acutally see org messages.
If you have an org tax, created a new character, gave him no creds, invited him into guild and then logged out he'll not recieve the guild channel cause he has tax debts...

Zarkingu · « **Reply #8 on:** December 08, 2005, 06:17:22 pm »

This is not the guild channel though, its a new channel FC made not long ago called Org. Msg.

Every rank has this channel since this is where org tower attack messages, people who join org and people who leave org messages appear.

Khalem · « **Reply #9 on:** December 09, 2005, 01:49:36 am »

Im not able to check right now. But i do belive the channel name is: [Org. Msg.]

I know the bot can see it as i used it as the testcase when initially getting the new 16.1 parsing working with Bebot (easiest way to generate messages at will, org invite and org kick

)

Wolfbiter · « **Reply #10 on:** December 09, 2005, 04:50:48 am »

Nothing at all shows up in console when org. msg. happend, and I'm clueless to as why.
The testsubject I used could see the kick msg when I kicked him, as an applicant, so the bot shouldn't have any such issues.

Blondengy · « **Reply #11 on:** December 09, 2005, 12:50:43 pm »

Quote from: "Wolfbiter"

As far as I can tell, bebot doesn't see this channel.

The console only shows channels which are beeing monitored by a plugin. Channels which no plugin wants any info on are ignored - otherwise you'd get all the OOC and Shopping channel spam in the console too.

You have to know the name of the channel and have a plugin monitor that - once that's done it'll show up in your console too. Did you do that or where you just looking for that channel in the console so far?

Wolfbiter · « **Reply #12 on:** December 09, 2005, 06:27:18 pm »

I must have been high or drunk when writing my org. msg. script.
It was '$commands["gmsg"]["group"]["Org. Msg."]'... Thanks all.