Title
Also, why buff striker pvp?

The topics we're debating in the Feedback section aren't important enough (that is, they've not been heavily requested by the KR playerbase, nor are they being planned on in the slightest by the devs themselves). So, until the rng favors us and we come up with the right topic, yeah. Nothing will get promoted to AFB.

The striker needs to be buffed. Otherwise he's too weak to get his bananas, surely. 

^seems to be the case 😭

on a funny note

the latest post on adventure board, GM dug up an old post with 1 upvote and no replies re: cross server guild renewal to make a *we listened to your suggestion* post and mark it as applied

...but if you read the OP, the post was made after the calpheon ball announcement and they are suggesting something else that wasnt implemented 🤣

*edit* incase anyone new reads this thread, this is fixed now 😊 just to save you confused time looking for it

Funnily they already said that this is not possible to make them cross server due to muh "technical" reasons as answer to one of the topics, guess that was not aged well then.

lol they clearly didnt read it.....it wasnt even related to guild invites/renewals on different servers

No guys, adventure feedback not dead, its just we, players, don't guess upcoming changes correctly.

/s

Its never was a thing to begin with. Either publisher don't sumbit anything, or developers simple don't care, or both.

ye

I think at calph ball they said like "WE FIGURED OUT A WAY" which I mean, could be true. Maybe someone had a big brain moment and figured out how it could be implemented..

but I doubt it. I think they were just looking for some quick easy win projects to announce at the ball and the contract renewals were just one of those easy things.

I do wish they had implemented what that guy suggested in the post I mentioned though,  that would have been convenient. I always worry about sending someone a contract renew in the middle of grinding, if it went to a little notification that they could access any time thatd be a neat change. Or like you have said.. just remove contract expiration. idk why its even a thing.. the idea of needing to bug an officer to renew my contract all the time was very discouraging when I was a new player, so I just didnt join a guild for 9 months 😬

hehe it seems they read your post though ☺️

Pretty much this. As one of the organizers for the only thread that's still "open for discussion" on the AFB board proper, who's spoken to staff, volunteers, and former employees about why the hell the thread hasn't been labeled as reviewed and why no response has been given by current staff in like 5 months, the way things work at PA when it comes to QOL and Feedback is now pretty obvious:

1. If you don't get 200 upvotes, minimum, your thread on the Feedback forum won't get migrated to the AFB page. If it's not there, developers aren't told anything, so you're right about the normal Feedback board basically being a "guess what they planned on fixing already or nothing will happen" minigame.

2. If it's not on the AFB, and they aren't bothered by a partner, guest, or streamer about a problem at a live sponsored streaming event where negative feedback will affect their market value and scare their shareholders, the devs and executives will have no idea that a problem exists, and when they do, their poor translations mean the messages will not be received as intended.

3. The NA/EU/etc service teams *barely* find out anything any faster than we do when it comes to QOL and balance. If it's leaked or put on labs with no marketing beforehand and you're diligent you'll know things are happening before most of the GMs do. The flow of information is Executives>Marketing>Developers>Marketing Teasers or Testing Builds>GMs finally hear something/Information Leak>Players are informed.
4. When the GMs do respond to a thread, you'll notice it is not for the sake of gathering information for the developers, because the developers straight up do not listen to service staff. The GMs are responding as a token gesture to show you that *someone* looked at what you said, even if that effectively means nothing. They are handed a script or a set of criteria to meet in a response to us so that they don't pose any risk of forcing the developers to do something that the executive or marketing teams don't feel like doing.
5. Cadry's response to that other thread is basically pointless, but some of the staff are at least *trying* to tell us things are getting better and attempts are being made, so I don't begrudge them for having or wanting to share good news, even if it's not the good news the community is asking to be told.

The thing that honestly frustrates me the most is that the developers will be told to completely abandon projects that are announced or QOL that was confirmed to be in the pipeline, and nothing will be said until it finally crawls its way to whatever GM has to be responsible for telling us stuff like "sorry, shai isn't going to get jetina, dandelion, blackstar, caphras, or marketable sols" when prior official livestreams made the promise those things would exist. So things that we are told we will get, we don't, and things that we ask for directly here are just us guessing and hoping for implementation because there is now no actual way for us to present requests for features or fixes and be listened to without a filtering wall and a layer of bad google translations. If the responses are always going to be neutered and impersonal and either apologetic or self-congratulatory, the service teams shouldn't be reading and responding to these boards for anything other than like, actual forum moderation. The devs should be reading them instead, so they are at least direct witnesses to the things the community is asking for.

^ That! Cadry had a reply regarding more group focused content, reminding people that PA promised at the Ball that all bosses in Haso will be available for both, solo or group challenge. Well, the group part of that is gone (for now, at least). So while we're kinda used with PA's habit of promising stuff and then changing their minds (ice fishing, skating, etc), the GMs and CMs are in quite the pickle too. And I'm pretty sorry for them. Just as much, I'd say as the I am for the devs that made the prototypes and presented stuff to the management. Stuff which was approved, advertised, flexed at various Heidel/Calpheon Balls and then dumped like a hot potato.

All in all, there are just way too many barriers in the flow of information for the AFB to be a viable tool of communication between us and the devs. All intentional.