There are also posters at that board who agree with the attempted bombing even if they didn't participate, and like the idea that HVS took the low road. And a few who are claiming that the negative reviews were posted by anti-HVS people in an attempt to make HVS look like bad guys.
Nearly every single time that this happens the stupid fucks get caught and the bad press and counter-measures persist.
Does there really need to be a 'Don't be a fucktard.' clause placed into any contracts signed when people are hired? I mean, sure, be an asshole...I can respect that...but this is just plain dumbassery.
Murdock was thoroughly unprofessional--and all they did was give him a good ribbing for it.
Everything in the review seems believable to me. It seems most people think the voice acting is bad, even some of the HVS fans. The ending is laughable, though it does have some logic to it if you know the backstory.
Wii remote controls is a personal area. Some hate them while others love them. Some Conduit fans don't like Conduit 2 because it took away some options. Worse, there are bugs in the game that affect aiming, which the reviewer might have encountered. As for CCP support, HVS admitted they didn't put much work into that, and didn't want it in the first place.
Graphics is iffy. Some people praised Conduit 1, while others thought it was pretty bad. Conduit 2 has some things that look nice, but others again look bad. Level design I can't comment much upon, but level design in Conduit 1 was terrible. After it was released, HVS claimed they didn't have time to make good levels. But HVS has a bad reputation and a history of poor games, so it is as believable that they just don't know how to make a good one.
The only problem with the review is the knock against the multiplayer, and that only because he knocks it for the same things that other multiplayer games do with their equipment unlock systems.
Mind, if he had played the multiplayer mode more, his review might have included some of the many other bugs that the game shipped with, like respawning in the sky to fall to your death, the walk outside the map glitches, the texture color glitches, or any of the rest. Or played Invasion split-screen to experience enemies spawning under the map or in other nearly unreachable areas, or its game-stopping lock-ups. Or just general split-screen to see how shoddy its implementation is, where players 2-4 can't even pick their own colors or have their own profiles.
remember a couple of years ago when endless amounts of assholes tried to spoil the last two Harry Potter books for everyone?
As Conduit 2 supports game patches (though a bit clumsily in execution), HVS looked to the board to report bugs. At first, bug reports were scattered in separate topics. HVS started a single bug report thread and asked all bug reports to be files there, the reason given was to make them more visible. The thread quickly grew in size, and HVS eventually asked people to post new bug reports in their own threads, the reason given was to make them more visible. (Although board activity is still high enough that individual bug reports tend to get lost between the other posts. The main thing the policy change seems to do is downplay the existence of a massive bug report thread, and make new reports quickly fade from view.)
Mind, HVS also initially encouraged people to post YouTube videos of reported bugs, and link to them in their bug reports. Fairly recently, with people *still* finding new exploits and bugs, HVS has asked people to stop posting YouTube videos.
Yes, I have read it but don't own it.
High Voltage is a developer i will not be looking to support anytime soon.
I too hope he didn't get paid and the editor should also be ashamed.
And to people comparing his review to one of Jim's. Jim may be "controversial" if by controversial you mean occasionally giving a lower score than other critics to big name games but I've never seen anything flat out wrong in his reviews.
It's one thing to defend yourself in a blog, and another to completely trash some guy's book that the dev probably never read. The reviewer actually played Conduit 2, and he thought it sucked.
Also, I absolutely loath developers who cannot take criticism. I've seen it in a lot of places - the Hydrophobia devs stalked review outlets and tried to push people to give their game a better score - Two Worlds II had a major debacle involving a similar issue - Gearbox Software literally banned people who had legitimate complaints about Borderland's [many] launch issues and glitches (EA did the same thing with Dragon Age II naysayers).
The key here is that we have freedom of the press. The guy didn't like the game - so he said so. If developers start taking away our freedom to, you know, review things, out of fear of reprisal, that's...borderline illegal.
Posted attention-getting negative review like critics do. (+1)
Posted a spoiler which is marked in the review. (0)
Wrote some discworld-type generic fantasy novel. (yea, good point, -1)
Corso:
Made a Wii FPS. (-1)
Come to think of it, made any FPS without mouse/keyboard. (-1)
Mad a sequel to "The Conduit." (-1)
Tried to fight negative criticism Kevin Smith style. (-1)
Advantage Murdock. Look, you take down one of the thousands of quasi-employed individuals reviewing games online, and you're only going to open up that space for another one. And they all don't like the Conduit.
But I would urge people to watch a youtube or a quicklook or something before diving in.
That being said, it's completely unprofessional to go and trash his book just because he didn't like the game. That's quite nearly as bad as bribing someone to review your game positively.

surf dtoid with 

Rising (10+)
People you follow
















follow