Magikarp Code Spoiler http://pastebin.com/raw.php?i=p7mQ1iYv Hello everyone! Yes, it is finally here: Magikarp! If you remember, I adopted this a few months back. Unfortunately for me, the theme, and everyone else, I became very busy and couldn't really work on it. However, I was able to manage some time for myself and was able to finish this! I tried to keep it as simple as possible, so I didn't add too much. I mostly focused on balance and fixing up some stuff, as well as working on the spawn. I did add ONE thing (I hope Meowmix doesn't kill me for this) mainly for the sake of balance in earlier games. Here is a very short list of the roles: Magikarp: Can splash someone during the night and dies if he splashes a Gyarados. Shiny Magikarp: Can splash someone during the day, and dies if he splashes a Gyarados. Gyarados: Can kill one person during the night (shared). Bombs fisherman daykills and revenges Shiny Magikarp splashes. Fisherman: Vote of 2, can kill one person during the day and another with a 50% chance of revealing himself. But first, if you are unfamiliar with this theme, take a look at this strategic and overall goal of the theme guide: Spoiler First off, we have our village, the Magikarp. The Magikarp are essentially villagers with the ability to /splash someone during the night. This splash command is basically a distract command which is ignored by everybody. If the Magikarp splashes a Gyarados, the Gyarados will kill that Magikarp. Now you may be thinking, "What's the point of splashing? If I don't splash then I have a higher chance of surviving." Well, that second part is technically true, but splashing can actually be helpful. For example, let's say we have Player A and Player B. Player A is a Magikarp and Player B is a Gyarados. Player A decides to splash Player B. After the night ends, Player A will die due to splashing a Gyarados. People will now begin to suspect that Player B is a Gyarados, because Player A died after splashing Player B. If you tell people who you are splashing and you splash a Gyarados, then they will know who the Gyarados is. Risky, but effective. Also, if you happen to splash someone and you don't die, then that person is most likely a Magikarp themselves, so you can effectively clean Magikarp as well! Spoiler The main goal of the Gyarados, like any other mafia, is to get rid of the village. Gyarados has his generic kill (shared with his team) to get rid of the villagers. However, Gyarados also has to use tactics of deception, bluffing, and framing in order to fully achieve his goal. Framing is probably one of his best tactics to use. If someone says "I'm gonna splash Player C (who is a Magikarp)," then Gyarados could kill whoever is splashing Player C to make that person look bad. If someone splashes a Gyarados, the Gyarados could try to protect himself by saying "I was framed!" Another thing Gyarados could do is pretend to splash someone. A Gyarados could pretend to splash his own partner, so when people see that he doesn't die after "splashing" his partner, his partner will be "cleaned". This is a very effective tactic to use, but smart players may be able to sniff out a pair of Gyarados trying to protect each other. The Fisherman is an interesting role. When a game first begins, he will first come off as very weak and underpowered. However, the Fisherman has a tactic which can be very effective: blending in. If someone splashes the Fisherman, nothing will happen. This could mark him as "clean" amongst the Magikarp village. Fisherman does not become a real threat until later on. When players start to die off, his vote of 2 can become very effective. His daykills are mainly used to keep the Magikarp in check, but using his daykill is quite risky since Gyarados can bomb him. Essentially, the best thing for the Fisherman to do would be blending in and waiting until only a few players remain. The Shiny Magikarp is a new role which is sided with the village of Magikarps. Shiny Magikarp is basically like any other Magikarp who can splash, but, unlike normal Magikarp, the Shiny Magikarp has the ability to splash during the day! It's essentially the same thing: if it splashes a Magikarp or the Fisherman, nothing happens, but if it splashes a Gyarados, it dies! However, the thing that makes Shiny Magikarp really useful is the fact that his splashes are public. For example, let's say Shiny Magikarp splashes Player A, who is a Magikarp. Everybody in the entire game will get the message, "Shiny Magikarp splashed Player A. But nothing happened!" At this point, Player A will be confirmed not to be a Gyarados. This, however, isn't full proof, because he could possibly be the Fisherman. If the Shiny Magikarp splashes a Gyarados, then Shiny Magikarp will die, and unfortunately, nobody will know who he splashed. Shiny Magikarp can't claim safely due to the fact that Gyarados could easily kill him. This means that while Shiny Magikarp is a very useful way of finding clean Magikarps, it isn't completely full proof, which requires the Magikarp to continue risking their own lives of finding a Gyarados. (idk how to fix that double spoiler thing but it's annoying) Yes, I know, that is rather lengthy, but this theme is very strategical, despite being very simple. The guide above will kinda tell you what's going on, and what you can do to help your team win. Here is a short list of everything that I added/removed/changed in the theme: - Gyarados now share a kill. - Fixed a strange glitch which was making bluffing a difficult thing for Gyarados to do. - Added a tips section. - Added prevent teamvote and teamtalk for Gyarados. - Gyarados now bombs Fisherman daykills instead of revenging him. - I did the unthinkable...I added a new role. :x Here is the spawn list: Spoiler "bgyara", "karp", "karp", "karp", "karp", "karp", "karp", "karp", "karp", "karp", "bgyara", "karp", "fisher", "bgyara", "skarp", "karp", "karp", "karp", "bgyara", "karp", "karp", "karp", "karp", "bgyara", "karp", "karp", "karp", "bgyara", "karp", "karp", "karp", "karp", "bgyara", "karp", "karp", "karp", "bgyara", "karp", "karp" So, of course, no theme can go without some concerns: -I am very concerned about the spawn list. Very, very worried. I don't know how it will play out, at all. And the worst part is that the way for me to truly know is for me to see the theme in action. -I'm worried about the Fisherman being underpowered in larger games. I might end up buffing his vote by a little. -I'm worried that the Shiny Magikarp may prove to be too beneficial towards the village in smaller games, but I'll have to see. -I'm worried about Gyarados being underpowered in smaller games, since he's alone until 11 players. Anyways, thanks for reading, and happy reviewing! (Also special thanks to RiceKirby for helping me with the mistakes I made in the coding.)
I know, I noticed it right after I had submitted the thread, should be fixed. (I think) Unless, for whatever reason, it still appears as private for you. (I don't think it is, since I'm able to view it even when I'm logged out from my pastebin account.) I think my internet was lagging or something and so it took a while for the thread to be updated with the correct pastebin.
Bug found (or more like, a Mafia Script limitation): Apparently it's not possible to use mode.poisonattacker with a poison that kills at the same night. This is a limitation specific to poisonattacker, other kinds of poison can be insta-kill, but not this one. It may still be possible to achieve what you need with copy: have the /splash a combo distract + copy command, then if target is Gyarados the Magikarp will convert into a role with initialCondition.poison that kills at the same night.
Spoiler: Review #1 Cohesion- There's very little to say for Cohesion in a theme with 4 roles. The elements work together well. Magikarp, Gyarados, and Fisherman are a common trio in the Pokémon games. Shiny Magikarp is an acceptable addition. If anything, I'd suggest adding a new role (Shiny Gyarados) for consistency's sake. 5/5 Creativity- Well it isn't a terribly groundbreaking premise, but internal family conflicts will pass for a TV show at least. The flavor is good. The mechanics are unique and original. 5/5 Craftsmanship (Balance, Tactics)- The balance is extremely questionable. The mechanics of the game do not lend themselves to a game where every side has an equal chance of winning. Many things are decided the first night. If multiple Magikarps are killed in a single night, then every Magikarp that died hit a Gyarados. The village can use this information to end the game extremely quickly. On the other hand, the game can end prematurely with the Gyarados winning because of bad splash coordination causing too many Magikarp to die in a single night. This is the most difficult aspect of the theme to develop. It will take more than spawn adjustments to balance it out. 1/5 Course (Learning Curve, Flow)- The roles and rules are simple. That's a large part of the appeal of the theme. However, the pace is quite suspect; as mentioned above, multiple Magikarps can die in a night, suddenly ending the game without giving them a chance, or on the other hand, all the Gyarados might be ousted in a single night because of multiple Magikarps dying on different players. This could be fixed with some advanced coding. 3/5 Concept- It's fun because it's simple, and it's also problematic because its simplicity jeopardizes the flow of gameplay. If you can manage to preserve the straightforward, playful nature of the theme while dealing with balance concerns, it will be a very successful adaptation. 4/5 Total: 18/25 A suggestion I have for addressing balance issues is giving each Gyarados an individual kill, but limiting the amount of Magikarps that can die on a single Gyarados to 1. This would standardize the amount of kills per night and make the village have to think about frames and mind-games more.
So, now that I have Mario in review, I think I'm gonna put this on hold. I will come back to it eventually, but I want to focus on Mario for the time being. Requesting lock.