Good afternoon all,
We just discovered that one of our players' Brettonian team appears to have gotten corrupted. This probably happened when the update to the Brets came out, but we're just now discovering it, as they've come back to play this season. Under the Race column, they read "TRANSLATION ERR"
http://motorcitybloodbowl.org/index.php ... obj_id=184
I'm wondering if there's any way to retrieve/restore the team in the back end data, or if the best option would just be to create from scratch and then manually add all the SPPs/Skills/etc.
Thanks in advance for any guidance!
Tom
OBBLM: Brettonian Translation error--team roster incorrect
Moderator: TFF Mods
-
- Rookie
- Posts: 49
- Joined: Tue Apr 16, 2013 4:59 pm
- Location: Detroit
- Contact:
OBBLM: Brettonian Translation error--team roster incorrect
You do not have the required permissions to view the files attached to this post.
Reason: ''
- Vanguard
- Super Star
- Posts: 922
- Joined: Sun Jun 08, 2008 8:27 am
- Location: Glasgow
- Contact:
Re: OBBLM: Brettonian Translation error
This looks like an issue with the translations.xml file which handles the display of various pieces of text in different languages.
It shouldn't impact the usage of the team in any way, other than not displaying the Race correctly.
What is your language set to? You can see this under your profile, in the user menu.
It shouldn't impact the usage of the team in any way, other than not displaying the Race correctly.
What is your language set to? You can see this under your profile, in the user menu.
Reason: ''
-
- Rookie
- Posts: 49
- Joined: Tue Apr 16, 2013 4:59 pm
- Location: Detroit
- Contact:
Re: OBBLM: Brettonian Translation error
I'm set to en-GB.
I'd really like to be able to have the stats and prices appear correctly, so this DOES impact the usage of the team. To me, this isn't a usable roster. The player costs aren't there, the TV is wrong, and all the stats for several pieces are zero, while other pieces of the same type do not have that issue. One blitzer's stats do not appear, another's do, etc.
I appreciate the insight about the language, but I hopefully en-GB should be able to show the correct player prices etc. Hopefully there's a way to do that?
I'd really like to be able to have the stats and prices appear correctly, so this DOES impact the usage of the team. To me, this isn't a usable roster. The player costs aren't there, the TV is wrong, and all the stats for several pieces are zero, while other pieces of the same type do not have that issue. One blitzer's stats do not appear, another's do, etc.
I appreciate the insight about the language, but I hopefully en-GB should be able to show the correct player prices etc. Hopefully there's a way to do that?
Reason: ''
- Vanguard
- Super Star
- Posts: 922
- Joined: Sun Jun 08, 2008 8:27 am
- Location: Glasgow
- Contact:
Re: OBBLM: Brettonian Translation error--team roster incorre
Ah, I'd missed the player values as they weren't in the screenshot, thought it was just the Race Name that was causing you an issue. (And somehow overlooked the missing stats. )
It's an odd bug as it's not affecting all positions, just some players.
Can you try the following from the Admin page:
If that does not rectify the issue, can you try creating a new Brettonian team and see how that is calculated?
It's an odd bug as it's not affecting all positions, just some players.
Can you try the following from the Admin page:
- Synchronise database with game data files
- Re-install database back-end procedures and functions
- SyncAll()
If that does not rectify the issue, can you try creating a new Brettonian team and see how that is calculated?
Reason: ''
-
- Rookie
- Posts: 49
- Joined: Tue Apr 16, 2013 4:59 pm
- Location: Detroit
- Contact:
Re: OBBLM: Brettonian Translation error--team roster incorre
That did it, thanks so much!
Reason: ''
- Vanguard
- Super Star
- Posts: 922
- Joined: Sun Jun 08, 2008 8:27 am
- Location: Glasgow
- Contact:
Re: OBBLM: Brettonian Translation error--team roster incorre
Glad it's fixed, still puzzled at how it happened though. Let me know if it crops up again.
Reason: ''