Advertisement
Guest User

Role Reversal Contest

a guest
Sep 27th, 2016
189
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.52 KB | None | 0 0
  1. I'm not sure if I'm in a position to be hosting a contest, but there's no harm in trying, right?
  2. [center][size=60pt]Role Reversal Contest[/size]
  3. [size=24pt]Hosted by EPICI
  4. [url=http://www.timeanddate.com/countdown/generic?iso=20161031T07&p0=250&font=cursive]Due: October 31st, 2016, 11:00PM UTC[/url]
  5. [url=https://docs.google.com/spreadsheets/d/1GCansiVxXHICyEaDpYk3qKORqYcQ1grnNKbIE4dsyOo/edit?usp=sharing]Sign up and stuff here[/url][/size]
  6. [size=8pt]My timezone is -4, so it would be 7PM on my clock
  7. Format is taken from recent LOCAA contests[/size][/center]
  8.  
  9. [size=24pt]In a Nutshell[/size]
  10. This contest is open to everyone.
  11. Did it ever seem unfair that the players can send barrages that the boss can't dodge, and the boss can only use pretty patterns to fight back? Or what about the hitboxes and the health difference?
  12. You pick a character that hasn't been taken/reserved and create both a player and a boss for that character, both sort of a cross between boss and player.
  13. You can submit multiple entries. However, you can only reserve one character at a time. Submit your first entry before reserving another character. Contestants on their first entry always get priority.
  14. Submitting multiple versions of the same entry is different. I will take the most recent one with the assumption that it is the best, unless you otherwise specify.
  15.  
  16. I plan to take all of the players and bosses and bundle them as a sort of mini-game. I will also add music and sound if there isn't any already. This will make it so people only have to download once. I will not take credit for any of it. If you do not want your entry to be included, please notify me. Alternatively put it under "Comments" in the [b][color=blue]g[/color][color=red]o[/color][color=yellow]o[/color][color=blue]g[/color][color=green]l[/color][color=red]e[/color][/b] Sheet.
  17.  
  18. [size=24pt]Specifics[/size]
  19. Use Danmakufu.
  20. Your script should contain everything it needs. If not, include all dependencies in the download.
  21. You probably already have your own custom system by now.
  22.  
  23. I am the only judge right now, however, if you want to be a judge/co-host ask politely.
  24. Scoring is primarily based on the following:
  25. [list]
  26. [li]Professionalism - Does it look like it was made by someone new to danmakufu or someone with lots of time and experience? I don't mind if there aren't original sprites, sounds, music, or anything else copyrighted. However, if there is something you should be capable of making, such as a custom system, I will look for it. This also includes minor stuff like sprite clipping, bugs no matter how minor, improper music looping, sloppy effects, bad dodging AI (scroll down), bad score mechanics or calculations, unreasonable lag, etc.[/li]
  27. [li]Recreation accuracy - To an extent this overrides the previous. How similar is your recreation to the original boss? I don't expect pixel perfection, but it should look like a duplicate of the original.There are three major exceptions. One is the timer, which can be modified to fit the 10 minute goal, but they should still be proportional to the original. The second is if the original boss was too weak you are allowed to buff it, within reason. If it is buffed ti should still look like the original, just harder. The third is if for the player you decide to make some or all parts of the attack(s) controlled by the player rather than scripted, within reason, you will not lose score.[/li]
  28. [li]Fun - A more minor and subjective factor. How much fun is it to play as and against that character? If the original boss fight was no fun, the recreation likely wouldn't be much better. However if both the player and boss are really good you'll probably get a good score anyways.[/li]
  29. [/list]
  30.  
  31. No plagiarism. Only use resources with permission.
  32. Download links to everyone else's scripts are public, however, you are not allowed to take anything, only look, unless they give you permission. You are allowed to give and receive help.
  33.  
  34. Not all characters can be used.
  35. You don't need approval from me if your character satisfies these two criteria:
  36. [list]
  37. [li]The game they appear in is a standard danmaku shooter in the Windows era, and in the main series.[/li]
  38. [li]They appear as a boss in Stage 4 or higher. So Extra and higher difficulties such as Phantasm count too.[/li]
  39. [/list]
  40. Otherwise, you can still take it but you aren't guaranteed acceptance. Please ask first. I am simply trying to keep the weaker bosses and less "main" characters out of this (ex. Suika's only boss appearances are in the fighting games, but she is considered a main character, and her attacks can be adapted and modified to work as danmaku).
  41. Once a character is reserved only the person who reserved it can use it. If you enter with the same character as someone else, whoever properly reserved it first will have a valid entry, everyone else will be turned down.
  42. Appearances in different games count as different characters. As far as I know no characters satisfy these conditions in two different games but in theory it makes it possible for multiple people to have the same character. It is still discouraged though.
  43.  
  44. The boss and the player should pretty much be mirror images.
  45. The player traits they should inherit are free movement, and a small hitbox.
  46. The boss traits they should inherit are the danmaku attacks. These should be based on lunatic difficulty if they are from the main story. No last words or last spells, unless the original boss had them (ex. Yuyuko, Kaguya).
  47. The length of the "boss fight" should be shortened or lengthened to be roughly 10 minutes. Try and match it as closely as possible. To be fair the player timer should be slightly longer than the boss timer. If there are last words or last spells they should be included in this timer.
  48. Also, player bullet damage should be set to 1. Health can be more to match the non-spell or spell card timer.
  49. This will ensure your script is compatible with everyone else's.
  50. Any shot sheet is fine. If you want to use mine ask politely.
  51.  
  52. How the player should work is each life starts with the corresponding non-spell. After a timer or a certain amount of damage taken, the player would automatically be killed.
  53. The player by default gets one "bomb" per life. This triggers the spell card with the appropriate timer and attack/effects. After a certain amount of time the spell card ends, the player would be killed anyways and forced onto the next life.
  54. If they don't bomb, they lose the opportunity to use that spell card. Death-bomb timer should be something reasonable. If you want you can create a copy/version with auto-bomb.
  55. Reverse spell card capture bonuses and other stuff are optional.
  56. If you use an internal counter to track the player "health" have a display in the player script, not in the system.
  57. For clarity's sake player bullets should be translucent. The exact alpha value is up to you.
  58. There aren't built in lasers for players, so if your custom player lasers are a bit sloppy, your score won't be deducted.
  59. The player can have extra custom controls for controlling the attacks and stuff, but they shouldn't be too complicated.
  60.  
  61. Bosses should use the standard spell card system and basically be a copy of the original boss.
  62. The timers will likely be different because you are aiming for a 10 minute long fight.
  63. The boss should also have a small hitbox, normal movement speed and die in one or a few hits.
  64. The boss should have some kind of dodging AI. If you need to use Common Data to assist the AI, I recommend you communicate with the other participants, however, you will only be scored on your character vs itself, so it's not mandatory. The AI doesn't need to be too advanced, if it can dodge most danmaku it's probably good enough. If you are using an learning/evolving/neuron network/node-based AI, it might be helpful to include a save-state. Again, not mandatory.
  65.  
  66. I have school to deal with, but I will try and keep the [b][color=blue]g[/color][color=red]o[/color][color=yellow]o[/color][color=blue]g[/color][color=green]l[/color][color=red]e[/color][/b] Sheet updated. When the contest ends I will post the scores and bundle download link here as soon as I can.
  67. In the interest of keeping things fun I request you point out any loopholes or flaws, and not abuse/exploit them.
  68. I know people don't like restrictions, but hey, I haven't seen anything like this in the past, I think it's new enough that it's fair.
  69. Any questions or comments go in this thread. Feel free to discuss anything related to the contest. I will try to check daily.
  70. There's tons of minor things, so I won't deal with them individually unless I have to. If you are unsure, talk to me.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement