8 Mar 2018, 01:11
@prastle as long as hitting space while chatting doesn't confirm the casualty
Casualty Auto Selection - Engine Preference To Disable
-
@prastle as long as hitting space while chatting doesn't confirm the casualty
-
@redrum When I proposed it years ago I had mostly in mind maps like Feudal Japan Warlords, in which it is extremely annoying having to undo the autoselect each time, before selecting.
The concept of rather improving the autoselect to cover all is a good point, theorically, but, as you see, at the distance of many years AA are still not covered (not saying they should have had, since there are many more important things to do); so, I think, especially in a volunteer based project, an opt out option, to fall back, has a good value.
Anyways, I'm not playing much of those games lately, so I'm not strong, and I agree that for most people this opt-out would have no value.
But, again, it may have a value because of that problem of spacebar selecting casualties while you are using it for chatting, but, again, that would be better if solved specifically.
But, yeah, if everything would be fully covered and nothing would have any problems (like the spacebar chatting / confirming mash up), then you would not want to have this option. Question is, will it always (or should I say ever) be? -
@redrum It works for me too, but I think it would be better if generally chatting would not confirm generally, since there are other things that spacebar still confirms, like politic and action proposals, but this is off topic. Mostly, I don't think that is really a solution, because it is kind of easy not spotting it, so you will still have people misclicking at random.
-
@redrum @prastle Problem is if you have it set to use spacebar. While chatting and not looking at game events. The cursor automatically tabs to somewhere on the game interface. This happens on nations turn start for sure, on game start and various notifications that need clicks, and there's a few other times that I don't recall atm. Anyways so while typing for chat, your actually accidently somewhere else on the game interface, clicking away. This includes on the menu as well as what ever various user actions are currently popping up.
There should be an additional mechanism to keep the cursor in the chat box during the various cases. So then it can truly be avoided.
-
@general_zod good point but i am literally reffering to while typing as now my spacebar confirms something... even when on a different webpage
-
@redrum Yah, regarding the negative support, the autoselection is very bad for games like Blue vs. Gray, where it autoselects the inf. crack before the veterans. I would definitely opt it out if playing that game, but obviously if the selection would see that the crack are worth more than the vets, then I would not.
-
@redrum to reiterate something Cernel and I were ignored on years ago but is kinda semi fixed would be to explain in this fashion. DEFAULT settings should be typing cant cause a click!
-
Uh. There are several different conversation going on here now. Anything that isn't directly related to either disabling default casualty selection or configuration of default casualty selection should probably have a separate thread.
-
@redrum Due to some overlapping behaviors and then linking to others. But yes the spacebar chat issue needs its own feature request or bug report.
-
@general_zod naw I'm done with it now ignored then ignored now moving on
-
@redrum Would that optional "slower / perfect" casualty selection you removed have handled the HoH case with negative support attachments @CrazyG is pointing out? Just mostly curious, as I never got to know what that option had to offer.
-
@cernel Yes, I believe so. It handled enemy support attachments. It still never handled AA though.
-
@redrum Well, if I knew that handled negative supports, I would have suggested keeping it, but it would have needed a tooltip or something to tell it (and whatever else it offered in exchange for being terribly slow), otherwise very unlikely to figure it out. Still, not much value added, as those thing might get used only by very few power users. Anyways, now that HoH is in the repository, you might consider adding it back, so that @CrazyG might be able to use the BC.
-
I made a topic for the chat spacebar issue.
https://forums.triplea-game.org/topic/644/chat-dialouge-lock-mechanism
-
@cernel It was too slow to really be usable. It was more of an experiment to see how much I could get the calc to cover. I would need a more optimized approach to cover some of the remaining items that it doesn't today in a fashion that finishes in a reasonable amount of time.
-
@redrum I actually used it a bit, even to not managing to understand what it was doing different from the default one, and, while it was like 10 times slower, I would say it was fairly playable, as long as you were not playing a game with massive stacks, and depending on the calculating power of your terminal.
In a case like I mentioned, I think it would definitely be nice to have (sounds like, I've not met the case myself), but up to you; there are very few maps like HoH, for which it would matter. -
The Battlecalc has a very good option to manually set order of losses. What if we got an option to make a default order for a specific map?
This gives some options to fix enemy support issues (it works for HoH at least).
Also its just appearances but I would love it infrastructure units no longer displayed 1 HP in the battle calc.
-
@cernel tww broken as you said
stacks NWO not much better -
@crazyg Yeah, the HP battle calc issue is really more of a bug as very few maps use infrastructure that can participate in battles during attacks. Probably better to submit a github issue for it. Most of the time manual OOL will be worse as often unit sets to need weave units to consider support attachments plus things like technology and territoryEffects.
-
@crazyg yup it would require each map maker to set the default but a great idea!