Go to Page... |
Compatibility: | Harrowstorm (5.3.5) |
Updated: | 02/28/20 02:09 PM |
Created: | 10/26/18 04:58 PM |
Monthly downloads: | 1,128 |
Total downloads: | 144,916 |
Favorites: | 66 |
MD5: |
LibCraftText.DailyQuestNameToCraftingType("Enchanter Writ") ---> returns CRAFTING_TYPE_ENCHANTING LibCraftText.ParseDailyCondition(CRAFTING_TYPE_ENCHANTING , "Craft Superb Glyph of Health with Ta: 0/1") ---> returns table: { essence = { name="Oko", item_id=45831, ... } potency = { name="Rejera", item_id=64509, ... } aspect = { name="Ta", item_id=45850, ... } } LibCraftText.ParseDailyCondition(CRAFTING_TYPE_CLOTHIER , "Craft Normal Ancestor Silk Shoes: 0/1") ---> returns table: { item = { name="shoes", mat_set_id=mat_lgt, pattern_index=3, ... } material = { name="Ancestor Silk", mat_set_id=mat_lgt, level_index=10, ... } } LibCraftText.ParseDailyCondition(CRAFTING_TYPE_ALCHEMY , "Acquire Mudcrab Chitin: 3/3") ---> returns table: { item = { name = "Mudcrab Chitin", item_id=77591, ... } } -- and if your ESO UI is set to DE German or some other supported -- language, then the name strings change, but the numbers don't: LibCraftText.ParseDailyCondition(CRAFTING_TYPE_ALCHEMY , "Besorgt etwas Schlammkrabbenchitin: 3/3") ---> returns table: { item = { name = "Schlammkrabbenchitin", item_id=77591, ... } }
File Name |
Version |
Size |
Uploader |
Date |
5.0.1 |
152kB |
ziggr |
05/05/19 03:37 PM |
|
4.2.5 |
152kB |
ziggr |
11/25/18 07:47 PM |
|
4.2.4 |
92kB |
ziggr |
11/12/18 05:18 PM |
|
4.2.3 |
10kB |
ziggr |
10/28/18 12:07 AM |
|
4.2.2 |
5kB |
ziggr |
10/27/18 10:16 PM |
|
4.2.1 |
4kB |
ziggr |
10/26/18 04:58 PM |
![]() |
Comment Options |
hotrockin |
View Public Profile |
Send a private message to hotrockin |
Find More Posts by hotrockin |
Add hotrockin to Your Buddy List |
ziggr |
View Public Profile |
Send a private message to ziggr |
Send email to ziggr |
Find More Posts by ziggr |
Add ziggr to Your Buddy List |
![]() |
||
|
Thoughts?
I had someone report this error to me. Do you have any suggestions for a work around? I can't seem to reproduced this error.
|
|
![]() |
![]() |
Argusus |
View Public Profile |
Send a private message to Argusus |
Send email to Argusus |
Find More Posts by Argusus |
Add Argusus to Your Buddy List |
![]() |
||
I don't actually use LibCraftText within WritWorthy for writ parsing, or anything, really. I do use LibCraftText for some private add-ons to drive daily writs and Rolis. |
||
![]() |
![]() |
ziggr |
View Public Profile |
Send a private message to ziggr |
Send email to ziggr |
Find More Posts by ziggr |
Add ziggr to Your Buddy List |
![]() |
|
Hey, I'm actually no longer (mostly) using lookup tables for daily writs. Instead, I'm using DoesItemLinkFulfillJournalQuestCondition and doing some loops. So that's an option too.
|
|
![]() |
![]() |
Dolgubon |
View Public Profile |
Send a private message to Dolgubon |
Send email to Dolgubon |
Find More Posts by Dolgubon |
Add Dolgubon to Your Buddy List |
![]() |
|
|
Thanks Ziggr. This will make addon development for the writ stuff easier to support all the given languages!
I hope the devs will find it if they start a project ![]() |
![]() |
![]() |
Baertram |
View Public Profile |
Send a private message to Baertram |
Send email to Baertram |
Find More Posts by Baertram |
Add Baertram to Your Buddy List |
![]() |
|
6 languages supported
EN DE FR ES RU JA
All official and unofficial translations now supported. I've got the daily and master crafting quest titles for the above six languages. IT Italian: the translation project hasn't gotten to crafting writs yet, neither daily nor master, so the language file for that is a placeholder for now, filled with EN English strings. If any translation changes out from under me and breaks this library, let me know and I'll update the library. Still haven't gotten to Rolis dialog yet. Maybe tomorrow. Maybe not. Depends on how ornery the crafting tables are on PTS. --Z PS: the GitHub repo has all the fancy-schmancy automation that I use to scrape translations from the current ESO client and merge them into a database that I use to generate all the language files. Here's the database file. Lua Code:
|
|
![]() |
![]() |
ziggr |
View Public Profile |
Send a private message to ziggr |
Send email to ziggr |
Find More Posts by ziggr |
Add ziggr to Your Buddy List |
![]() |
||
Re: Nice lib!
Good idea about the community language packs. I'll wait until there's a bigger motivation than "Some of Zig's add-ons use it" before pestering them. But I'm adding it as a todo so that I don't forget about it if/when this library gains traction. |
||
![]() |
![]() |
ziggr |
View Public Profile |
Send a private message to ziggr |
Send email to ziggr |
Find More Posts by ziggr |
Add ziggr to Your Buddy List |
![]() |
|
Nice lib!
This is a really good idea, kudos.
![]() ESO has only three 'official' language modes: English, French, and German. Any other client language relies on 3rd party language pack addons. These translations are created by the community and subject to change, and in some cases there might be multiple different language packs (Japanese for example) to choose from. If an addon looking to track writs doesn't see exactly the right text in the quest name or status, which could be likely with custom translations, then the entire writ tracking functionality of that addon will not work when using that language pack. Having a library to standardize the text strings used by writ quests to indicate requirements or completion status within each of these community language pack addons would greatly ease the work of other addon authors having to download each custom language pack in turn and find the string (if any) assigned to these values manually (and each time the language packs are updated in perpetuity). What will ultimately be required for this to be relevant however is contacting the authors/maintainers of each community language pack (Spanish, Italian, Russian, Japanese) and convincing them to adopt this library as the standard for translating these select writ strings within their mods, providing any corrections as needed. That way any addon tracking writ quests could simply and reliably do so in any supported language with minimal additional and repeated upkeep work otherwise required to ensure text string matching didn't break over time and language addon updates. |
|
![]() |
![]() |
Phinix |
View Public Profile |
Send a private message to Phinix |
Send email to Phinix |
Visit Phinix's homepage! |
Find More Posts by Phinix |
Add Phinix to Your Buddy List |
![]() |