Shipwright Archive
Thread: interdependence
Besides, you can't make an expansion interdependent because some people do not buy the expansion.
CerionSkydreamer wrote:
We hashed over interdependence in beta. The fact is, there would be no TRUE interdependence as shipwrights make no components that other professions could use. Sure other professions make items that a SW could use, or could be integrated, but then you have DEPENDANCY not INTERdependency...that in my opinion and many others in beta is bad.
Besides, you can't make an expansion interdependent because some people do not buy the expansion.
With the feel of the game i got i don't think i completely agree with your statement here. I think interdependency would exist if SW's need components from Armoursmiths, Weaponsmiths, and Droid Engineers for ships. Yes that would create a dependency for the SW's, which is no different than current proffessions. I am an AS i need tailored components for my armour. As well look at the resource consumption ... no way a single player can digup that much steel alone. I saw no reason SOE couldn't incorporate the current crafting proffession's into JTL.
And as far as the i need stuff from them, but not vice versa arguement ... how exactly are these players that purchased the JTL plan on getting past tier1 in any of the piloting proffessions? Answer complete dependency on SW's. I saw tier1 TIE's going for 200K on radiant last night. The idea of having SW's build everything required for ships is not an arguement agaisnt dependency on other proffessions, it is an arguement in favour of complete SW dependency, while i really have nothing against it even as an AS who would be one of the affected proffessions, at least have the nerve to state your intentions.
Ewach wrote:There's nothing wrong with one profession being dependent upon another, rather than independent.I can't think of a single thing, schematic wise,that Master Artisans require from Droid Engineer, yet DEs rely on the MAs for their electronics.Same goes for architects and Master Artisans. Now, the case could be made that a MA requires factories and crafting stations, but those are the products and are not plugged into the actual crafting schematic.Also, if you want to go that route, you could argue the WS that supplies required parts to a SW (if it were that way) then relys on the SW for a ship if he wants to be a pilot.The lack of integration with the ground game, and existing crafting professions, within SW is appalling. The shipwright is now the ONLY crafting profession in the game that doesn't require anything from another profession.I think this was done not because of concerns with dependency, but because it was simply easier this way. Easier is not always, often never, the best option.Possible examples of where some dependency could have been introduced without even modifying existing professions:WS subcomponents used for ship weaponsMA electronics required for reactors and suchAS subcomponents required for armor and shields (after all, a ship shield is just a big version of a PSG)And those are just a few ideas.These could be optional components, like the MA electronics in the crafting stations, but they would be necessary for high quality parts.
yep, what Brilyn said--
let me clarify with a rhetorical question. "Is every profession dependent on every other profession?" No. But no profession stands alone. DE can use composite plates from AS, but Archis need droid compartments from DEs for crafting stations.
So there is a web of interdependency--but not all are two way streets so to speak. Shipwright offers nothing in return that other professions could use.
and no, ships are PRODUCT and cannot be considered 'needed' by a profession.
And my statement about not all people purchasing JtL still stands as a valid barrier to interdependency.
wilibus wrote:
CerionSkydreamer wrote:
We hashed over interdependence in beta. The fact is, there would be no TRUE interdependence as shipwrights make no components that other professions could use. Sure other professions make items that a SW could use, or could be integrated, but then you have DEPENDANCY not INTERdependency...that in my opinion and many others in beta is bad.
Besides, you can't make an expansion interdependent because some people do not buy the expansion.With the feel of the game i got i don't think i completely agree with your statement here. I think interdependency would exist if SW's need components from Armoursmiths, Weaponsmiths, and Droid Engineers for ships. Yes that would create a dependency for the SW's, which is no different than current proffessions. I am an AS i need tailored components for my armour. As well look at the resource consumption ... no way a single player can digup that much steel alone. I saw no reason SOE couldn't incorporate the current crafting proffession's into JTL.
And as far as the i need stuff from them, but not vice versa arguement ... how exactly are these players that purchased the JTL plan on getting past tier1 in any of the piloting proffessions? Answer complete dependency on SW's. I saw tier1 TIE's going for 200K on radiant last night. The idea of having SW's build everything required for ships is not an arguement agaisnt dependency on other proffessions, it is an arguement in favour of complete SW dependency, while i really have nothing against it even as an AS who would be one of the affected proffessions, at least have the nerve to state your intentions.
First, please use interdependency correctly..not to be snide, but you use both interdependency and dependency in the same breath to describe the same system. They're not the same. Secondly, to address my highlighted point above, it most certainly IS different. DEs can buy your composite plates for armor. DE's need electronic parts from MAs, MAs need droid storage compartments made by DEs, DE's need parts from Architect, Architect needs parts from Tailors...on and on.. That's interdependency, not the one way street of DEPENDENCY people advocate most often.
Don't get me wrong, I like interdependency. I think it's a good thing in the current ground game. I'm not a fan of dependency.