=VG= SemlerPDX

That is quite a lot of maps..... All those need to be removed from the map list randomizer and placed on the blacklist? Or do you mean simply remove them from the seeder/starter rotation and place them in standard rotation?

Done and done (but no one replied about the question: did we put Muttrah 128 on disabled after report that shit wouldn't work? for that reason, it remains on the disabled list until I get answer). Gotta go. Have a wonderful weekend! Will check back in case needed.

That will do - each member group can be part of the filter in Advanced Search under Members.... But that would be if you're trying to see all that info about all the different groups and members at VG.... If you just wanted to check a list of only officially tagged VG Members, Moderators, and PR Admins, just click on the Staff link instead of Members... Here's a lazy link: http://veterans-gaming.com/index.php?/staff/

These are the entries we have for the maps you noted -- are the INF layers the 16's? Wanted to verify before removing maps from the list willy-nilly: mapList.append khamisiyah gpm_coop 16 mapList.append khamisiyah gpm_coop 32 mapList.append khamisiyah gpm_coop 64 mapList.append khamisiyah gpm_coop 128 mapList.append pavlovsk_bay gpm_coop 16 mapList.append pavlovsk_bay gpm_coop 32 mapList.append pavlovsk_bay gpm_coop 64 TO CLARIFY: Should we remove Sbeneh maps? If so, which ones (be specific please)? *By remove, I mean put in standard rotation, and not starting/seeding rotations Also I thought we purposefully added Muttrah 128 to the disabled list after a report of issues with it two weeks ago? Busy packing for my trip, just taking a quick break otherwise I'd look into it further.

If you're talking in-game in PR, that has been a feature since the beginning - so people didn't have to make a new name when joining a clan, they put in a field specifically for tags separate from the username space. Surprised you didn't notice until now, you've played PR for a few minutes now... As far as people putting on false VG tags, sometimes it's someone messing around and deserving a warn and/or kick, but other times it is legitimately a brand new player (or even brand new to PC gaming in general) and is misunderstanding the concept. That was the case with Wooz, who went on to actually become a real member over time - so be sure you're understanding and giving the benefit of the doubt. Some are new, some are dumb, some are smart but just don't "get it" yet. Kindly explain it to them and welcome everyone you see who isn't a giant asshole. *edit: If you are talking about the website, that's just our extended username field which unlike most websites, allows special characters AND spaces.

Yea, that's how that happens. Impatience is paid back in data loss. Today you learned that an OS installation is specific to a motherboard, and any vast changes while the OS drive is removed from that motherboard will null and void the OS install. Good tip, if one can afford it, when upgrading PC's, keep the old hard drive separate and buy a new one for the new PC -- then install the old HDD into the new system as a secondary drive. Over time, once you pull all your data off the old drive, you can then re-format it for more space (deleting the WinOS files) with no data loss. Wish I could have told you that last week... I feel for ya, bro! It happened to me once way back when I deleted the MBR from my data drive by accidentally adding it to the RAID array - when I took it back out realizing what I did, none of the data was accessible due to the master boot record being wiped. All the data was still there, that was the most frustrating part. *On that note, there are tools to recover data from a formatted drive, but they can get expensive (or free but very risky or shady)

....so, basically, this means that:

If it makes anyone feel better, there will likely be no COOP mode for this WW2 stuff - at release, anyway - because no one wants to do the navmesh for all those new maps. So, sadly, unless someone steps up and gets cracking a little faster than a map a month, PR WW2 COOP will be a long way off....

I assume you were equally unhappy when PR Vietnam was incorporated into standard PR? I think it's a smart idea: rather than split the community through 3 different war mods, they're all in one and just dictated by the maplist choices of any given server. So, if there were numbers like the old days, someone could run a WW2 only, or Vietnam only server - or just play the cool maps they like, now and then, alongside normal PR. Well... you can make some people happy all of the time, and all people happy some of the time, but never all of the people all of the time.

mapList.append muttrah_city_2 gpm_coop 128 mapList.append kashan_desert gpm_coop 128 mapList.append karbala gpm_coop 16

We've fixed the encoding issue and it's back in action. We can make revisions as needed moving forward, and of course, take any map that is reported to be broken and place it on the Exclusions list - just let us know!

If that were true, we'd never innovate - very dark thinking, that. Luckily, we'll have it patched in a matter of minutes when we get together tomorrow and all will be well. He's the pro, and I like to play nice with others, so I don't want to insert my code into his script without running it by him first. Bugs are bugs, patches kill them. If there is someone to blame, it is microsoft once again - forcing UCS-2 LE BOM encoding on the Out-File cmdlets when the Refractor 2 engine that runs the game reads only non-BOM UTF-8 encoding.

There was a small issue with the launch of this system, specifically the encoding of the final output file is incorrect. Will work with Xenalite first thing tomorrow to get it updated. Until then, I have disabled the Randomizer and have restored the previous maplist. One more day of "Muttrah Restarts" for you lot

*FYI: If a map is not relatively easy for most players and tickets do not bleed on the last flag, the map will not be found in the seeding maps list. Also, force restarting the server through TCAdmin will not force the maplist to randomize. I may create a button for that purpose so it can be manually executed if needed, though the need would be rare. edit: Added button to TCAdmin web panel, in case needed. SOP is to stop server, edit disabled maps list if needed and/or click button and wait for it to complete, then start server again. (*randomizer runs naturally every 30 minutes regardless of server restarts, or whether server is stopped or online)

VETERANS-GAMING is Proud to Announce a New System for our Project Reality COOP Server: Huge thanks goes to Xenalite for creating this system - next time the server crashes, and you DON'T have to play Muttrah once again, be sure to give him your thanks!! In the past, we have used systems that forced the server to restart at a certain time once a day to change to one of 4 pre-set maplists that we created. Though this was a great start to relieving the annoyance of playing Muttrah after every crash or restart, it introduced another annoyance in the forced restart itself and never really removed the problem of playing the same map over and over in one day surrounding crashes or restarts. This randomizer will ensure that the VG Project Reality Server map rotation will remain fresh and new after every restart or server crash. Each time the server restarts or crashes, a new maplist will take effect, with the first several maps being chosen from a select few we know to be good seeding maps. VG PR Maplist Randomizer features: Randomizes the map list, with a unique map at the beginning (following a crash or restart). Excludes maps (which we place on a list) that were broken by an update or otherwise undesired on our maplist. Starter maps are random and unique, i.e. No 2 of the same map in first 10 rounds. Round 11 and on are non-starter maps taken from discarded starter maps and all other enabled maps. Remaining maps are random and non-adjacent, i.e. No 2 of the same map back-to-back. If a map is on disabled maps list, it will never appear in the final map list. The odds of playing the same starter map after crash is max 2% when running as designed

Roger that. Universal Plug and Play is quite different than disabling an entire comm protocol for speed or security purposes. Glad you cleared that up. If one is going to manually configure port forwarding for the various internet gaming software(s) they may use, uPnP can be disabled without causing any issues. uPnP is an automatic system to decide what traffic goes to which computer on the router, and so it's going to come down to the router (or modem) manufacturer and the software/firmware handling the uPnP tasks as to whether it's any good at it. Great for some ideas, but for gaming/hobbyist applications where you do the work yourself to tell it what traffic on what ports goes to which IP on the router, it can get in the way. Concerning the "pro persons" at avast, I would say that unless you get one to talk to you directly with knowledge of your home computer/internet setup and speed, you are getting "blanket knowledge" that does not always apply to a specific person or situation. In that way, I recommend to avoid listening to that kind of advice where no further information is provided as to why/how and what is happening when you do the thing they "recommend". Do the hard work and research things yourself as needed - it usually doesn't take long to brief yourself on a new or foreign concept, especially if you already have some basic knowledge to build upon. Knowledge is power. Always remember, "First jou get the power, then jou get the money, then jou get the weeemen". (...or is it money first? lol) glad you enjoy my old ass movie references haha

Then we moved there after the new server switch awhile ago. Either way, it's not Kassel. Just wanted to point that out.

Well, it's not. Not sure where that information came from, but I don't always know how networks and the infrastructures connect. I just know where our server is physically located, in a massive datacenter... more than 200 km from Kassel in Vogtlandkreis. They have another datacenter in Nürnberg, but still that's quite a distance from Kassel. Just FYI Thank you so much for your help @0100011000101! I know ranger must be feeling pretty helpless and alone with this issue, but you have provided some much needed expertise and experience in troubleshooting his problems, and all of us need a guy like you to help out once in awhile when we hit a wall. Cheers, bro! Hope you guys can get to the bottom of this! I can assure you we have nothing running on the server that would cause these fairly regular interruptions in his otherwise stable connection to our server. Furthermore, he is the ONLY person out of many, many people who regularly play on this server every day that has this very specific issue. Common sense tells me that this issue needs to be examined first from his end as we have been doing. Getting more information directly around the time when these disconnects actually occur would be invaluable - that should be a major focus of this troubleshooting effort, if possible. ..... WRONG!! (just messing with you, WarGhost - don't take it personal) SERIOUSLY THOUGH - NO ONE READING THIS SHOULD DISABLE ANY UDP MODE ON THEIR ROUTER UNLESS WELL EDUCATED ON WHAT YOU ARE DOING WHEN YOU DO THIS! Please do not re-post "shot in the dark" suggestions you may have found on some random webpage like this without any further information describing why, how, or in what way this would benefit anyone. There is a reason to "try" turning a thing off for a test, but a blanket rule of "turn off UDP mode" without respect for other games or activities on that computer is just bad practice. This would most likely introduce MORE lag in his multiplayer online games (even if not PR itself). That one is up there with "put the computer's IP in the router's DMZ and leave it there". Don't do this! There may be a reason for ranger's intermittent disconnects when he has an otherwise stable connection, but unless it's shown that it is due to an unacceptable drop rate on his end of the connection, UDP and TCP should both be made available to his router. *connecting to the internet is a possible breach - everything is; primary communications protocols are about as broad a term to use for a "potential breach".... just sayin.