Alex Mooney

Hidden at the bottom of these patch notes: https://www.reddit.com/r/RotMG/comments/6bx8am/patch_notes_277x14_20170518/ > And don’t worry, Muledump will still be usable with the changes, simply add &muleDump=true to the URL parameters.

You're right. `%B` is not being parsed on our Redhat machines because of the older version of git. It seems like `git log -1 --pretty=%aN,%aE,%ai,%P%n%s%n%n%b` might do the trick for...

I suspect that the generation of -5 weapons is a bug. If it's not a bug, then we should probably just make the damage 0 and have the AI drop...

Also happens with armor. 

This report is about the generation of really really terrible equipment; I've opened https://github.com/Attnam/ivan/issues/206 to track the negative damage problems.

I think we should just destroy (or prevent) any weapon generated that's so useless, but then again I'm not rolling up my sleeves and doing it... :stuck_out_tongue_closed_eyes:

The goal is to automatically generate a couple dozen presentations when the data they present is updated. Every couple of weeks, we get updates and I want to save everyone...

They won't be able to modify the Python code. They will definately have to modify the slides by hand after it's populated with the data but before it's shown to...

> @AlexMooney Could you [squash your commits](https://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#squashing-commits) please? 🙇 @zzak Sorry this notification got lost under a pile of work notifications. I just squished it.

> Both methods have this comment which should be changed: > > ``` > # The given range must be fully bounded, with both start and end. > ``` Thanks...