You must login to post a comment. Don't have an account? Register to get one!

• 

  • Reply
  • #7

  sworisbreathing Thu, 01 Dec 2011 21:31:42

  BunnyCensor 0.1g is now live. This is only a toc change. All code remains the same.

  If anyone is interested in getting involved with the project, please let me know. I've thought up some new features I'd like to see in an official release, but I have neither the time nor the lua/regex experience to do it myself.

• 

  • Reply
  • #6

  sworisbreathing Thu, 14 Oct 2010 03:44:37

  BunnyCensor 0.1f is now live. Bugs related to WoW 4.0.1 should now be fixed. Sorry for the delay.

• 

  • Reply
  • #5

  sworisbreathing Fri, 25 Dec 2009 06:44:18

  BunnyCensor 0.1d is now live. With a new bunny feature: Custom Replacement Text!

  Example: To change the replacement text from "bunny" to "smurf", simply use:

  /bunnycensor replace smurf
  

  It's just that easy!

• 

  • Reply
  • #4

  sworisbreathing Fri, 07 Aug 2009 05:17:53

  BunnyCensor 0.1c is released! This is a trivial update, to make it work with 3.2.0.

• 

  • Reply
  • #3

  sworisbreathing Wed, 05 Aug 2009 02:37:29

  Patch 3.2.0 is out, and BunnyCensor (like many WoW addons) is broken :-(

  I'll try to roll out a new version this weekend. Until such time as it is fixed, please rely on WoW's built-in profanity filter for naughty-word-censorship.

• 

  • Reply
  • #2

  sworisbreathing Sun, 03 May 2009 17:10:23

  2009-05-03: BunnyCensor 0.1b is now available from Curse.

  I'm using Mercurial for the version control because I wanted to try something new (I'm already quite familiar with Subversion), and the results of my brief web search of "mercurial vs git" led me to believe that Mercurial was the safer choice (at least in terms of getting it up and running).

  This is my first WoW AddOn, as well as my first lua project. After experiencing the way CurseForge deals with approvals/rejections, let me just say that I look forward to working with them on this or other projects. It's such a relief to be told, specifically and in plain English, exactly why a submission was rejected. If you've ever been told that your "submission violates our project upload guidelines", you know what a relief it is to see something along the lines of "MACOSX folders were found in your file. This creates extra files when unzipping on non-OS X computers. Please re-zip your project without including such folders and re-upload."

  Seriously, props to these guys :-)

• 

  • Reply
  • #1

  sworisbreathing Sun, 03 May 2009 04:07:25

  2009-05-02: Curse admins rejected the initial import files due to the existence of Mac OS X files in the addon folder. I'll fix this tomorrow when I start using version control.

  You know, it's really nice that Curse specified the reason in the rejection email. It saves the developer a lot of time trying to figure out what he did wrong. Now, if only other entities followed this example...