Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The rule I have heard is criticize the game, not the person; but lately I feel in the absence of substantive news of PC2 or PC2 Pacific, is these mindless, ongoing disgorgement's, which are in lieu of any real sort of beneficial, discussions of the game, we all really like.
I have opinions, but they are not valid if they criticize people. Having said that, all that keeps this sad thread of attention to this wonderful game is two very specific posters. If you can guess them then I make my point.
Development is hard. Putting forth information is a perilous game, as any new insights make the developers feel beholden. But in the absence of real information comes threads that are left to the vultures and the despondent.
Please either moderate or dissipate, this interim modality is damaging to the game we actually all like and want to succeed.
De·stroy
verb
put an end to the existence of (something) by damaging or attacking it.
"the room had been destroyed by fire"
or for PC...
"the unit has been destroyed by surrendering."
As to criticism? The developers ARE as much the game as the software itself. No one is criticizing the people however. I am critiguing game mechanics, specifically in the Czech scenario and the logic used to validate what both of us believe is a poor or deficient terminology.
Surrendering is NOT a synonym. It is being used as a euphemism for 'destroyed'. You can intend to use it that way, but should be mindful that it is misleading. It would have been a lot less problematic if, somewhere, an editor had bothered to write: For this scenario a surrendered unit will be considered as 'destroyed'.
Games don't improve without feedback, which is what this is intended to be. If you want to moderate an echo chamber and have everyone hold hands, sing Kumbaya, and only talk about happy things that everyone agrees with, then relabel this blog and put a 'content warning' up. Expressing dissatisfaction seems to be threatening and offensive and probably needs to be controlled.
It's not my favourite scenario and as an AO it's up there with 1944 Historical in terms of quality but if you played it once it should be obvious surrendering equated to destroyed as you get a message re lost points as soon as this happens.
Given the terms of the scenario think its fair enough that you lose the points if a unit surrenders, whether the scenario should have been there in the first place is a better question.
Good point. My question is why can't the developers share even small bits of information on what is coming for the game, more consistently? Rather then leave the message boards silent where all that can take place is fighting over semantics.
Having stumbled across this thread, it is now apparent that the developers ARE making that equation . I (and apparently Ken) don't think that was a wise equation without any explanation. I just agree with Ken that it was a poor linguistic choice akin to calling beach sand 'dirt' or 'topsoil' because it's all 'earth'. The unit is 'removed'. " You will forfeit the bonus if a unit is removed". If a developer wants to term all removals as destroyed they certainly can. But a 'destroyed' unit has a different connotation than a captured or surrendered one, at least IRL, and a developer/editor ought to be cognizant of that and could/should take it into account.
BTW, it really isn't just semantics. The older players are, the more impact creatively using or combining terminology becomes as it imparts an unreal, discordant quality that isn't intuitive. Words and symbols have certain expectations. I am only suggesting that manuals, literature. or pop-ups disclose those creative (artistic license) uses.
The dev's wrote the scenario briefing. In their mind it is clear, and does not require a redo. No matter how many things you fix with clearer briefing etc, there will always be someone that interprets it differently. ( remember we all come from different backgrounds, education level, life experiences, languages, cultures, etc..) So in the end not fixing something they feel is not broken is their choice. They do not owe us anything. If it is a bug that effects play yes it should be fixed.
You can argue the meaning of words forever and it will not change anything. Those of us that have played PzC 2 since it launched have seen these arguments before. ( in reality you should search the forums for what you have an issue on, read those posts and move on) Many people simply post the question some of which have been answered many times. Then when someone answers it with what they KNOW to be accurate those people argue they are wrong because this word means this or that. The game is supported by a very small staff. If they were to correct everything you want corrected it would slow down future content. Most of us would rather see that not happen.
You know, I think many of you aren't really getting what I'm trying to get across, but you did succinctly point out the source of the problem quite nicely.
It's isn't about being a game or a simulation (we can dicker those meanings as you suggested different things to different people) and it isn't relevant that it's a small staff. Those are straw man issues.
"In their mind it is clear" IS the point. 'Their mind', NOT my mind. I'm simply trying to let you know what I have a problem with, and why. Everyone is egocentric and sees through the lens of their own eye, not someone else's (I think you said that too). I think the way it was done was an unintended error. It isn't about anything other than that.
I don't expect a dev to like what I said . I don't expect a dev to do anything about it either. I do expect that someone on the programming/design side ought to be able to go "Hmmm, didn't think of that". THAT tells me someone assimilated the idea and gets it. I don't care what they do with it after that.
How can something you feel is correct be an error? I understand to YOU it is an error. But to the vast majority of us and to the dev it is not an error. Like I said before we can argue the meaning of words forever and get no where. Thank you for discussing this with me. We might have to agree to disagree and move on,
I am giving out a warning for this post because it's agest and disrespectful to certain generations of players. It also implies that anyone that disagrees with the OP's postion is "doubling down", I.E. incorrect because they don't have the insight of the older generation. It's written extremely well but it's also written to be insulting and to belittle any differing response.
I don't care how elegantly and apologetically "Anyone who disagrees with me is an idiot" is written, it's not allowed here and it's flamebait.
This is a game, and in a game words mean specific "game" things. This is why such words are often defined by the manual. However, in this case, the word is not being used in this way (like words such as "meta" or "tempo" might be).
The Oxford dictionary defines "destroy" as follows:
end the existence of (something) by damaging or attacking it.
A surrendered unit literally ceases to exist, so by this dictionary definition, it is destroyed.
There is no confusion here to be had, the word is being used correctly.
I am going to lock this topic as well, because it is only leading to people flaming each other.
Edit: I will make a feedback note, to make it very clear that surrendered units are destroyed.