Join the official Goodgame Big Farm Discord today!
Are you looking for a community of like-minded farmers to discuss your farming experience with? Look no further than the GoodGame Big Farm Discord Server!
Our server is the perfect place to connect with other farmers from around the world. Whether you're looking to chat about strategy, share tips and tricks, or just make new friends, our community has got you covered.
And that's not all - as a member of our Discord server, you'll also have access to exclusive giveaways and other special events. It's the perfect way to stay up to date on all the latest news and updates from GoodGame Studios.
So what are you waiting for? Join the GoodGame Big Farm Discord Server today and start connecting with fellow farmers from all over the world. Just click here to join the fun!
Comments
Back at the issue of this topic... There are a handful of players who visit & make comments [ to which i have seen.] on forum, but there are a lot of players that don't come to the forum site. A lot of good information from repeated players with valid view points. What of those players in coops who don't see all this information on forum. Their coops could fall in same situation we had. With this added feature '' last known coop'' could be an asset. It is the decision of the Leader or Deputy to contact former Coop Leaders if they wish to. If this feature was added, i think some will not use it, but some will.
After getting burned once we have stopped accepting new members around start of VF. Which is sad tbh because we therebye sort of accuse them (and maybe) wrongfully for being sent by another co-op with the mission to ruin the VF for us. Iiiiif the last co-op they were a member of were added to the application we would have a better way of treating them right. Accept right away or reject. We can mail them and ask what co-op they left, but we can´t really believe what they tell us. Not with the VF about to start.
That is why I support u think (US1). It would be an asset to get the former co-ops name on the application. It would be on mine as well should I wish to leave my co-op and join another and - it´s OK by me!
Another point would also be that if the last co-op we are a member of were on the application - it would prevent the co-ops from using "plant a member to ruin the VF" strategy. It would put a stop to it. Ofc there are always ways around stil doing so, but it would mean more hazzle and fewer would bother.
This is why I keep on pushing for u think (US1)s suggestion.
Cheers
Had I known about this Forum and all the good information. I might still be in my own co-op - still struggling but getting somewhere.
I think player '' u think '' has something good going here. Having ''Last known co-op" is having a step up from NOT knowing. Us little people/co-ops want good players just like the rest of us. But having the "last known co-op" on player's info is a good thing to have.
Maybe if it gets added to the game - I might consider starting up another co-op.
I just wanted to voice my opinion..
Pros and cons, points of view make a discussion. Pref a good one.
Cheers
THIS IS A GAME NOT REAL LIFE
If you are the leader of a coop and a new member comes in and you do not like them boot them simple as that. If a game gets to the point we need background checks it is then it is no longer a game.
As I believe we can all accept that at times we could feel tempted to or even do post ventilating heartsighs here at the forum too. So we take posts like that for what it is, heartsigh, and concentrate on the reason for the post instead. Not get hung up on the heartsigh part. Right?
Some thoughts do spring to mind from what she writes.
Because could it be that we are only thinking of ourselves and not the bigger picture?
hmm could some of those who object actually be the ones using "plant a member to ruin the VF" strategy and fight to be able to keep it?
Thoughts.
the new co-op wanting to get good players, and a player leaving a co-op that was a bad fit who might bad-mouth them to the new one.
-
I left my long-time co-op and started my own a while back, due to a deputy who started... acting badly, after the leader had health problems and had to leave.
If anyone had sent her a message she would have given me a very bad report. (Especially as 5 other people later joined me in the new co-op for the same reason.)
-
One would need to take the previous co-op's response with a grain of salt.
For the more established co-ops it would be a great tool around the couple of weeks before the VF starts. Unfortunatelly we have experienced co-ops using the "plant a member to ruin the VF" strategy. Their aim is to ruin the VF for another competing co-op and by that gain maybe, but hopefully 1st place. Using that strategy ups their chances. And as it is now, they succeed if they manage to get their member accepted at the competing co-op. There is nothing stopping that member from starting a killer 13 hour challenge. And continue doing so unless the leader of the co-op is a hard nail immediately kicking out new members in spite of no real proff. Few leaders are hard nails....
Another point would also be that if the last co-op we are a member of were on the application - it would prevent the co-ops from using "plant a member to ruin the VF" strategy. It would put a stop to it. Ofc there are always ways around still doing so, but it would mean more hazzle and fewer would bother.
Sooo with `last known co-op` on applications both the new/smaller and more established co-ops will benefit.
Mind you `last known co-op` must be put auto on the application and not filled in by the applicant. That would make the info non valid = be of no help.
I believe all co-ops can benefit this request of ' last known co-op'. So now that all this has been said.. Where does this request go to now? To hopefully get it added to the game...??
Cheers
Cheers
only leaders/deputies can start VF challenges
activity chat log shows which deputy starts a VF challenge
activity chat log shows which deputy starts a co-op project
activity chat log shows which deputy starts co-op boosters for co-op events: CC, CHWE, etc.
activity chat log shows which deputy starts a village building upgrade
...any action that involves starting a co-op related activity should chat log the player who starts it.
...then there wouldn't be a need to instill background checks on players trying to join a co-op.
I am sure there are some Cooperatives out there who had this happen to them.. they would know what it feels like to be shut down for many hours ..and you can not do anything about it ..but wait it out. But for those Cooperatives who havent had the pleasure of being shut down for many hours .. can not fathom it.
Our coop is in the Diamond League.. we were in the 11th in the rankings of 1st shut down. By time both players were removed, and the finish of the Village Fair. Our rankings dropped down to the 30th position. The 28 hr shut down.. not a good feeling.
If the ' last know coop ' could get attached to the player's info on applying to any coop ( especially when Village Fair is in play) who are from another cooperative. It should raise some ' red flags'... to cease the accepting. Without it... it is the chances you take.
We learned a hard lesson... i get it ..that in future will not accept anyone in coop prior to Village Fair.. but then again, what if the person is the real thing not out to harm, and we turn them away even with a message ..to accept them after the event. What is it to say that the player in waiting to be accepted, get this kind of message. Is it fair to them to be put on hold because of an event. I dont think it is, they will go somewhere else and we would lose a good player. It is a catch 22 situation.
The ' last known coop' will benefit everyone.. all coops.
good idea, that way they can't go in 1 day before and start a 12 hour challenge, just like it used to be with the village league too.
Yep I agree. once the damage is done, the chat log will only tell which player did it. yet at least you can boot them from the co-op. Then no repeat offense would occur.
With regards to the "last known coop," I would have that list extended to "last 5 known coop." Because a player could be sneaky about it-- just bounce around co-ops and 'play the part' before joining the intended 'mark.'
So in the meantime.. .the leader would have to ask the applicant beforehand, "what co-ops have you play for?" Then speak with leader/s of those co-ops for references. A cumbersome job for leaders to deal with, if you ask me.
You are also forgetting this part of the reason why the previous co-ops name is wished for. Copied from my reply posted 13:04.2019 addressing autumnsharon20 (US1) and juliette9 (US1)s inputs :
It would be an asset for all co-ops.
Cheers
LOL....I did say "last known co-op" should be extended "last known 5 co-op."
Whether that info is used to detect potential harm-doers,
or be used to determine a players worth/experience to the co-op,
I agree, knowing an applicant's last-known co-op history is beneficial in both cases.
I was simply replying to the original poster's incident, where I feel-- just knowing the applicant's "last known co-op" would not be enough to stop a "harm doer" from infiltrating the co-op.
Joining a co-op is easy...
Its what regular members are being allowed to do is where is the problem begins:
...start VF challenges
...and the lack of chat activity not documenting who is starting activities like starting boosters, starting projects. etc.
Cheers
But I looked at this ' last known co-op' would definitely benefit the new cooperative starting up.