Greasy Fork

Optional Assets at character level

I absolutely love your script. I did make one minor change, though. I move the Option Assets checkbox down to the character settings instead of in the main section. I like to be able to control this for each character since I may have some asset-poor characters. I'm not great at javascript coding but I can share what I have with you if you're interested in implementing it this way.

If its ready for test then make "unlisted fork" or use some other way to public it.

There is also minor failure,

https://greasyfork.org/en/forum/discussion/3523/x

, script seems to need "idle check" and "better error detection",.

Not sure how to do this. Is this something on greasy fork or on github?

Here's a copy on pastebin: http://pastebin.com/pjCV61Qm

Here is the mod 5 tabbed version with optional assets per profession per character.... the optional asset switch in the main profile acts as a master on/off switch as well. http://pastebin.com/NpDEgD41

Here is the mod 5 tabbed version with optional assets per profession per character.... the optional asset switch in the main profile acts as a master on/off switch as well. http://pastebin.com/NpDEgD41

Cool,

I was thinking that it needs "Use optional assets" act like "Master" and per character just takes action over. Looks valid now, ;D.

That way users who have 20+ character or multiple accounts has less "troubles".

...any ideas for this,

https://greasyfork.org/en/forum/discussion/3523/x

, it seems to be quite random error, I think its just somekind "load error", not happen daily with 10x browser and "auto reload" deal it well.

ps. @Quinncy, can you look it again, make "Use Optional Assets" work as master and per character settings if used takes over asset selection.

Here is the mod 5 tabbed version with optional assets per profession per character.... the optional asset switch in the main profile acts as a master on/off switch as well. http://pastebin.com/NpDEgD41

If you want merge your changes to Greasyfork -supported version, you need use Greasyfork version as master.

Check difference, https://www.diffchecker.com/ggzgvrpt

Github Noonerelly ver. 2.0 is nice, but I cant support it.

I'll try to play with it this evening. I've never used Github so I'm clueless about merging changes. I typically do everything in Sublime text editor I use total commander for diff compares.

I'll try to play with it this evening. I've never used Github so I'm clueless about merging changes. I typically do everything in Sublime text editor I use total commander for diff compares.

Well, I think you look wrong direction now, ;D.

Greasyfork has now version 1.10.5 and it is same what you used.

Only thing is that, Current "Use optional asset" must be Master switch and per character "use assets" override it.

This will make easier handle accounts/multiple characters, I hope you got it?

Changes what will not directly affect users settings are easier handle...

Wow. Just checked out the 2.0 version That options panel is amazing... Great job!

Here

ps. @Quinncy, can you look it again, make "Use Optional Assets" work as master and per character settings if used takes over asset selection.

The only way I can think of to implement both a global and a character setting is to make it a drop-down with Yes, No and blank values and if it's blank use the global setting (if it's defined).

If we're going to leave it as a checkbox then it should only be defined in the character section.

So, should we leave it as a checkbox or use a dropdown? Also should I try to update the 2.0 version or stick with the latest version?

Here

ps. @Quinncy, can you look it again, make "Use Optional Assets" work as master and per character settings if used takes over asset selection.

The only way I can think of to implement both a global and a character setting is to make it a drop-down with Yes, No and blank values and if it's blank use the global setting (if it's defined).

If we're going to leave it as a checkbox then it should only be defined in the character section.

So, should we leave it as a checkbox or use a dropdown? Also should I try to update the 2.0 version or stick with the latest version?

I have no plan to go ver. 2.0 before Mod6 changes and after that it is only support question.

Is 2.0 working now or is it still in progress? I can test it some if you like.