BuzzerBeater Forums

6 months later... and I still feel exactly the same way about this issue as I did back then. Bumping because I believe this suggestion is still relevant. Has there been any new lines added to the game commentary at all since February?

in germany we started addin new/ funny lines in season 6?! and our GMs still adding new lines every season....i really dont know why some American GMs dont do that....its sooooooo easy to do :P

in germany we started addin new/ funny lines in season 6?! and our GMs still adding new lines every season....i really dont know why some American GMs dont do that....its sooooooo easy to do

Your player reaches up to grab the defensive rebound, but the RNG hates you tonight since despite double digits in rebounding and handling, he'll fumble it out of bounds for the fifth time this half.

Sol Scarborough jacks up a 3 from downtown!

shot missed

He's so cold, he's think he's Ray Allen. (or Steph Curry)


xD

Can your German GMs throw a thread up in the GM forum explaining to USA GMs how and what to do to improve our commentary...

at this point our commentary is so old and stale I might just watch games in German.

hehe..its by far the easiest thing that we could change..every la (gm) could change it at any time by logging in..why the las from one of the biggest communities in bb didnt do it? i have no clue...

cheers

Because all your german GMs are doing is changing translations of the ENGLISH from the ORIGINAL game, IE USAs commentary. You are not adding anything new, just messing with wording...

IF USA changed its wording, then every nation in the world suddenly gets a message that they have to retranslate, and it woudl not be an LA to do it...not sure if even GMs have access...I think it would have to be a BB to change the original ENglish tag.

Or just create a new localization for English-USA with all the text tagged with the current version, and get rid of any hardcoded default texts. Which is of course no small effort, and whether it's worth said effort is another story, but it's far better than just fixing the hardcoded default English texts other than addressing a typo.

If people are sick of the wording 'jumpshot' and they change it to 'jumper'.....then eventually people will just get sick of the word jumper.

The idea is not to simply reword, the idea is to leave the wordings that are there, there, but to add OTHER wordings AS WELL to add flavor and variety. The idea is that we want more variety/play types etc...

We aren't gonna get a new GE with new types of events, so they would need to make different wordings for the same types of events so that they seem different. I think there is already several kinds of events that can just be worded differently in the viewer...

So what we ARE asking for (I think atleast) is a game viewer update, which could only be done by the BBs, where they actually add new texts. If this were done, all the LAs would get new tags in their queue to translate. I was an LA for several seasons and personally finished the Japanese translation (although I did not do the bulk of the work, I did a few thousand tags at the end so that finally the game could be released in japanese)...

Anyway The point is I know what I am talking about and Will obviously does not.

I guess the question I had based on how I interpreted what you read was whether the base American English version also had the text pulled from tagged resources like other localized languages or whether it was hardcoded. We have done some localization on the software product I work on and initially there were a lot of hardcoded strings in the program that we'd just say "If they're Spanish, do this instead." That quickly proved to be dumb and now we have a localization setup with keys for English-US, English-UK and Spanish and it's possible that if we expand to other markets that we could translate quite quickly. So pretty much all of my post was more just curiosity on that front.

Having multiple texts for the same event key would probably also be doable, and I'd agree that would be a nice implementation. If I take a hypothetical key like MIDRANGE_JS_BAD_MISS, for example, just adding five or ten versions like MIDRANGE_JS_BAD_MISS_1, etc. would solve the problem pretty cleanly - and when the calculation occurs that creates the key for viewer/pbp, it can select one of those 10 at random or even just by using a specific digit from the previous generated random number. But, yes, that would definitely require BB intervention and the usual caveat about development priorities and whatnot clearly are in effect.