This project is read-only.

Calling All Developers!

Topics: Rawr.Addon, Rawr.Base
Dec 6, 2013 at 1:03 PM
If you're reading this and you're a programmer of any sort, I want you to come and be a part of our team. I love Rawr and I think it's a great program that works better than Ask Mr. Robot or any of the theorycrafting spreadsheets as far as user friendliness and accuracy in defining upgrades and the value of gear. The problem with Rawr is, we need more programmers to come in and replace those who have moved on to other games and other projects, because World of Warcraft is constantly changing and we need to change along with it. If you're interested in working on a neat tool that does lots of intense math, drop me a line! We're taking applications for maintainers of class modules, people who want to add new baseline features, and especially someone who might want to take up the project of the Addon, which is our #1 requested feature update. I'm good, but I can't do it all, at least not in any reasonable time frame for our users. So come aboard! We'd love to have you come write code for us.
Dec 6, 2013 at 6:58 PM
Hi Dope,

Where do we stand in terms of maintainers for the class models? I think that's where there's a big problem with Rawr -- and that's where I'm getting stuck with my motivation. If we release a tool that works great for one or two models (I'm thinking Mage is the one that gets the most love?), then the tool doesn't look right / doesn't make sense for the other classes.

We really need to make a concerted effort to get that up-to-date. As for me, I had gotten the addon working for some mop versions (though not the latest), but I lost motivation because the models were out-of-date (so who cares about the addon import / export path if the theorycrafting is broken). If I get a sense that there is a significant up-take then maybe I can pitch in and do my part. Heck, my main is a cat / bear, so I am motivated to fix that too, if only it feels like the tool is not dead.

How do we make sure that enough ppl are on board? I see your plea for help, but is that a sufficient strategy? Maybe someone should spam the theorycrafting forums too?

Dec 6, 2013 at 7:30 PM
That's why I made the discussion. I'm also going to eat some humble pie and go to Elitist Jerks this weekend; I also plan on opening an official Rawr Twitter account (that will be passed along to whomever the current maintainer is, should I ever give it up) that we can post updates and requests with. I'm planning on getting some feedback on the official WoW forums, too. I'm on a Druid podcast that I put in a plug for to hopefully find some Druids out there that might want to help us. I'm trying to broaden my advertising strategy. Right now, we have myself on Moonkin, and Omniaa on Mage (and even he's not putting in as much effort as he used to). We had a guy come along for Warlock, but I have no idea what happened with that. I am absolutely intending on getting more people to establish at least a respectable set of models; I don't expect to ever have all 34 specs represented and maintained, but I hope to get some reasonable percentage thereof. And I will be advertising every way I can find, not just here.
Dec 7, 2013 at 8:29 AM

Thanks a lot for your response. Just to be clear, I wasn't trying to be discouraging, I was just explaining my dilemma / blocking factors to contributing. If the momentum is there it will probably get me off my butt to pitch in too.

I was also wondering if the right thing to do at this point is re-brand Rawr for what it can really do. For that, I mean, should we just turn off the models that are just out of date? Or maybe is there room for some kind of generic model that just accumulates stats so if you want to see your stat summary from one set of gear to another (but without any analysis) you can do that? It's of limited value to be sure, but it's no less value than models that are obsolete and incorrect entirely.

Dec 7, 2013 at 1:33 PM
Well, going into Warlords I am absolutely turning off/disabling models that don't work, but largely because I've already changed some core Rawr mechanics and don't want to spend time picking through irrelevant models to fix compile errors. A default model that has zero deep analysis might help - I know some people get turned off by an application that crashes or does some other unexpected behavior when they load a character, even if they've been told their character isn't supported. Those are both good suggestions as far as how to do the best with the staff we have, but one thing we definitely need (that I've agreed with you on for a while) is to try to staff up and just get some more working models. That'll bring people to actually use our program, because you're right - if Mage and Moonkin are the only two functional areas, they're both widely represented classes but it's still only 2 of 34 possible specs!
Dec 9, 2013 at 3:11 AM
Edited Dec 9, 2013 at 3:19 AM
I am probably going to be coming back to Rawr soonish; possibly this week. May need to get in touch with Dope about it. Basically had some job issues recently and I have some free time at least until the start of the new year hopefully longer. I don't think I'll be able to get back into the Feral or Guardian modules since I really have not been following the theorycrafting on it recently. Due to switching my main to Monk, I can probably work on that. Considering even after 1 expansion there is disagreement on how to play the Windwalker spec (and Blue posts stating as such), if I can get that working, I think I can get that going.
Jan 5, 2014 at 1:44 PM
Hi. I recently have come back to playing wow and I might be able to help, I am still updating myself on the theorycraft, I am going to download the source and start taking a look at it to see if I can handle it. Haven't really worked with C# just done official courses but i do have experience with web java development, going to fire up visual studio and start taking a look, but please tell me if the project is still active.
Jan 6, 2014 at 1:52 PM
Hey! Yeah, the project is still active, albeit barely. Development has been in a bit of a lull because I've had other stuff going on, but I'm hoping to get started on integrating the new secondary stats and cleaning up the old useless stats here Soon (tm). You're more than welcome to play around with the source code as you like.
Jan 9, 2014 at 3:00 PM
Hi I recently restarted playing Wow. I reached level 90 yesterday. I'm a french player so sorry for my English. I'm a C# developer. I'm not an expert on theorycrafting but, if I can help on development, I may have a look on my personnal time and help with some code too.

Jan 11, 2014 at 4:55 AM
I am not playing WoW anymore, but I am still interested in working on this. I will look into getting the Elemental and Enhance modules back into working order.
Jan 12, 2014 at 7:03 PM
Nicco, I approved your developer request today. Welcome to the team. :) Timetodance, thank you, that would be wonderful. I appreciate everyone's help on this, it's a big project but I hope we can make it go again.
Jan 13, 2014 at 8:41 AM
Thanks. I will download asap the source code. I will need a few time to navigate into the code ;)
Jan 15, 2014 at 9:26 PM
Hey, I'm in the same spot as Nicco, I just started back up but I'd be willing to put in some time to at least try and get the Retribution model up to date. Looks like a good chance to expand my C# knowledge out of ASP.NET a little more. If you need any of my credentials let me know. My resume isn't exactly up to date but I'm sure I can put something together.
Feb 20, 2014 at 12:16 AM
Hello. I would be willing to help. I have been working with C# since it was released.
Mar 5, 2014 at 1:43 PM
The models development page has not been updated since 2012. My main is priest and I am a senior developer with decades of development experience, including years of C#. Is priest model needing a maintainer?
Mar 7, 2014 at 9:12 AM
Edited Mar 8, 2014 at 4:20 AM
I'll work on updating the model status page.
I am reasonably certain that we do not have anyone maintaining the priest modules.

Edit: Updated the model status page to the best of my knowledge. For any existing and new developers, could you add yourselves to current developer section beside the module you are working on.
Apr 14, 2014 at 8:52 PM
Included this in my commit note for change 74181 that updates miss/parry/etc. to be in-line with removal of hit/expertise. As part of this, there needs to be a decision on whether to "rip the bandaid" and take out Rawr.Base references to Hit/Expertise that will be removed in WoD. That will cause most (all?) class modules to not build, but may give us a far more realistic picture of how far away from viability we are.

I know generally the theory is "don't break the build", but I think that's going to be tough in this situation. All references to those could be commented out of the individual class modules, but without understanding the individual modules, there's a good chance that will host things up even worse and make it harder to find them to fix. I did a test removal in Base, and got about 80 bad references in just that module alone. This one isn't going to be fixed overnight, but wanted to at least get the discussion rolling here.
Apr 14, 2014 at 8:56 PM
I agree that it's the right thing to do. I'm uncertain if it's the right thing to do right now. I have a changeset in flight for Moonkin right now; after I'm finished working on these changes, why don't I have a look at how bad it'll be for removing hit/expertise from Base. I know a bit more about the Base code and I can hopefully figure out how to fix at least that code correctly.
Jun 6, 2014 at 10:09 PM
This project is dead, otherwise you would properly respond to e.g. my application as a developer....
Jun 6, 2014 at 10:13 PM
Edited Jun 6, 2014 at 10:15 PM
Well, I'm incredibly sorry that I don't get everything done on your timetable. Duly noted.

Edit: And considering that you're already a developer, I'm not exactly sure what else you would want me to do.
Jun 16, 2014 at 9:10 PM
Edited Jun 16, 2014 at 9:11 PM
I'll be returning as well, but alas not on shaman. Hard to work on a class I haven't played seriously since the end of ICC.
There's just such a massive black hole of decent theorycraft in the holy paladin world, being one gives you not a lot of places to turn for information.

Most just go to icy veins and use AMR to spit out whatever gear it assumes you need. With randomness coming to gear down the road with special ratings, rare sockets, if there were ever a time to get Rawr back up and running, now would definitely be the time.
Jul 2, 2014 at 12:32 PM

I'm Rottennerve from EU-Daggerspine, semi-hardcore player since Vanilla till the start of cata. I'm also a game programmer IRL and I'm currently returning to WoW and gearing up.


I connected to SVN, downloaded rawr and saw a lot of errors during compilation, strange that ppl keep committing changes that didn't work.

As I'm playing on mage mostly I unloaded other classes and made it to compile only a mage. Doing so I found silly hardcoded default class in Characters.cs although I had a Mage being configured in Settings.Designer.cs.

Okay, so yay, it is built and it works! Firstly i will try to update the maximum numbers of upgrades from 2 to 4 for SoO items.

Planning to check the rotation for Frost as I can believe what mr robot says these days about haste>int stuff, but you can't blame mr. robot - it has a static weights table.


Yours sincerely Rottennerve @Daggerspine Furious Few guild
Jul 2, 2014 at 12:48 PM
Okay, I have read some previous posts: I get it now why there are some compilation issues :)
Jul 2, 2014 at 5:32 PM
Hi Rotten,

Guessing from your second message that you've sorted it out, but basically the stat changes with WoD led us to strip out the stats in the core (Rawr.Base), which resulted in all modules referencing that not building. I think the general idea was to give a little time for people to fix modules that are active or semi-active, then remove modules from building that are not at all updated.

To All - I'm thinking about a stop-gap here to still allow everything to build where we basically go in and comment out the lines that aren't needed but add exceptions to be thrown if they're actually initialized (selected) in the interface. That would allow things to build, but still signal clearly what is and is not ready for even basic usage. Basic goal here is to just "un-break" the build so that people who are trying to get involved don't have a hard up-hill climb to even get the thing to build and enable walking through the code. Thoughts?