Ciuine

Thanks for the tip Ramirez, I'll make the necessary changes tomorrowish; just finished another add-on. This one just for fun.

I do name all three cannons for the Russian localization... And only one turbine/motor/helm matter the second listed version is actually near the reactor where it demonstrates the health of these things easily not meant to be an actual device.

The Event you're looking for is EVENT_INGAME_UNDER_CURSOR_CHANGED.

Huh, odd.

Test out the file in the post below, I'm pretty sure everything is correct.

The blank name is there to fix the error that everyone has been talking about. If the add-on can't find who sent an Emote it prints a blank name.

As for the system messages, I don't see the problem. It is not like you're going to freak out that you sent yourself a message..

Can the two of you test this for me? Just need a standing on ship test, don't need to do anything or what have you. Anything that isn't detected properly (if it exists) will show up gray.

My ShipHUD only cares about cannons/artillery and the reactor/turbine/motor/helm. So the naming problems with the other things won't matter.

So my string checks will be lower case forms of двигатель (Motor), руль (Turbine), реактор (Reactor), Штурвал (Helm), лучемёт (Artillery), and пушка (Cannon). About the other cannons you mention do they not have named suffixes similar to these?

I'll just lowercase the strings before running the check.

Do not the better devices have similar names? IE Kanone for cannons. I do string compares based on the standard normal name. The devices are oddly slotted. The Motor/Turbine/Helm are all at the same position; so collecting data by position alone would prove un-resourceful.

I do not collect shield names just the shield data of the ships.

Just need some strings compiled for ship device names, so that I can localize ShipHUD.

If someone could run this in an add-on on their ship and give me the mods.txt; that'd be swell.

Rar.

I'm well aware of the issue, it has already been addressed in my version. I have been busy.

Instead of changing the reaction, you can change the name of the button as viewed by the LUA.

Then you can ask on the reaction what the name of the button is via params.sender. If params.sender == "NewName1" then do this..

There are examples of this code at work in WhisperWindow as there are only four reaction buttons total in the add-on.

If that exists. It would more than likely be a state defined global class variable though. "AlignLeft" and such ideas, I have no idea what it actually is.

Google Translate:

Если это существует. Было бы более чем вероятно, будет состояние, определяемое глобальной переменной класса, хотя. "AlignLeft", и такие идеи, я понятия не имею, что это на самом деле.

Click the little symbol on the bottom left of the main window, it'll open the configuration window. Then click the "Size" button and it will open an EditLine. Type an integer into the EditLine and that will be the size of all incoming text.

Google Translate:

Нажмите маленький символ в левом нижнем углу главного окна, это откроет окно настройки. Затем нажмите кнопку "Размер" и она будет открыта EditLine. Тип целого числа в EditLine и что будет размер всех входящих текста.

/wwtop is meant to put the display of the add-on over-top of the map or below it.

EditLine is the little square that pops up where you type stuff into when clicking certain buttons.

Thank you for the translations.

I noticed this while running tests on the Russian servers. I believe these are erroneously sent as CLIENT_MESSAGES when they should be sent as UNIT_MESSAGES. This could be an error or intentional due to the need for colored words without using colors.

Google Translate:

Я заметил это в то время ходовых испытаний на русских серверах. Я считаю, что сегодня ошибочно направлен как CLIENT_MESSAGES, когда они должны быть направлены как UNIT_MESSAGES. Это может быть ошибка или преднамеренное в связи с необходимостью для окрашенных слов без использования цвета.

This is actually an error in the zoning of Yazes, not in the mini-map. The names attached to the specific subzones of Yazes have changed repeatedly in localized versions of the game.

Each of the containers can be renamed and restructured by right clicking the button name. You can then select what you want shown there and can rename the container. As shown in this example.

Google Translate:

Каждый из контейнеров могут быть переименованы и реструктурированных щелкнув правой кнопкой мыши название кнопки. Вы можете выбрать, что вы хотите показать там и можно переименовать контейнера. Как показано в этом примере.

Ha, sorry. In English I have the whisper messages set as "to" or "from", I forgot that in Russian they were actually "whisper" based. Really it should be combat damage "to" or "from".

I apologize for the error in translation for "received". I will correct it.

Could you clarify more on your first and last comments?

Google Translate:

Ха, извините. В английском я шепотом сообщений устанавливается как "до" или "из ", я забыл, что в Россию они были на самом деле "шепотом" основано. Неужели это должны быть боевые повреждения "на" или "из".

Я прошу прощения за ошибки в переводе на "получил". Я буду наказывать его.

Не могли бы вы прояснить еще на первой и последней комментарии?

Oop, too late, heh. I sat around for around six hours making adjustments as singular world announcements came in.

Apparently all the world announcements are sent as tabled information that are put together into a format after they get to the client. Weird method, but it works, I guess. Had to figure out a way to reconstruct this without damaging anything. It should work the way I have it set up, but last I checked my color class code wasn't working properly. It doesn't affect the item link any, just doesn't show the color. The class should be named <rs class=params.results[index].name.."Quality"></rs>, as per the information found in params.text but when I tested that nothing happened.

Possibly because I overwrote the color change with my code elsewhere. I'll look into that.

I was just putting the finishing touches on loot, combat, experience, skill gains, and world announcements; world announcements being the most difficult to test and reconstruct, they've been holding me back from releasing my version of this add-on.

Thanks for the extra notifications that I forgot; reputation and auction messages. I'll try and add these while I wait for a confirmed test of world announcements.

Google Translate:

Я только последние штрихи на добычу, борьбы, опыт, умение выгоды, и мировой объявлений; мире объявлений является наиболее трудным для проверки и восстановления, они проводят меня от выпуская моей версии этого дополнения.

Спасибо за дополнительные уведомления, что я забыл, репутации и аукцион сообщений. Я постараюсь добавить их, пока я жду подтвердили испытания мира объявления.

Edit: http://i56.tinypic.com/wko309.jpg

No go on the reputation for right now; I'm getting errors from the two functions that call it saying they don't exist. Auction is done.

Не идти на репутацию прямо сейчас, я получаю ошибки две функции, которые называют это говорят, что они не существуют. : P Аукцион проводится.

-- FADE CONSTANTS

Global( "MESSAGE_FADE_IN_TIME", 350 )

Global( "MESSAGE_FADE_SOLID_TIME", 3000 )

Global( "MESSAGE_FADE_OUT_TIME", 750 )

My add-ons use EVENT_AVATAR_EXPERIENCE_CHANGED to track experience. So that could be used as well.

So the bug they repaired fixes the need for the changes involving GetGameLocalization()? Just trying to get a clarification.