Closed dazer closed 12 years ago
So... I've been meaning to post on EJ about this, and sort of feel out where people want to go with theorycrafting tools. Partly because I don't expect to have as much time to devote to the project as I have for expansions in the past. I might help some, but I don't really expect to be able to singlehandedly write the entire model like I've done before. Particularly since I will probably spend at least some attention on Monk DPS.
My feeling is that the exact architecture should be more up to the people who are doing the heavy lifting, and as that's unlikely to be me...
If you'd like my advice on what I think worked well (and not) in this expansion, and/or which directions I might want to explore were I continuing to spearhead this, I'll happily provide it; but I'm trying not to dominate a project that I will probably have a much smaller role in come Mists.
On Tue, Apr 3, 2012 at 3:38 PM, dazer < reply@reply.github.com
wrote:
I think it's time we start thinking about the next xpack. Before I start pushing code I'd like to know what people think should be done. I'll throw some thoughts out, see what you guys think:
For starters, how do these big changes affect us? would it be interesting to keep somehow the present Shadowcraft as a comparison tool? should we keep adding to the existing project?, start a new one?, branch the existing one as to signify a landmark?.
Talents got a major revamp. I imagine we don't need the subclassing anymore as game-classes are a lot more simple in this department. Do we want a similar input like we had before with the three numeric strings? it'd be something like '121132'; or keep the format for glyphs (passing all the talent names)?.
The damage calculator class needs some clean-up since talents, as we once knew them, are gone. I recall some formulas were coded somewhat funky so that'll need some work too. As for numeric values, once it's possible we'll need to figure the new damage modifiers, combat ratings, armor, etc. In the same line, the model will need some major updates to include the new abilities and deprecate old talents.
Frontend: I don't know if Antiarc will still be doing his amazing work; the last updates got a bit slower than I would have liked (with all the confusion in the forums). I've been toying with Android and I intend to make one app for ShadowCraft at some point in the future (porting the engine to Java and all that). Did the python UI get any use? I kept adding items but didn't really play much with it.
Other classes: I might try and write a model for windwalkers. Is this to be merged with Aldriana's project? or should I keep my own repo? is anyone else interested in working on other specs or helping out with monks?.
Reply to this email directly or view it on GitHub: https://github.com/Aldriana/ShadowCraft-Engine/issues/96
Even if you step aside, I believe Shadowcraft will inevitably be entangled to you no matter what: you've been the driving force and, as much as it developed as a comunity work, the ideas behind it spell your name, not to mention that the success of this tool has a lot to do with the "Aldriana's seal of approval". Every piece of input is appreciated; you having an opinion but not writing the code won't necesarily make it so you're the head of the project: you can coach it just as well.
Praising aside, I have the feeling that I've been heavily hand-held in this project (after all, I started working on it with next to zero knowledge of programming). So yes, I certainly would like to know your ideas about how to keep this thing going forward.
Maybe this would go better in EJ; I was just testing the waters here, see if 'code-capable' people are still interested in developing this. In the latest patches not many people pushed code; I still don't know how much spare time I'll have to work on it, but the idea of building up to Mist all alone is daunting to say the least.
I agree that I'm probably going to be affiliated with any ShadowCraft-based tool created going forward. That said: I don't want to tell my successors
Anyway, sometime soon - probably this weekend - I'll try to get a post up on EJ for people to discuss what they liked, what they didn't like, and which direction they'd like to see things go, as well as who (if anyone) is interested in working on tools for Mists. Hopefully that will help us hash things out in more detail.
On Wed, Apr 4, 2012 at 1:46 AM, dazer < reply@reply.github.com
wrote:
Even if you step aside, I believe Shadowcraft will inevitably be entangled to you no matter what: you've been the driving force and, as much as it developed as a comunity work, the ideas behind it spell your name, not to mention that the success of this tool has a lot to do with the "Aldriana's seal of approval". Every piece of input is appreciated; you having an opinion but not writing the code won't necesarily make it so you're the head of the project: you can coach it just as well.
Praising aside, I have the feeling that I've been heavily hand-held in this project (after all, I started working on it with next to zero knowledge of programming). So yes, I certainly would like to know your ideas about how to keep this thing going forward.
Maybe this would go better in EJ; I was just testing the waters here, see if 'code-capable' people are still interested in developing this. In the latest patches not many people pushed code; I still don't know how much spare time I'll have to work on it, but the idea of building up to Mist all alone is daunting to say the least.
Reply to this email directly or view it on GitHub:
https://github.com/Aldriana/ShadowCraft-Engine/issues/96#issuecomment-4949500
This has been redirected to the EJ fori.
I think it's time we start thinking about the next xpack. Before I start pushing code I'd like to know what people think should be done. I'll throw some thoughts out, see what you guys think:
For starters, how do these big changes affect us? would it be interesting to keep somehow the present Shadowcraft as a comparison tool? should we keep adding to the existing project?, start a new one?, branch the existing one as to signify a milestone?.
Talents got a major revamp. I imagine we don't need the subclassing anymore as game-classes are a lot more simple in this department. Do we want a similar input like we had before with the three numeric strings? it'd be something like '121132'; or keep the format for glyphs (passing all the talent names)?.
The damage calculator class needs some clean-up since talents, as we once knew them, are gone. I recall some formulas were coded somewhat funky so that'll need some work too. As for numeric values, once it's possible we'll need to figure the new damage modifiers, combat ratings, armor, etc. In the same line, the model will need some major updates to include the new abilities and deprecate old talents.
Frontend: I don't know if Antiarc will still be doing his amazing work; the last updates got a bit slower than I would have liked (with all the confusion in the forums). I've been toying with Android and I intend to make one app for ShadowCraft at some point in the future (porting the engine to Java and all that). Did the python UI get any use? I kept adding items but didn't really play much with it.
Other classes: I might try and write a model for windwalkers. Is this to be merged with Aldriana's project? or should I keep my own repo? is anyone else interested in working on other specs or helping out with monks?.