It's reverted to try and fix the bug, not because we don't want you to get the 2nd skill at 10 points. If it works, we'll reimplement without the bug.
Overall: -Names on bodies is awesome. -I'll give diminishing returns on refineries a try. -I'll give the sudden death changes a try if you can get Vicki to host emp_district402 on bloody VIPER's (and emp_escort, ask for emp_escort too). -Otherwise I love most of these changes and I think they will make Empires a much better game. It doesn't have everything I thought it would from Suggestions but I'm sure they'll come eventually. If Sudden Death makes district worse than it already is then I'll join the bandwagon to remove it. +1, I agree. Forcing users to join a squad for their skill promotes nothing but teamwork. Squad menu should automatically display upon joining a team or it should force users into the first open squad. SPECPIRES DOESN'T ALWAYS WIN? Q_Q Q_Q This expands on my overall. My one concern is will commanders be able to use A to see all enemies in an area or will it be reduced to one as well? Unless they only make WWII games in which case they would accept a beer. And I'm glad you didn't say ramen, I would have been very angry. I love 2nd skill at 10 points, thank you for not just deciding to banhammer it. Also, what was the skill bug? No, play singleplayer with bots, don't be a noob.
I don't mind ramen.. but, its takes too much effort to make. cup noodles is soo much better tasting and easier to prepare. Open cup poor water in and nuke it for 2 mins. close lid wait 2 mins. eat.
Wrong. Forcing people to join squads to get the skill meant that no-one actively made a point of joining the squad, so they never played with it. I was in your position back when this used to be like that in 2.12, but when it got removed, you noticed that the people in squads were doing squad work, and the people in them weren't. Beforehand, everyone just joined and no-one paid attention as to what squad they were in, they were just doing it for the skill. It's better to make it a conscious decision to join squads. Just because someone is in a squad does not automatically mean they will work with the squad. You can already use the A-box to see all enemies in an area now. That's the honest truth as to why all the oldfag commanders are much better than the newfag ones. People who started playing after targets were removed have no idea about this, whereas we use this to constantly scan every area. I have no issues with this at all. And the skill bug is where skills stopped working in the 2nd, 3rd and 4th slot on some occasions. If this fixes that, then we'll redo it from scratch and allow the boundaries to be more moddable. Chances are that we'd go with a 15, 30 and 45 split.
That's why I added the contradictory statement of saying people should automatically join a squad on join, in which case they would unlock the skill regardless. I wasn't combining them; I was appealing to either-or. I think your point actually applied to my other statement better than the first. If you lock the skill until they join a squad, then squad leaders can just kick loner players and the players who don't know how to join a squad are 'punished' until they listen to the team while they tell the player to press C. I like that because then the lone wolf or the French or the Chinese player not in a squad has to join one. Yeah, that's what I feared was that attack targets restricted to 1 would also restrict the commander to 1. Well that's bad, I don't know if it's ever happened to me and if it has I'm glad it's been fixed. I wouldn't mind 15-30-45, my problem with the old system was how damn long it took to get 20 points on some maps.
You're kidding yourself if you think squad leaders regularly kick players who aren't sticking with them. Even moreso if you don't think this will result in players who could care less about their squad, becoming squad leaders. I have no idea how you seem to believe that FORCING them into a squad is better than making them join to get a skill, which is already worse than the way it is now.
With Squads, you just gotta make it easier. A button on one of the existing popups saying "join available squad" would make everything easier. Sure those popups are difficult to deal with, but the main problem with squads is you need to open another popup to deal with them. People just don't want to. The people that do, fine, they'll manage their squads great. The people that don't, well hell, add a button to the spawn selection map or the class loadout, or even the score menu. You could add an extra column listing what squads people are in in that, too, so others could find someone they're near, or think is good, and just join that squad. Bit fiddly, but worth considering imo... Thank you for the hard work guys, makes me consider testing at least
put that somewhere into the scoreboard and we're fine. N00b checks the scoreboard for K/D , sees that 12 others are in a squad, asks how to join one, we tell him, he feels like bfbc2-pro in super-squad, win.
Ikalx has it right to be honest. Prompting people to join squads is a good idea, especially if you concisely laid out the advantages to sticking together. But you can't force squadwork, so forcing people into a squad to get a skill won't work.
I think the more important question is, could it somehow break vipers custom player models for donators?
does the model information with each skin need to be used in each itteration of the skin? IE, if you have 1 tank with 4 different camo skins, that one tank will be loaded into memory 4 times completely with each variance? If I'm understanding this correct, then yes, it would cut down the loading time probably something close to significantly.
I have no idea. I would imagine though that anything that can be readily spawned into game would need to be buffered in order to prevent lag when it was spawned. Not being buffered so that it had to be loaded and then spawned would be stupid too. Just because it's not being used, doesn't mean it's not there.
