Configuration questions for potential new server (huge post!)

[Lucia Moore]

Originally Posted by rencro

Here is how I disable "tell, ooc, and auction", same priciple can be applied for group...

diff --git a/zone/client.cpp b/zone/client.cpp
index 533f8b5..750ff73 100644
--- a/zone/client.cpp
+++ b/zone/client.cpp
@@ -872,6 +872,9 @@ void Client::ChannelMessageReceived(uint8 chan_num, uint8 language, uint8 lang_s
 		break;
 	}
 	case 4: { // Auction
+		Message(13, "Auction is disabled."); //rencro
+			return;
+
 		if(RuleB(Chat, ServerWideAuction))
 		{
 			if(!global_channel_timer.Check())
@@ -911,6 +914,9 @@ void Client::ChannelMessageReceived(uint8 chan_num, uint8 language, uint8 lang_s
 		break;
 	}
 	case 5: { // OOC
+		Message(13, "OOC is disabled."); //rencro
+			return;
+
 		if(RuleB(Chat, ServerWideOOC))
 		{
 			if(!global_channel_timer.Check())
@@ -966,6 +972,9 @@ void Client::ChannelMessageReceived(uint8 chan_num, uint8 language, uint8 lang_s
 		break;
 	}
 	case 7: { // Tell
+		Message(13, "Tell system is disabled."); //rencro
+			return;
+
 			if(!global_channel_timer.Check())
 			{
 				if(strlen(targetname) == 0)

A lazy way of doing it but gets the job done..

Is that an entire .cpp file that I can just copy/paste into my source, or do I have to plug that in somewhere?

As I said, I know some things about programming, but I don't wanna FUBAR my code unless I can figure out where I FUBAR'd it at.

[rencro]

Originally Posted by Lucia Moore

Is that an entire .cpp file that I can just copy/paste into my source, or do I have to plug that in somewhere?

As I said, I know some things about programming, but I don't wanna FUBAR my code unless I can figure out where I FUBAR'd it at.

Thats a diff with my changes that would modify your code, but you want it for groups so you would be better going into zone/client.cpp and making the edits there yourself...

A word of warning..Once you start modifying things, it will be a chore to keep up with the tip release, so you may need to draw a line in the sand and just work from your source exclusively and perhaps cherry pick any new releases to the code manually, if at all....

Any ways:

About line 743 of zone/client.cpp

void Client::ChannelMessageReceived(uint8 chan_num, uint8 language, uint8 lang_skill, const char* orig_message, const char* targetname) {
.
.
.
	case 2: { // GroupChat
		Raid* raid = entity_list.GetRaidByClient(this);
		if(raid) {
			raid->RaidGroupSay((const char*) message, this);
			break;
		}

		Group* group = GetGroup();
		if(group != nullptr) {
			group->GroupMessage(this,language,lang_skill,(const char*) message);
		}
		break;
	}

Not sure about the raid but could try this:

void Client::ChannelMessageReceived(uint8 chan_num, uint8 language, uint8 lang_skill, const char* orig_message, const char* targetname) {
.
.
.
	case 2: { // GroupChat
		Message(13, "Group chat disabled."); //remove group chat
			return;

                Raid* raid = entity_list.GetRaidByClient(this);
		if(raid) {
			raid->RaidGroupSay((const char*) message, this);
			break;
		}

		Group* group = GetGroup();
		if(group != nullptr) {
			group->GroupMessage(this,language,lang_skill,(const char*) message);
		}
		break;
	}

Then recompile and test. If you dont like the "Group chat is disabled message, then remove it -)

[Lucia Moore]

I see. So, if I'm understanding this correctly, could I do something like this?

(Note that I can't actually see the code right now because I'm at work, so my exact syntax may be wrong)

{ // GroupChat
		Raid* raid = entity_list.GetRaidByClient(this);
		if(raid) {
			raid->Say(this,language,lang_skill,(const char*) message);
			break;
		}

		Group* group = GetGroup();
		if(group != nullptr) {
			group->Say(this,language,lang_skill,(const char*) message);
		}
		break;

In other words, just make it so that anything you say in /group comes out as /say instead?

[rencro]

Not as in that example as say is not a member of Raid or Group, but if you like you can repipe it through say, yes, there are actually few limits in what you can do, you just need to "do" it....

I went the lazy route by just disabling the feature and letting the players know it was disabled so they would use other methods, but re-writing it to use the current system as close as possible is also viable...