.jpg.bb0ec39358cdd187e29484a737c641af.jpg)
TEDF
-
Posts
884 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Downloads
Gallery
Articles
AVCS Bug Reports (automated)
AVCS Bug Reports (manual)
VG Wiki
Blogs
Store
Everything posted by TEDF
-
sushi LAN_WROTE ... Midnight Sun + Street 2 THANK YOU!!! Finally someone who remembers! !crazy MELON! WE WANT STREET 2!!!!!!!! STREET 2!!!!!!!! !crazy !crazy !crazy !crazy !crazy !crazy !fans
-
Hi there. To quickly clarify things - I was the one who resigned you from the squad. You got reported on TS that you made a duplicate squad for trans. As I was unable to join the server at the said time and the remote admin tool doesn't show squad names, I decided to trust the person, who reported you, and resigned you from the squad. Bingreding LAN_WROTE ... More infuriating however, was that the admins present refused to respond to my calls to rectify the problem by resigning the later squad. We all make mistakes but refusing the rectify them is absolutely appalling behavior in my opinion. The admin program froze (like it does every 10 seconds ) and I decided not to bother to open it again.
-
Love all of the INF only maps.
-
I've always wondered what's going on on the server while I'm away... !crazy
-
Personally, I discourage people to run to stationary AAs. on Muttrah when I'm doing CAS as I know where they are and I like to be the one that takes them down so I could start a respawn timer. What I usually do is warn people on chat twice and then do a hydra/hellfire run on the AA. I know that this may seem a bad habit and be pain in the arse, but it is really annoying when you have someone next to AA and knifing the gunner. Specially when knowing that bots don't have weapon cooldown timer and they can fire instantly as they spawn on the weapon. Like Semler said, communication is very important in these kind of situations, but I personally think, that inf should stay away from stationary AAs unless asked otherwise from CAS squad.
-
There's not much we can do about the server crashes as they are completly random. It can be caused by people jumping on different vehicles/weapons, bots getting random orders, placing deployable assets to random places etc. There are some maps that are known for crashing most of the times (Silent eagle) that you should avoid running. Other than that, there's not much else to do but do cross your fingers and hope that server stays. If it does crash a lot, the best thing you can do is to set up next map that was supposed to be run before crash happened.
-
-
-
-
-
Thanks for the report. Archer and Ferzpwnz have been banned. Mr.Aruba got away though. Ban will stay for a week (If they appeal for an unban).
-
Got another problem now. Server is automatically switching players on to bot team after they die or load in the game EDIT - Bots are on other team and players are not being switched, but there are 4 VG COOP servers on the list now.
-
It seems to be fixed now. The server is back on the list
-
The server is running, but only accessible via IP - 5.9.23.136
-
PR moments
-
-
Fun round on Deployment - Gaza Beach, Insurgency
-
-
-
Daily update from PR lands. Today, 2 squads entered into friendly competition to find out who's the best sniper/marksman After hours of hard fighting, one team emerged victorious. Congrats. !clap
-
Few shots from OPFOR event
-
US pilot gave the victory to MEC !crazy !punish Hello there !spite Samsppaaa after hard day at work !cool
-
PR physics Time to move out Wrrrrrrrrrrrrrrrrmmmmmm...
-
Yes! That's right. It's time for another PR coop event. All players are welcome! Start : 5 th October 2013 - 7:00 pm UTC/GMT +3 Rules : 1) standard =VG= server rules 2) for players joining ts - it is not allowed to be in any wrong channel(e. g. - lounge) - we have named channels for a reason 3) have fun Hope to see you all on the event!
-
The update seems to block players to join any old version server even if they skip it. Witnessed it yesterday when I skipped the update to join COOP, but couldn't because the account was blocked.
