![]() |
![]() |
#1 |
Junior Member
Join Date: Nov 2007
Posts: 3
|
![]()
I’ve been having problems using Ventrilo 3 on my university’s network recently and apparantly there’s been a lot of questions floating as to when a patch will be available for the now UDP reliant Vent3. So I posted the following on the Ventrilo 3 forums:
When asked in the post (”Are we going to get some answers?“) about what university/college students should do to solve for getting stuck on “MSG: Contacting server.”, Flagship writes:Originally Posted by Flagship ![]() My first reaction was “You have got to be joking me. What cloud is he living on?” Most IT departments are not just going to unblock traffic for a small group of gamers who live on campus- much less a single student’s request. I’ve tried this route, it’s a policy change… It runs through a bureaucracy where if one person on that ladder says no, it’s dead. Additionally, you fail to outline what “adjustments” should be made to support Ventrilo 3. Ventrilo 2.x worked. Ventrilo 3.x broke. Here’s what your (mainly University/College) users are saying:
You’re not only toying with your users, but also with the users of Ventrilo server companies. You are now playing with the lifeblood of server companies who maintain themselves through your product. They can’t answer questions when something like this happens to a product they didn’t make. It’s not their responsibility, please don’t put them into this position. It just frustrates users even more. Flag, I’m formally asking you, as a longtime user of Ventrilo, to talk to your community. You’re a developer, sometimes as developers we just want to push out our project when we think it’s ready, only to turn out that there is an extra feature (scope creep) that someone wanted or there was some bug that needed to be fixed. That’s understandable, however just leaving them in the dark is something else entirely. |
![]() |
![]() |
![]() |
#2 |
just tryin to help
Join Date: Jul 2006
Location: Local Space/Time Continuum
Posts: 23,463
|
![]() |
![]() |
![]() |
![]() |
Thread Tools | |
Display Modes | |
|
|