Forums

12-Mar-2015 23:44:30

Mod Maz said :

That's part of the problem. We DON'T track this data. So if you have someone who is disgruntled with the clan and queues 500 people to join... you'd have no way to find out.

I see what you are doing then, future proofing a bit. I will keep this in mind when thinking of a modified solution/new solution.

On a lighter note, I would probably want to promote that disgruntled clanmate for their amazing recruiting skills!

AO

Deputy-Owner :

The Nexus CC

13-Mar-2015 14:13:04

Mod Matthe said :

Until you realize they have invited all the bots they have been using and have traded with most of your Clan and half of you are banned as Gold Farmers...

It is not so much future proofing as making sure we include oversight as and where we can rather than having to back hack it in later when it becomes a demanded feature that some players cannot understand why we would ever have released without it



Good point about the bots!

It sounds like if you are going to want to add a meta-data feature with any solution, (Who invited you, what time they invited you...) you would have to "back hack" it in. And to me it sounds like a pain any way you look at it. It would probably require a new database junction table, since it is a many to many relationship...

Then again, if that is a required feature, (although probably not considered kosher) you could temporarily store more information about who recruited/time recruited in the player data, and then at the point they were autojoined that data could be transposed to the appropriate tables.

But I am sure this would be just as much a technical headache... So I will keep thinking about some other solutions.

EDIT:

What am I thinking... The recruiting player would have access to the clan data when they "Invite/que". Theoretically, wouldn't the recruiting session have access to write to the required tables, even though they aren't added immediately?

AO

Deputy-Owner :

The Nexus CC

13-Mar-2015 14:53:35 - Last edited on 13-Mar-2015 15:00:22 by AoDude

13-Mar-2015 15:59:59 - Last edited on 13-Mar-2015 16:01:15 by AoDude

Mod Matthe said :

Merging both systems -

This would still leave a number of issues outstanding that we cannot see a way to technically resolve while running a hybrid of the two.

I'm sorry but could you clarify a few things for me? Because a hybrid system would tick off pretty much all the criteria if you'd add a few things like block orts for the seven days since you've left the clan and blocking access to the clan cup for the seven days. But if it doesn't tick off all criteria then I'd like the hear which. But then you can still join a clan which solves the key problem here.

Because lets face it new players have just one chance to find the perfect clan or else they'll be blocked from being in a clan for 7 days before they can try again. But lets face it the odds of finding the perfect clan straight away are nil to none. Like it took me a good chunk of my rs career to get to where I am today and I had to visit quite a few clans just find out the difference between a stable clan and one that is on the verge of falling apart. Would I have been able to get where I am if this system was in place in those years I was actively looking for a clan? Who knows?

But unlike the new ranks or guest whitelist the hybrid system isn't a half measure.

But if you were talking about actually implementing this into the code. Well the information from wether or not the info that you were in a clan and have left it does carry over so in theory it should work. But unfortunately this is where my knowledge on the subject ends.

But I say we should put the old system, new system and the hybrid system to the polls to see what player think is best. But this probably won't happen. I'm actually not even sure if you'll take the time to answer this. The statement below is false.
The statement above is true.

15-Mar-2015 04:13:42 - Last edited on 15-Mar-2015 04:29:25 by Ashlin107

15-Mar-2015 13:34:17

16-Mar-2015 00:59:06