Review bomb time?
This sort of attitude is absolutely degenerate.
| |
Waa Waa Waa!
Someone call the Waambulance! ~Hear 'em Howl~
Tommy Bolin's Wild Dogs off the album titled "Teaser" |
![]() |
Actually read the whole thing you forgot to mention why the reviewbomb and also no one cares about review bombing poe this game had ups and downs for long years now, on the last part where you actually made a point that it scares new people why ? Is there no Elden Ring dominating the market or any other hard game why should the game be easy and get finished in a week by a random casual we already have something like that on the market its d4. So as you said poe caters to a niche market apart from the bugs and issues theyre doing great.
|
![]() |
" I did but ill spell it out again. As EA isnt an excuse to do whatever players buy it and play it and form their opinion of the game right than and there. Regardless of if it is fair or not first impressions are key EA or not. So the logic is as follows. If GGG still hasnt learned from POE1 than we need to remove the enticement for folks new to POE to not touch this until they learn they cant be jack wagons with giga chad nerfs right out the gate. Because if POE2 is your first experience with GGG and you just had a CoX build there is a pretty good chance they will quit and never come back. So lets try to prevent that and instead when someone picks the game up have a better chance at getting them to be a very long term player, as that is a win win for everyone. Toss a Chaos to your Leader
OH Red Maps a Plenty oh Red Maps a Plenty OHHH Toss a Chaos to your Leader |
![]() |
If you don't give feedback, the group cannot engage in improving their customer service. This damages the company far more long term than it does in the short term. The smaller the business, the worse this effect is.
If the group providing the service is quick and reactive enough, it can stop the problem in it's tracks. They could have patched in free gold for the people using those skills for a free respec the next day, but they chose not to. This is a forum with a section that has feedback in it for that purpose. The idea that "boycotting" is better than complaining, coming from a small business perspective, is pretty amusing. The first person to give you honest criticism, rather than building up pressure and exploding with anger and damaging your business by telling people not to go there, is very important. Would you rather everyone just silently stopped playing and they lost half their playerbase for reasons they can't determine? Now, if you consistently wallow in in recreational complaining or outrage, sure, but consistently hiding what you feel is doing no one any favors. It also doesn't make you cool, tough, and super manly. You play POE, paid for a game that is going to be released for free in the future, and are on a POE forum with a made up name with a 4 digit number after it. Try to sound cool to anyone that doesn't play video games regularly while explaining why the 4 digit number is necessary and what you do on this forum. Last edited by Gigs#6884 on Dec 13, 2024, 11:55:41 AM
| |
" Yup pretty much defines this thread. |
![]() |
In this thread: Waaaaaaaaaaaaaaaahhhhh
|
![]() |
Just manage refunds fast since many people like me just regret offering the support.
Then you enjoyers enjoy your refreshing community experience. Problem solved. It's not even rocket science. |
![]() |
This is pathetic.
|
![]() |
Just want to say I play lots of summoners in ARPG and even though my first character in PoE2 got hurt by nerfs I am still having tons of fun.
Review bombing is not a good behavior. The game is in Early-Access which is a period where developers adjust/develop/change and balance stuff based on player's feedback. Baldur's Gate 3 had Early-Access for few years and it was one of the reasons the game became the massive success that it was. The same thing goes for PoE 2. By all means, provide feedback, complain about things you don't like, but never go for such a thing as a review bomb. It does nothing but cause chaos. |
![]() |