Outfitter Recipes

[Gilley]

Discussion thread for Outfitter Recipes wiki. If you would like to add a comment, click the New Reply button.

[Battleborn]

Ok we need to get some discussion going about how we should lay out the data. A couple of things come to mind as to how I think it should be laid out, but this is a group effort so everyone chime in plz.

First we should order them by tiers. I think we should do level over lap, where need be, and correctly show everything available by/within a tier. Actual made items vary in level based on what you add to them in the making process so I don’t think we should do it by item level. Level and variations on items should be left to the actual page of the item.

Recipes can often be "bought" at a different level than the Level of difficulty the recipe. So after ordering them by tier I think we should order them by level of difficulty and then side note the level of purchase, since that is we are most commonly looking for with the recipes.

I can see using the level of purchase as a way to go since this is a player’s first point of interaction with recipes, and then side noting the level of difficulty and/or tier. I just don’t think it will be as useful to us at a quick glance. I think most people will want to quickly check level of difficulty since that is not labeled in game. Should that change then I would see moving the table to a level of purchase orientation. If we explain carefully what is going on then a new player will be able to follow our layout.

So anyone else have any thoughts?

[Taronn Anvilmarr]

Battleborn, are you referring to recipes or work orders?

I have never seen a recipe offered to me ahead of time as of yet. Work orders can be done above the lvl you currently hold so maybe you are talking about work orders.

My suggestion is to allow sorting of recipes at the instructors in a "tree" type of form - like windows explorer kind of functionality. That way we could close off the subclass that we dont use (carpenter) and only see and concentrate on the subclass that we do use (minerologist).

They seem to want us to be able to see all the recipes available to the main class in general, but just be able to access and train in the subclass we have chosen.

Of course this would apply across the board for all crafting professions.

[Battleborn]

Well in the medium and light armor professions we get recipes early all the time. e.g. As I recall, we get chest pieces at 18th level, but they are lvl 20 difficulty.

The reason they may have laid it out in the current table form is that many of the recipes, Outfitter wise, are the same in terms of availability. So you if one side is incomplete, but there is info on the other side, then you can use that data to guess what is going to happen. In addition many of the original class recipes are used across classes. i.e. Blacksmith items (grips come to mind) are used in both subclasses, so it would help in some cases to see what the original class can make.

In general though, much of this applies to Outfitter. Artificers' two subclasses do not likely have any symmetry in them, and I have no reasonable amount of xps in the Artificer classes.

The "tree" form is ok, but I don't know how to program that in the wiki. Where as I do know how to do the tables and I think they mostly work, or will with clarification.

I do see how on the Artificer side there is not much need to see the recipes of the other subclass, and there isn't that much of a need in the other 2 classes either.

Do you (or anyone) know how to program a "collapsible tree"?

[SwordMage]

When I started the Outfitter page, I intended it to be listed by recipe level; however, I could go with either one (with the alternate level being part of the recipe page). Both have their pluses and minuses (and I can probably see strong arguments for purchase level).

I probably won't be coming back to play VG for a while; so I will kibbitz, but not try to push this kind of decision one way or the other.

I would have no problem splitting the artificer page into two tree column pages if the 4 column tables really don't look sane. However, from what I see, they seem workable.

-----

As far as a tree structure, I have seen some of the newest wikia using a tree form; however, I am pretty sure this version doesn't support it yet.

Even if we did have it, I don't think the tree format is particularly suitable for the recipe lists since for each specialty needs 3 of the 4 columns anyway. The tree would stretch things out down the page significantly. As long as the 4 columns fit pretty well on the page, I think they are the clearest way to organize this data (I would actually suggest going to per-specialty, 3 column tables before the tree).

[Galahad]

i can make collapsible trees using javascript, i had to do it for a page here at work. as far as using wiki tools, haven't used them yet.

i do like the idea though, because as of right now, i have to retry every level to see if i can make something grade a yet, but having the level of difficulty on the wiki would help save me a lot of resources.

actually, i'm a computer programmer by profession and passion, but currently got stuck in a web development office and have been programming in coldfusion with mixed in javascript for a few months now.

[Taronn Anvilmarr]

wow - i thought you were asking about in-game info - if you want to apply that idea to the wiki here woot go ahead - great idea!!

I cant program in java or much else - last time i got into it was in the early 80's - inputing from the back of a magazine lol was fun though.

[SwordMage]

Originally Posted by Galahad

i can make collapsible trees using javascript, i had to do it for a page here at work. as far as using wiki tools, haven't used them yet.

i do like the idea though, because as of right now, i have to retry every level to see if i can make something grade a yet, but having the level of difficulty on the wiki would help save me a lot of resources.

actually, i'm a computer programmer by profession and passion, but currently got stuck in a web development office and have been programming in coldfusion with mixed in javascript for a few months now.

Which idea do you like: the collapsible trees or showing the actual recipe levels in the table?

I just took a glimpse at the help on Wikimedia related to javascript. I really don't think we want to move down that road; it seems, from what I read, that activating javascript on wiki pages pretty much eliminates any server security. I may have stopped reading too soon, but that scared me.

Given that the original suggesting for using trees was actually made in the context of in-game display enhancements, we may want to move back into the discussion of table formats and contents.

[Galahad]

it really depends on how it's written, but as far as i'm concerned, just putting the difficulty levels in the tables would be great. It's easily readable and understandable, so no reason to get fancy.

[Balaern]

Check out the Artifcer Recipe Table, it's completed, as far as purchasable recipes are concerned.

If there are no objections, I'd probably get around to completing outfitter sometime this week/weekend.