Sometimes some things stop to work midgame (a ui-reload fixes this). I'm led to believe that the event API stops working, but I have nothing to really check it. Grid would still show healthbars alright and GridStatusHots works normally, but most other things don't... in particular, RaidCooldowns and TankCooldowns aren't shown anymore, and the healing prediction doesn't work anymore, too (not working = not showing anything even though I'm sure there's something that should be shown). Also, any combat-log addon I use (skada + death note) stops recording, nothing shows up anymore.
I'm not familiar with the plugins you listed, but it sounds like you're running into the same bug that's existed since Blizzard first implemented the combat log back in TBC. Sometimes the combat log just stops working, and this will affect any addon that depends on the combat log. Use this addon to automatically clear and restart the combat log when it breaks.
I have no idea what you're asking. Please try again using comprehensible English. If English is not your native language, post your question in your native language, and I'm sure I can find a machine-translation service that will give a more comprehensible result than what you posted.
He's saying he only has a 40y range check status now, should be pretty obvious since you're the one who implemented that. :P
So Paladins are from now on going to be forced to use GridStatusMultiRange? Meh. Hands have 30y range :(
So Paladins are from now on going to be forced to use GridStatusMultiRange? Meh. Hands have 30y range :(
If you want to have multiple range checks, yes, you'll need to use the plugin. The whole point of Grid is that it doesn't need to be a huge addon that includes every feature every player of every spec of every class might need, because it's easy to write plugins to add new features.
I posted in this thread almost two months ago proposing to remove multiple range-checking from the core, and nobody offered any reasons why I shouldn't do that. The main reason that multiple range-checking was added to the core in the first place was that healing and dispelling had different ranges for all classes. Now that those ranges have been standardized, the vast majority of class/spec combinations only have one useful range to check.
Multiple-range checking in the core led to a large number of tickets from people who thought the addon was broken, when really they were just confused about how an unintuitive and overcomplicated system was supposed to work. It was frustrating for me to spend time going back and forth with these users trying to find out what the problem was only to realize there wasn't really a problem, and it was frustrating for those users to deal with a system that seemed broken and then be told that there wasn't a problem and they were just doing it wrong.
There were also several bugs on Blizzard's end with spell-based range checking. For example, it frequently failed when zoning in/out of cross-realm dungeons.
Moving multiple range-checking to a plugin will reduce the core footprint for the majority of users, and remove a common source of confusion for the majority of users. The few people who actually use multiple range-checking can install the plugin, and because they understand what they're doing, they won't be confused when they enable a 40-yard range check on their healer and then don't have a 40-yard range check available on their rogue.
Feel free to subscribe to this thread to keep up-to-date with development. I generally post here and ask for feedback before making significant changes.
Am i the only one who finds the new "tabbed" options window is not an improvement at all?
It just doesn't work with the release version (tabs are each displayed on one row, occupying half of the screen, and are wider than the window), hence forcing me into using the alpha version.
I really prefered the previous setup interface: the one that was integrated, like 90% of other wow add-ons, to the standard UI. I found it much more readable and just don't understand why you had to change it. I just didn't see any new feature that explained that change. I may have missed something though.
Sorry for this negative feedback, i just love grid and admire you for the tremedous work you've done on it. It would be a shame it becomes unusable just because it's no longer possible to set it up!
It just doesn't work with the release version (tabs are each displayed on one row, occupying half of the screen, and are wider than the window) ...
That's a bug in the Ace3 libraries that generate the options frame, and Grid has no control over it. It "works" with some versions and not others because each Grid release includes whichever versions of the Ace3 libs were current when that version was packaged. Since the Ace3 devs (like most library devs) hardly ever tag stable versions, I have to pull in directly from the trunk or else people end up using versions that are months out of date and complain about that. If you have other addons that also embed AceGUI-3.0, their copies (if newer) should overwrite the ones in Grid, and everything should work. Or, you can download a standalone copy of Ace3. Either way, it's not a Grid bug.
I really prefered the previous setup interface: the one that was integrated, like 90% of other wow add-ons, to the standard UI. I found it much more readable and just don't understand why you had to change it..
Grid's options have never been integrated in the standard Interface Options window, so I'm not really sure what you're talking about.
The original Grid UI was a series of nested, scrolling dropdown menus. When I first converted it to use AceConfig-3.0 (as part of the general transition off the outdated and deprecated Ace2 framework) it was using the default AceConfig layout, which uses a tree with tiny, tiny buttons that had to be clicked to expand categories and get to any actual options. I found that less usable than the dropdowns. The tabs are easier to click on in general, and make it easier to get from the Frame category to the Layout category and back, since you can just click the tabs instead of scrolling through a long list of subcategories and trying to click on the tiny buttons.
The only problem is that some plugin authors are too lazy to spend 30 seconds once every few months making a few minor changes. The last time there was a change, I spent hours going through dozens of other people's plugins making changes for them. This time, only a few plugins are affected, and it's really not my problem. If the author doesn't notice that their plugin needs to be updated, they're probably not using it, which means that they're probably not going maintaining or supporting it either.
Thanks! I have updated the lib and it works like a charm.
However I think you should link each Grid release with a specific version of libAce. You are the first one to ask people not to use alpha release of grid (and you are sooooo right). That would prevent us from thinking Grid is the responsible of the bad behaviour.
After all, we all behave like end-users: when something doesn't work, our first thought is to blame the manufacturer, not his subcontractors.
Grid's options have never been integrated in the standard Interface Options window, so I'm not really sure what you're talking about.
I can assure you there was a release of Grid on Curse that was integrated in the standard interface. It stroke me because i found that new feature was VERY cool.
It was around cata release (4.0.1 or 4.0.3 i don't remember exactly). Then a new release was posted on curse with the new tabbed window.
That's why I was quite bothered : it seemed like a step backward to me.
I've done some process-of-elimination troubleshooting and determined that my Grid frame tab is being "garfed up" (that's my technical description of the issue documented on the Grid main page here on WowAce) by the plugins GridIndicatorSideText and GridIndicatorCornerText.
I gather these two plugins haven't been updated to comply with Grid's switchover to AceConfig tabs.
Unfortunately, based on comments s/he's posted on Curse, it appears that the author of those plugins has abandoned them for another raid frame solution. More unfortunately these are two plugins that I'm hard pressed to let go of. (On my resto druid main I'm tracking four HOTs per unit, and I find the extra information granularity of the text indicator (versus a shifting color pip) to be awfully handy when my making next cast decision.)
While this is obviously a plugin rather than a Grid core problem, I'm posting here to alert the greater Grid community that these two plugins having entered unmaintained (and already mildly broken) status. I'm hoping some other concerned user(s) of those plugins will happen to have a developer bent and will fix and/or take them over. (The original author has left contact information on the Curse pages for GridIndicatorCornerText and GridIndicatorSideText indicating s/he could be reached if someone wanted to take responsibility for them.)
after login (without doing anything): ~1555 KB
with opened options (no click on a tab): ~1655 KB
with opened options and click on every tab (expect 'Status'): ~1922 KB
with opened options and click on every tab (including 'Status'): ~5354 KB (a simple click on the tab, not focused nor typed-in anything in the Spell-EditBox)
5354-1922 = ~3432
3432 KB of memory for a useless feature!
3432 KB of memory for a feature that was not requested by the user!
What a waste of memory and CPU resources. All this hidden spell check is done with the default global GameTooltip (Sure, this is the fault of AceGUI-3.0-Spell-EditBox)!
It's ok to use memory (even if it's huge) to store things! But it's not ok how this 'spell check' is currently implemented.
It's not okay that a simple click on the Status tab starts such hidden mem/CPU waste.
It's the second time that you, Phanx, implement some strange mem/CPU/(bandwidth) hungry lib (LibHealComm-4.0). Why?
Why do you destroy GridStatusRange and simultaneously release a 3rd-party-module that does what GridStatusRange did? Why?
The internal GridStatusRange module is much much more important than some stupid resource-inefficient spell checker.
Do you really think the use of 3432 KB memory for nothing is okay?
The solution:
Simply start the AceGUI-3.0-Spell-EditBox 'spell check' _after_ someone typed-in at least one character in the Spell-EditBox.
However I think you should link each Grid release with a specific version of libAce.
There's no way to do that unless I stop using revision control to generate packages from the SVN repository and start uploading manual zips for every release, which will probably never happen. Feel free to suggest to the Ace3 developers that they tag stable versions more often.
Why do you destroy GridStatusRange and simultaneously release a 3rd-party-module that does what GridStatusRange did? Why?
If you'd bothered to read my multiple explanations in this thread, you'd know why. I posted about my intentions months ago. If you had something to say, you should have said it then. Please don't post here if you're just going to rant, insult, and not read anything.
Simply start the AceGUI-3.0-Spell-EditBox 'spell check' _after_ someone typed-in at least one character in the Spell-EditBox.
Feel free to request it of the library author.
Also note that no release has been tagged with the library you're whining about. I added it as an experiment, because people often type spell names incorrectly or don't realize it needs to be capitalized, and I thought the library would be helpful. I have not yet decided whether to keep it. As I've said over and over, ALPHA VERSIONS ARE DEVELOPMENT SNAPSHOTS and are not finished, final products ready for widespread general use. There is absolutely no reason for you or anyone else to have an aneurysm because I changed something in an alpha version. If a change will be permanent, I'll announce it in this thread and ask for comments. On the other hand, you're not my mother. I don't need to ask you for permission to test something out.
If you have an opinion about something you see in an alpha version, feel free to post a constructive comment using wording that is appropriate for a public forum. Hysterical ranting, name-calling, and other insults are not appropriate, and will get your post deleted, not read or considered.
scubamonkey, those are easily fixe. Open GridIndicatorCornerText.lua and paste "inline = true," after line 30. I'm sure you can see the pattern and apply the same fix to the other plugin.
I do hope someone picks up those plugins, too, they're very usefull.
I added it as an experiment, because people often type spell names incorrectly or don't realize it needs to be capitalized, and I thought the library would be helpful. I have not yet decided whether to keep it.
I think that is an extremely useful feature and I really hope you decide to keep it. And who cares about performance in a configuration dialog? It's not a highly repetitive or time crucial activity. I didn't test the feature but as long as it is happening only once to build up the database, its ok.
scubamonkey, those are easily fixe. Open GridIndicatorCornerText.lua and paste "inline = true," after line 30. I'm sure you can see the pattern and apply the same fix to the other plugin.
If you'd bothered to read my multiple explanations in this thread, you'd know why. I posted about my intentions months ago. If you had something to say, you should have said it then. Please don't post here if you're just going to rant, insult, and not read anything.
Phanx, you simply do not care what people post here nor what people submit to the repository. Your posts and repository commit messages are sometimes full of ignorance and arrogance.
Why should anybody believe what you write here? You (I think so) deleted nearly every post from me that corrected(!) wrong postings you made about some of my Grid addons. You (I think so) deleted nearly every post here that critized changes you made to Grid.
I do not believe in one single word you post here. Do you remember your wowinterface.com announcement for your 3rd-party-addon-descruction-changes some time ago? You did not used this thread! You did not posted such massive changes here. You (I think so) deleted simply posts!
I think that is an extremely useful feature and I really hope you decide to keep it. And who cares about performance in a configuration dialog? It's not a highly repetitive or time crucial activity. I didn't test the feature but as long as it is happening only once to build up the database, its ok.
Read my post. I am not against the use of AceGUI-3.0-Spell-EditBox, but AceGUI-3.0-Spell-EditBox is a typical example how someone should not code a library: resource-inefficient. The idea is good, but horrible coded.
...If you have an opinion about something you see in an alpha version, feel free to post a constructive comment using wording that is appropriate for a public forum...
!
REMEMBER: The Grid repository is OPEN, Grid is 'All rights reserved.'. The Grid authors are: Pastamancer and Maja!
You (I think so) deleted nearly every post from me that corrected(!) wrong postings you made about some of my Grid addons. You (I think so) deleted nearly every post here that critized changes you made to Grid.
Yes, and those deletions had nothing do do with WHAT you were saying, and everything to do with HOW you were saying it. Posting in all caps with 12 exclamation points after every sentence, and using insulting language like "you are stupid" will get your post deleted, period.
And HERE is the place to discuss such changes!!! HERE!
Great, I'm glad we agree. Please check further back in the thread for where I clearly announced my intention to remove multiple range-checking from the Grid core, and asked what other people thought. If you can't be bothered to check the thread every few weeks (or just subscribe to it) and comment when I've asked for comments, then it's really not my problem if you don't like what happens.
Grid is 'All rights reserved.'. The Grid authors are: Pastamancer and Maja!
Feel free to contact Pastamancer for verification that he has given me permission to develop and maintain Grid. Also, if you weren't being hysterical and intellectually dishonest, you'd see that I am also listed as an author on the project page. I can't magically add my name to projects. Pastamancer, as the project owner, had to add my name there.
Please do not continue posting in this thread unless it is directly related to Grid. If you want to complain about my actions as a moderator, blame me for your apparent inability to read clearly written announcements, complain about the quality of other people's code, or do anything else other than offer useful and constructive feedback about Grid, please do so in a PM, or don't do so at all. I will be deleting any further off-topic posts.
before i updated my grid today, units out of range had their healthbar faded, now all units seem to be in range visually. How can i make the health bar in the center fade to grey again for iunits further away than 40 yards?
If you're using the alpha version, the range checks for specific distances have been removed, and there is now a single "Out of Range" status that works like range checking in 99% of other addons. Make sure that status is enabled on the indicator(s) you had the old "More than X yards away" status enabled on.
French, Russian, Simplified Chinese, and Traditional Chinese are currently missing some updates. Simplified Chinese doesn't really matter right now since current versions of Grid are WoW 4.0-only, but there's no harm in entering them.
Please report anything you notice that isn't translated in-game.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I'm not familiar with the plugins you listed, but it sounds like you're running into the same bug that's existed since Blizzard first implemented the combat log back in TBC. Sometimes the combat log just stops working, and this will affect any addon that depends on the combat log. Use this addon to automatically clear and restart the combat log when it breaks.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHe's saying he only has a 40y range check status now, should be pretty obvious since you're the one who implemented that. :P
So Paladins are from now on going to be forced to use GridStatusMultiRange? Meh.
Hands have 30y range :(
I don't speak AOLese, and I'm not going to bother helping anyone who can't take a few seconds to type intelligibly.
If you want to have multiple range checks, yes, you'll need to use the plugin. The whole point of Grid is that it doesn't need to be a huge addon that includes every feature every player of every spec of every class might need, because it's easy to write plugins to add new features.
I posted in this thread almost two months ago proposing to remove multiple range-checking from the core, and nobody offered any reasons why I shouldn't do that. The main reason that multiple range-checking was added to the core in the first place was that healing and dispelling had different ranges for all classes. Now that those ranges have been standardized, the vast majority of class/spec combinations only have one useful range to check.
Multiple-range checking in the core led to a large number of tickets from people who thought the addon was broken, when really they were just confused about how an unintuitive and overcomplicated system was supposed to work. It was frustrating for me to spend time going back and forth with these users trying to find out what the problem was only to realize there wasn't really a problem, and it was frustrating for those users to deal with a system that seemed broken and then be told that there wasn't a problem and they were just doing it wrong.
There were also several bugs on Blizzard's end with spell-based range checking. For example, it frequently failed when zoning in/out of cross-realm dungeons.
Moving multiple range-checking to a plugin will reduce the core footprint for the majority of users, and remove a common source of confusion for the majority of users. The few people who actually use multiple range-checking can install the plugin, and because they understand what they're doing, they won't be confused when they enable a 40-yard range check on their healer and then don't have a 40-yard range check available on their rogue.
Feel free to subscribe to this thread to keep up-to-date with development. I generally post here and ask for feedback before making significant changes.
It just doesn't work with the release version (tabs are each displayed on one row, occupying half of the screen, and are wider than the window), hence forcing me into using the alpha version.
I really prefered the previous setup interface: the one that was integrated, like 90% of other wow add-ons, to the standard UI. I found it much more readable and just don't understand why you had to change it. I just didn't see any new feature that explained that change. I may have missed something though.
Sorry for this negative feedback, i just love grid and admire you for the tremedous work you've done on it. It would be a shame it becomes unusable just because it's no longer possible to set it up!
That's a bug in the Ace3 libraries that generate the options frame, and Grid has no control over it. It "works" with some versions and not others because each Grid release includes whichever versions of the Ace3 libs were current when that version was packaged. Since the Ace3 devs (like most library devs) hardly ever tag stable versions, I have to pull in directly from the trunk or else people end up using versions that are months out of date and complain about that. If you have other addons that also embed AceGUI-3.0, their copies (if newer) should overwrite the ones in Grid, and everything should work. Or, you can download a standalone copy of Ace3. Either way, it's not a Grid bug.
Grid's options have never been integrated in the standard Interface Options window, so I'm not really sure what you're talking about.
The original Grid UI was a series of nested, scrolling dropdown menus. When I first converted it to use AceConfig-3.0 (as part of the general transition off the outdated and deprecated Ace2 framework) it was using the default AceConfig layout, which uses a tree with tiny, tiny buttons that had to be clicked to expand categories and get to any actual options. I found that less usable than the dropdowns. The tabs are easier to click on in general, and make it easier to get from the Frame category to the Layout category and back, since you can just click the tabs instead of scrolling through a long list of subcategories and trying to click on the tiny buttons.
The only problem is that some plugin authors are too lazy to spend 30 seconds once every few months making a few minor changes. The last time there was a change, I spent hours going through dozens of other people's plugins making changes for them. This time, only a few plugins are affected, and it's really not my problem. If the author doesn't notice that their plugin needs to be updated, they're probably not using it, which means that they're probably not going maintaining or supporting it either.
However I think you should link each Grid release with a specific version of libAce. You are the first one to ask people not to use alpha release of grid (and you are sooooo right). That would prevent us from thinking Grid is the responsible of the bad behaviour.
After all, we all behave like end-users: when something doesn't work, our first thought is to blame the manufacturer, not his subcontractors.
I can assure you there was a release of Grid on Curse that was integrated in the standard interface. It stroke me because i found that new feature was VERY cool.
It was around cata release (4.0.1 or 4.0.3 i don't remember exactly). Then a new release was posted on curse with the new tabbed window.
That's why I was quite bothered : it seemed like a step backward to me.
I gather these two plugins haven't been updated to comply with Grid's switchover to AceConfig tabs.
Unfortunately, based on comments s/he's posted on Curse, it appears that the author of those plugins has abandoned them for another raid frame solution. More unfortunately these are two plugins that I'm hard pressed to let go of. (On my resto druid main I'm tracking four HOTs per unit, and I find the extra information granularity of the text indicator (versus a shifting color pip) to be awfully handy when my making next cast decision.)
While this is obviously a plugin rather than a Grid core problem, I'm posting here to alert the greater Grid community that these two plugins having entered unmaintained (and already mildly broken) status. I'm hoping some other concerned user(s) of those plugins will happen to have a developer bent and will fix and/or take them over. (The original author has left contact information on the Curse pages for GridIndicatorCornerText and GridIndicatorSideText indicating s/he could be reached if someone wanted to take responsibility for them.)
Grid (without plugins and empty SavedVariables):
after login (without doing anything): ~1555 KB
with opened options (no click on a tab): ~1655 KB
with opened options and click on every tab (expect 'Status'): ~1922 KB
with opened options and click on every tab (including 'Status'): ~5354 KB
(a simple click on the tab, not focused nor typed-in anything in the Spell-EditBox)
5354-1922 = ~3432
3432 KB of memory for a useless feature!
3432 KB of memory for a feature that was not requested by the user!
What a waste of memory and CPU resources. All this hidden spell check is done with the default global GameTooltip (Sure, this is the fault of AceGUI-3.0-Spell-EditBox)!
It's ok to use memory (even if it's huge) to store things! But it's not ok how this 'spell check' is currently implemented.
It's not okay that a simple click on the Status tab starts such hidden mem/CPU waste.
It's the second time that you, Phanx, implement some strange mem/CPU/(bandwidth) hungry lib (LibHealComm-4.0). Why?
Why do you destroy GridStatusRange and simultaneously release a 3rd-party-module that does what GridStatusRange did? Why?
The internal GridStatusRange module is much much more important than some stupid resource-inefficient spell checker.
Do you really think the use of 3432 KB memory for nothing is okay?
The solution:
Simply start the AceGUI-3.0-Spell-EditBox 'spell check' _after_ someone typed-in at least one character in the Spell-EditBox.
This is for all admins/mods that continuously deleted my posts:
http://en.wikipedia.org/wiki/Criticism
There's no way to do that unless I stop using revision control to generate packages from the SVN repository and start uploading manual zips for every release, which will probably never happen. Feel free to suggest to the Ace3 developers that they tag stable versions more often.
HealComm was (a) not implemented by me, and (b) an extremely popular library that can hardly be described as "strange".
If you'd bothered to read my multiple explanations in this thread, you'd know why. I posted about my intentions months ago. If you had something to say, you should have said it then. Please don't post here if you're just going to rant, insult, and not read anything.
Feel free to request it of the library author.
Also note that no release has been tagged with the library you're whining about. I added it as an experiment, because people often type spell names incorrectly or don't realize it needs to be capitalized, and I thought the library would be helpful. I have not yet decided whether to keep it. As I've said over and over, ALPHA VERSIONS ARE DEVELOPMENT SNAPSHOTS and are not finished, final products ready for widespread general use. There is absolutely no reason for you or anyone else to have an aneurysm because I changed something in an alpha version. If a change will be permanent, I'll announce it in this thread and ask for comments. On the other hand, you're not my mother. I don't need to ask you for permission to test something out.
If you have an opinion about something you see in an alpha version, feel free to post a constructive comment using wording that is appropriate for a public forum. Hysterical ranting, name-calling, and other insults are not appropriate, and will get your post deleted, not read or considered.
I do hope someone picks up those plugins, too, they're very usefull.
I think that is an extremely useful feature and I really hope you decide to keep it. And who cares about performance in a configuration dialog? It's not a highly repetitive or time crucial activity. I didn't test the feature but as long as it is happening only once to build up the database, its ok.
That worked like a charm - thank you for the tip!
Phanx, you simply do not care what people post here nor what people submit to the repository. Your posts and repository commit messages are sometimes full of ignorance and arrogance.
Why should anybody believe what you write here? You (I think so) deleted nearly every post from me that corrected(!) wrong postings you made about some of my Grid addons. You (I think so) deleted nearly every post here that critized changes you made to Grid.
I do not believe in one single word you post here. Do you remember your wowinterface.com announcement for your 3rd-party-addon-descruction-changes some time ago? You did not used this thread! You did not posted such massive changes here. You (I think so) deleted simply posts!
And HERE is the place to discuss such changes!!! HERE!
Read my post. I am not against the use of AceGUI-3.0-Spell-EditBox, but AceGUI-3.0-Spell-EditBox is a typical example how someone should not code a library: resource-inefficient. The idea is good, but horrible coded.
If you implement a library: read the sourcecode!
Do not use mem/CPU/bandwidth inefficient coded libraries!
!
REMEMBER: The Grid repository is OPEN, Grid is 'All rights reserved.'. The Grid authors are: Pastamancer and Maja!
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorSaying one thing then another are we again kunda?
Yes, and those deletions had nothing do do with WHAT you were saying, and everything to do with HOW you were saying it. Posting in all caps with 12 exclamation points after every sentence, and using insulting language like "you are stupid" will get your post deleted, period.
Great, I'm glad we agree. Please check further back in the thread for where I clearly announced my intention to remove multiple range-checking from the Grid core, and asked what other people thought. If you can't be bothered to check the thread every few weeks (or just subscribe to it) and comment when I've asked for comments, then it's really not my problem if you don't like what happens.
Feel free to contact Pastamancer for verification that he has given me permission to develop and maintain Grid. Also, if you weren't being hysterical and intellectually dishonest, you'd see that I am also listed as an author on the project page. I can't magically add my name to projects. Pastamancer, as the project owner, had to add my name there.
Please do not continue posting in this thread unless it is directly related to Grid. If you want to complain about my actions as a moderator, blame me for your apparent inability to read clearly written announcements, complain about the quality of other people's code, or do anything else other than offer useful and constructive feedback about Grid, please do so in a PM, or don't do so at all. I will be deleting any further off-topic posts.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumPlease play nicely, everyone.
P.S. Don't forget about branches in svn.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhttp://wow.curseforge.com/addons/grid/localization/
French, Russian, Simplified Chinese, and Traditional Chinese are currently missing some updates. Simplified Chinese doesn't really matter right now since current versions of Grid are WoW 4.0-only, but there's no harm in entering them.
Please report anything you notice that isn't translated in-game.