Post Your Small Addon API Suggestions Here

[ZorbaTHut]

function rarityColor(rarityName)
	ret = {}
	if rarityName == "trash" then ret.r = .34375; ret.g = .34375; ret.b = .34375;
	elseif rarityName == "common" then ret.r = .98; ret.g = .98 ret.b = .98;
	elseif rarityName == "uncommon" then ret.r = 0; ret.g = .797; ret.b = 0;
	elseif rarityName == "rare" then ret.r = .148; ret.g = .496; ret.b = .977;
	elseif rarityName == "epic" then ret.r = .676; ret.g = .281; ret.b = .98;
	elseif rarityName == "quest" then ret.r = 1; ret.g = 1; ret.b = 0;
	elseif rarityName == "relic" then ret.r = 1; ret.g = .5; ret.b = 0;
	else ret.r = .98; ret.g = .98 ret.b = .98; end
	return ret
end

Given the time investment required to come up with a generic information-requesting interface, and documenting that interface, and making sure it adjusts to the real values, and so forth, this is currently the official recommended solution to that problem

We'll have a better solution someday, but right now I think you'd rather have new APIs.

[Xenyr]

Could we enhance the addon saved variables code to rename the previous saved variables file to .bak before it saves the new values?

[ZorbaTHut]

Could we enhance the addon saved variables code to rename the previous saved variables file to .bak before it saves the new values?

At the moment, it actually writes to a ".new" file, then clobbers the old one and renames once everything's saved. I've heard there are sometimes problems but I'm currently unsure where those problems could be located.

[Aieny]

Inspect.Item.Detail needs to return base armor value for armor items.

[the_real_seebs]

Given the time investment required to come up with a generic information-requesting interface, and documenting that interface, and making sure it adjusts to the real values, and so forth, this is currently the official recommended solution to that problem

We'll have a better solution someday, but right now I think you'd rather have new APIs.

Fair enough. I'll shove it in LibBaggotry.

[dOxxx]

function rarityColor(rarityName)
	ret = {}
	if rarityName == "trash" then ret.r = .34375; ret.g = .34375; ret.b = .34375;
	elseif rarityName == "common" then ret.r = .98; ret.g = .98 ret.b = .98;
	elseif rarityName == "uncommon" then ret.r = 0; ret.g = .797; ret.b = 0;
	elseif rarityName == "rare" then ret.r = .148; ret.g = .496; ret.b = .977;
	elseif rarityName == "epic" then ret.r = .676; ret.g = .281; ret.b = .98;
	elseif rarityName == "quest" then ret.r = 1; ret.g = 1; ret.b = 0;
	elseif rarityName == "relic" then ret.r = 1; ret.g = .5; ret.b = 0;
	else ret.r = .98; ret.g = .98 ret.b = .98; end
	return ret
end

I've copied this to the RiftUI wiki: http://wiki.riftui.com/RarityColor

[snowdude366]

I was hoping you could add some of the same functions to the RiftTextfield frame type as we are given in the Text frame type, things such as SetFontColor() and such. I have been struggling with RiftTextfields for some time now in my menu windows when trying to set a background color for the RiftTextfield frames and the font color becomes almost unreadable if the background color is set to some darker colors.

[ZorbaTHut]

Inspect.Item.Detail needs to return base armor value for armor items.

Whoops, knew I was forgetting something. This may have to wait for 1.6.1.

[dOxxx]

Wrong thread, reposted in Changelog Discussion.

[ZorbaTHut]

Inspect.Item.Detail needs to return base armor value for armor items.

It seems to do so already. Can you give me the item type for an item it fails on?

Turns out it *doesn't* record Valor, Toughness, or Vengeance, though, and we'll put those in.

[Naifu]

It seems to do so already. Can you give me the item type for an item it fails on?

Turns out it *doesn't* record Valor, Toughness, or Vengeance, though, and we'll put those in.

Any chance this fix will find it's way into a hotfix for 1.6 or will it rather be implemented in a future minor / major Rift version (1.6.1 or 1.7)?

Also I'll try my luck by asking if you can give a rough timeframe as to when the itemkey <-> item type reference will be implemented in the items.xml file on your FTP server?

Cheers
N.

[ZorbaTHut]

Any chance this fix will find it's way into a hotfix for 1.6 or will it rather be implemented in a future minor / major Rift version (1.6.1 or 1.7)?

It'll be a 1.6 patch.

Also I'll try my luck by asking if you can give a rough timeframe as to when the itemkey <-> item type reference will be implemented in the items.xml file on your FTP server?

Cheers
N.

I'll go ping someone about that. Chances are good that I won't have a response until the response is "it's up now".

[ZorbaTHut]

I'll go ping someone about that. Chances are good that I won't have a response until the response is "it's up now".

And it's up now!

[Lorandii]

Inspect.Unit.Detail is missing CurrentExperience and MaximumExperience. MaximumExperience at level 50 is easy: 500 000 per planar level; levels 1-49 are the interesting ones.

Print("The player has " .. CurrentExperience .. "/" .. MaximumExperience .. " and needs " .. MaximumExperience - CurrentExperience .. " to gain a level.")

I am getting the impression that Inspect.Unit.Detail is getting a tad bloated, but it would nice to also have the Noteriety levels. Preferably, because there are so many factions, this would be a different Inspector.

[Sithsa]

I would like to have the ability to call '/emote <text>' added to the addon api.

I was trying to write an addon which lets you expand the emote capability of the game with custom ones.