Beer blog

The phpBBModders.net beer blog is not about beer, as the name may suggest. Here we discuss what’s going on in the phpBB world.

Return to the “Beer blog” main page


A new Modding Process: Part 1

by Ganon_Master on 20 Aug 2008, 21:09

Well, I always knew there was a blog here, but I have never written anything for it... So I will just do that now. :D In this series (of wich I do not know how long it will last), I will try out a way of MODding that is entirely new to me. The "managed" way of MODding.

In my years of phpBB MODding, I have always looked at creating MODs as a process. This is correct, you may say. But how do you interpret "process"? In my first few years of MODding I interpreted it different from how I do now. Back then, I created MODs something like this:

  1. I get an idea.
  2. I start editting code to get to this idea.
  3. Gather changes into a file.
  4. Test it once.
  5. Release to public.

This might make sense for small modifications, but it is said that it works a lot worse then the following structure:

  1. I get an idea.
  2. I write down the idea and the exact features that I want: what does this MOD do?
  3. I look at points of improvement or conflict and write the points down in a logical order.
  4. Start scripting according to that order.
  5. Gather changes into a file and check if something doesn't add up.
  6. Test the entire thing yourself.
  7. Does it do what you wrote down in step 2? If not, go back.
    Send to a select group of people for more testing.

If thumbs up from small testing group, release to public for more testing.
Why is the second structure better then the first? Downside is that it has more steps and takes more time. But what this technique has over the other is some sort of quality insurance. It makes sure that you will release a product that matches your idea. Also, it adds an extra step of testing to eliminate bugs. This is said to work well for small modifications (Simple Points System) as well as large modifications (Advanced Dungeons & Rabbits). For larger modifications it is more of a requirement. ADR is one of my best examples for this. Up untill now I have tried to do it using the first method, and as some people might know, failed miseraly. :P This is the reason I am prepared to try this way of MODding, and will try to keep you up to date with all my latest opinions and obersvations.

In the next post, I will show you how I wrote my project plan.

Comments

Yeah, for larger MODs it's inevitable that you plan your development process and use a version control system, such as SVN. Looking forward to seing more. :)
User avatar
eviL<3
24 Aug 2008, 18:58

Heh...what, though, do you do first? Design the DB schema (table-design and DB alterations) or the actual PHP?
User avatar
Obsidian
02 Sep 2008, 16:44

I am doing the database schema first. But before that, I want to make the "MOD Documentation" more specific. In this case MOD Documentation means practical things such as the features list, battle calculations, etc. I have most of it in my head, so writing things down should go fast enough.
User avatar
Ganon_Master
04 Sep 2008, 21:29

I would probably be a lot more productive if I did something like this, wrote down what I want to accomplish and prioritize things a bit.

*waits for part 2 ;) *
User avatar
Mr. Bond
12 Jan 2009, 02:07

Part 2? Bobby, shhhhh!

I was hoping to steal all the beer from this thing through a bendy-straw in the back before anyone noticed. How very dare you try to foil my plans. :o

*quickly glurps all the remaining beer before they come back* @.@
User avatar
House
12 Jan 2009, 17:03

thank you very much :)
almsamim
07 Apr 2009, 21:17