Rule Sheet Development Process (Group 11)

 Rule Sheet Development Process (Group 11)

Dinosaurs and logic are certainly two topics that are quite random. But, our group was able to come up with an idea very quickly (even if it was only just the one.) I came up with the idea of putting together bones to make a skeleton, as that is one of the first things you think about when you think of the theme “dinosaur.”


Here is how the game works. Essentially, you play cards to the field in order to make a skeleton. Getting a skeleton allows you to either gain points from all the cards you’ve played (and move to the next round), or continue the round for a chance to gain double points when getting another skeleton.



(These pictures don't show all of the rules, but this is the gist of it.)


In the beginning, we were planning to make multiple sets of skeletons to create, and those sets would be different amounts of points. But I can not photoshop that quickly, and so the idea was scrapped. In the very first version of our rulesheet (before we turned it in), my teammate decided to ditch the skeleton idea, but I really wanted the skeleton, so I added it back in and then added in the double down rule so cards would get reshuffled into the deck.


There were also a few other things I tweaked in the rule sheet. For example, I saw that arm bones were missing, so I added that in. I also tweaked the points that every card was worth so it would make sense. Earlier, since the skeleton wasn’t required, it acted as an easy point increaser, and it increased points by 1.5x. I figured that players most likely find that difficult to do in their heads, so making it 2x is much easier. And of course, I added in the explanatory pictures. To be honest, I feel like they fall flat near the end.


And finally, I created a playingcards.io room for playtesting. It was a really grueling effort, because it was irregularly difficult to find good pictures of all the bones. They look fine in the pictures on the rulesheet because I’ve edited them, but the playingcards.io room just has the raw pictures. The next grueling part was figuring out how many cards there should be in the deck. There are a total of 95 cards in the deck. The cards are in order of most rare to most common: skull, back bone, tail bone, arm bone, and leg bone. There are also dirt cards in the deck to serve as duds so you have to sacrifice cards. That part was a lovely idea thought up by my teammate!


If you’d like to access the room, here is the link! (You can also find it in the rulesheet.): https://playingcards.io/acrxbt

Comments

Post a Comment

Popular posts from this blog

Aftershock Simulator - Sprint 16

Image
  On sprint 16 in Aftershock Simulator, I assigned the team 87 points and 51 points were finished. We’re beginning to pick up now that we have a plan on what to do. In this sprint, our team started on the tutorial levels and the objectives system. And of course, there was some extra work to do for the UI in the game as well.   As a producer, I still find it difficult to gauge the difficulty of a task, especially when it comes to programming. I still end up needing to change the point values of some cards because they end up more difficult than expected. For example, I had figured that creating the basis for the objectives system wouldn’t have been too difficult, but not necessarily. A few of the objectives require you to click certain UI elements on the screen, and the things that would “listen” to those UI elements are all each in their own separate scripts, so now there’s the added work of finding them and knowing where to put the code. I always end up asking people if t...
Read more

2D MegaMan Level 2 Feedback (10/27/21)

     Making a late-game type level is incredibly difficult. I had my idea of making the player climb up, but I wasn’t really able to implement that. I couldn’t really think of a layout for a room that wasn’t having the player zigzag up the room. Although, according to my playtesters, what was in the level was pretty good. At least I was able to avoid the “no clear way to the exit” problem I had with my tutorial level. It was a simple “gather the keys to unlock the exit” type level, and unlike my tutorial level, there was actually a point to it.      Players generally praised the way I set up my keys, as you need two keys to unlock the exit, but there are 3 in total. You can get the first key through an easy or hard route, and then you have to get the second key by passing through some enemies. When getting the second key, I put in a weapon deleter that takes out the Nado so you have to jump through a bunch of enemies to get to the top of the room. There’s a...
Read more

Chicken Scramble - Sprint 1

Image
  To start off, this first sprint was kind of disorderly. Since we’re using a completely new project management tool with no prior experience, it took some time to get used to (and still getting used to it). I suppose for my other teammates it wasn’t a big deal but it was an added pound of stress to my shoulders as the producer. To add to that, there was some confusion between me and the designer as to what the whole game idea and aesthetic was. My original idea for the game was a multiplayer maze in which the goal was for two players to compete to get to the other side of the maze. We could have ways for the players to mess around with each other, like using door switches to open and close doors. To clear up the confusion on what we were building, we set up a meeting to talk about it. To prepare, I made a design map of what I thought it should look like. (In the picture, the blue dots are door switches, yellow dots are checkpoints, and the red dot is where the enemy spawns. Bl...
Read more