Okay, so on July 28th, 2020, Warzones became a perpetual hell for me. The patch notes for 6.1.2d state that wins in Warzones, both ranked and unranked, are required for daily and weekly progression. I can see this being a needed feature for ranked arenas, as they take less time to complete than the typical 8v8 bloodbath, so I'd highly recommend reverting the change on unranked, but keep it for ranked. That might reduce the number of active leaver penalties at any given time, if the losing team gets some mission progression from doing an unranked match. Now, my judgement regarding the LEAVER PENALTY: Sure, it'll deter people from exiting Warzones prematurely, but keep in mind that not everybody has a solid internet connection at all times. I believe that the Leaver Penalty should only apply to people who physically click on the Leave Warzone Button located on the minimap. That way, people who disconnect due to latency issues, denial of service attacks, or power loss don't get angry when they still have a lockout upon logging back in. There will be people who use this as an exploit to get out of Warzones, I'm sure, but nobody should have to see a lock on their Warzone queue unless they deserve it. As for a recommendation regarding the leaver penalty, I say keep it, but exclude players who lose their connection to the server. I know that players will try to use this to get out of Warzones prematurely if they are close to rage quitting, but I think there's a solution to that, as well. If a player disconnects from SWTOR, there should be a record of how it happened, whether it be a forced application shutdown (Alt+F4), or an issue related to latency. Having an anti cheat system that logs this kind of information for Warzone participants might help regulate the problem. If this kind of system does actually end up being used, I'd also recommend applying it to PvE Group Finder. If the development team won't budge on these grounds, then I have a third suggestion: Let the playerbase choose which maps they would like to queue for. To balance the ability to choose, however, would involve scaling the rewards from Warzones by the amount of maps you are queued for. Me personally, I would exclude all of the arena unranked maps from my queue list simply because my chances of winning in those are much slimmer than that of an 8v8. They may take less time, but the chances of slipping up in those matches are much higher than the other type of Warzone. I hope that these suggestions make sense, and haven't offended anybody. Thanks for your time!

Even though this thread is related to PvP, I believe that this should have been posted in the Suggestion Box located within General Discussion.

I did a complete reinstall of the game and managed to pull the characters in question off of Onderon, but I'm thinking that the file dump creation error, labeled as "volmgr" actually damages my game files, and causes future crashes on the same spot. Before the reinstall, each time I logged into this character, my computer shut down and rebooted, and did another file dump creation error each time. Worse still, Onderon and Mek-Sha are actually on the same asset file, labeled as swtor_main_area_onslaught_1.tor. I couldn't find a swtor_en-us_area_onderon_1.tor file anywhere. Anything post-3.0 is listed as either kotfe, kotet, or onslaught.tor. While the files are more tightly bound, that also means that the files can be corrupted by file damage much easier.

Onderon is BROKEN. Reason: Hardware/System Strain/Map instability. Information derived from the Event Viewer is located below. The date listed is also not the only time this has happened. UNEXPECTED COMPUTER SHUTDOWN DETECTED. DATE/TIME: 7/14/2020 5:02:59 PM US EDT; SOURCE: Kernel-Power; EVENT ID: 41. KERNEL POWER ERROR PRECEDED BY ERROR SOURCE volmgr; EVENT ID: 161, 7 SECONDS BEFORE SHUTDOWN Operating System: Windows 10 Pro Processor: Intel Core i5-9400 CPU @ 2.90GHz 2.90 GHz Installed Memory (RAM): 32.0 GB (31.8 GB usable) System Type: 64-bit OS, x64-based processor Computer Model: Alienware Aurora R9 Display Adapters: NVIDIA GeForce RTX 2060 SUPER, Intel UHD Graphics 630 (Intel not in use) If this isn't enough to avoid system failure while playing on Onderon, then there's going to be problems for me playing this game. NOTE: I can also hear my hardware straining while playing on ANY Onslaught Maps, although Onderon is the only one that causes crashes, as of now. Stabilize your maps, please. I have a character stuck on Onderon because of this nastiness. I might have two stuck there now, if the strain applies across the entire map. UPDATE: Spoke to a player in-game who said that my game files for Onderon and Mek-Sha could be corrupted. Going to attempt the in-game repair. If this does not resolve the issue, then my assumptions regarding map instability still stand.

Hmm. That's just plain odd. Anyways, if you could pass some judgement on the suggested changes I listed, that would be greatly appreciated, thanks!

Also, what time zone is the forums on, because the post shows 9:07 PM, when it should be around 4:07 PM. Edit: Why would the Forum server time be set to Central European Time rather than an American time? Do I need to swap forums or something?

Okay, so I've noted the gathering skill changes made at the beginning of Update 4.0, and I'd rather say that the main anti-perk is rather troublesome, as I need to gather certain particular nodes as quickly as possible, especially droids and creatures lying dead on the ground. I need a solution, as I would very much like to scavenge and bio-analyze every droid and creature I kill, and seeing potential mats disappear before I can loot them is aggravating. New parameters need to be introduced so that this does not happen. I will list possible solutions to this problem below. 1: Re-introduce alacrity into crew skill gathering (not likely, since the developers intentionally took it away for various reasons) 2: Remove the pickup requirement for players and transfer gathered mats straight into the inventory, like companions do. 3: Prevent potential enemies that can be scavenged or bio-analyzed from spawning out of the world, so long as the player who killed/looted the NPC remains within 30 meters of the downed target. 4: Introduce 1-3 legacy perks that reduce gathering skill time by a maximum of 0.9 seconds for players (Excluding Slicing) I don't expect this to be acted on immediately, but I'd like to see the last of the crew skill nuisances mitigated, and this is a big one for me. As usual, I expect the development team to continue as they see fit, however they manage nowadays. I don't know how many have come back from Anthem as of now, but SWTOR's development community should be gaining its population back if they ever had people switch to begin with. Also, is there a way to separate my account username from my display name on forums, because I don't exactly want to wave around half of my account information for everybody to see. I consider it a major security breach, and I'll run the laps around this racetrack to get this loophole closed off. Other than that, I have no other concerns relevant to the original issue, and no further questions regarding the forums themselves. Again, keep it up, and I'll see everybody in-game!

If Ossus has any RNG whatsoever, they should at least be more considerate of what discipline the player is using, like no Primeval Fatesealer Relics for DPS, dump Accuracy Earpieces and Implants out the window, etc.

Okay, I have the segment for the Trooper's current galaxy map soundtrack recorded and ready for playback. Location of video online is As for the normal recording of the original soundtrack playing, no, I don't believe that I kept record of the galaxy map for Trooper, but I can check if need be. And while you're all at it, I'd like someone to tag the music in the video that I linked.

Update: Looks like Bioware came through with this request, or somebody demanded this before I did. Either way, I'm super happy and excited! GG!

It depends on what settings you have your buff tray set to via your user interface editor. Mine could just be out of whack and not set up properly. They should just make a setting where legacy buffs always appear in front of everything else, and be done with it, because I'm sick of removing and re-applying crap to get things to line up.

I'll have to load up Bandicam and record it through the game window. Do you want the file sent somewhere in particular, because I'll need a location to send it to if you would like it.

I learned a good chunk of what this game has to offer on my own, because I have been a loner for the longest time. I am a freaking misfit who complains more than runs content because nobody jumps into my group and says: "BUCKLE UP, LET'S ROLL!" The Oricon quest chain is a primary example of a Bioware roadblock. Treats you to some solo content, then throws 2 ops in your face to break through. Unless you have an already-prepared raid team ready to punch in, you're going to have to assemble a pug group, and those can take 15 minutes to several hours to assemble, depending on your server and your social status on the Allies and Fleet chat channels. I don't like waiting to assemble ops teams, particularly if I have a quest chain to eradicate, and abandoning them isn't an option, so some sort of solution must be devised. Maybe make a solo mode DF and DP specifically for the chain, or something like that? I dunno. I'll address this particular problem in a different thread to keep things separate.

Various NPCs will be taller than you regardless of your body type, like champion-rated opponents. Notable examples include Revan, Ruugar, Coratanni, or any humanoid champ out there.

BRKMSN, the core buffs are supposed to line up a certain way once you enter an instance in the game, but things like death and stims reaching the end of their lifetimes can throw the balance off. You can't move buffs around in your tray because they're locked in place. You have to remove them and put them back on, and that's a pain if you have buffs that aren't removable, like the CXP and XP boosts. The reason I find it annoying is because I need to see which abilities are able to proc because of chance based passive abilities that can screw up a rotation if you think they're active, but they really aren't. Example: Keening for Vigilance Guardian procs Whirling Blade, but only has a 30% chance of hitting, so you have to have all 3 burns active, as well as using Blade Barrage to make it happen. If that doesn't work, then you have to go out of your way to find Saber Throw, and use that in Whirling Blade's place before you lose out on further DPS. You can only do that if your proc lights are in working order, or if you can read your buff tray, which is hard to do after you have died once in an instance, because everything's all over the place, and it's overwhelming, at least to me.