- Joined
- Sep 6, 2013
- Messages
- 6,742
Hive Member
Create a warcraft hero, based on a hive member!
Let the Warcraft universe feel the power of The Hive and send our fellow brothers into the battle of storm, earth and fire. Shape a new son, give him the right looks and arm him with a unique spell to rule the battlefield for our good! Heed my call!
Theme Criteria:
The goal is to create a hero based on a hive user. Here are possible user associations that helps to define how the model, icons, and spell can look like:
|
Association
|
Example
|
Explanation
|
|
Avatar
| General Frank's avatar lets us associate him with a tank, possibly with a special shooting ability. | |
Name
|
Murlocologist
| Murlocologist could be interpreted as a murloc themed hero. |
Appearance
| Dr Super Good is actively promoting SC II, so I'm relating SC II with him. It would be possible to bring a SC II unit into the warcraft world to symbolize that. |
The technical criteria for the entry is:
- 1 Model
- 1 Spell
You may, but don't have to create one extra co-ability next to the main spell if it's required for your concept. In case a second ability is used, it's extend should be kept at a minimum, and it should exclusivly serve the main spell's effect, instead of only having some synergy.
- 3 Icons
- Hero Portrait
- Spell Icon (symbolizes the spell effect alone)
- Spell Icon (symbolizes the spell in usage of the hero, example Chain Lightning)
Two icons featuring the spell are regarded as two different variations/versions of one same spell. In fact they are representing two approaches to drawing the spell - abstract and figurative.
Copy pasting elements from one icon into another is not allowed, they need to be all drawn from bottom to top.
Team Criteria:
- Defining only yourself as team is not allowed.
A team is defined by 3 members, respectively responsible for: Model, Icons, Code - Work sharing inside a team is allowed. That means it's legitimate to share work, to make edits, and to support each other in what ever way.
There are general team rules, which have to be followed by everyone, and there are aspect-related rules, which are mostly only relevant for the 2D-, 3D-, Code expert respectively.
Team related rules:
- Submissions must follow the contest theme.
- Submissions must follow the General Resource Rules.
- Submissions may not be started / made before the official launch of the contest.
- The chosen hive user to create must have at least 100 forum posts. You can ask in thread for exceptions.
- Teamwork with non-team members is not allowed.
- Each team must post work in progress in the contest thread before the deadline. It should be made clear that the team works on each aspect (Model, Icons, Spell). 2 WIPs from each category is required!
- The final entry must be posted before the deadline in this thread using a demo/test map. The post should be a little presentation of the hero, and must link to all submitted components of the hero (link to Model, Icons, Spell in the resource section). The entry must contain a short explanation of the theme, naming the created hive member and it's theme association.
- The test map's name should be: <team> + "-" + <hero name> , and it must have decent testing conditions. Which means the user can test various aspects and behavior of the spell/code under certain conditions without too much of effort. For example cliffs/water/trees might be provided already in a spell demonstration, or chat commands might be given as well.
- Judges may not participate.
Model related rules:
|
|
|
Breaking any of these rules may lead to punishment in the judgement score, up to disqualification from the contest, depending on the weight of the issue.
In case of doubts towards a certain rule or the urge to discuss something related, you are very encouraged to post in the contest thread so others and judges may help with sorting it out.
- First Place: 100 reputation points + Special Rank Icon on the hive
- Second Place: 65 reputation points
- Third Place: 40 reputation points
- Remaining entries: 10 reputation points
- Judge: 10 reputation points
All winning teams will receive an award icon, representing the winning entry.
- @General Frank (Model)
- @The Panda (Icons)
- @Cokemonkey11 (Spell)
Mesh | How clean and well shaped is the mesh? Is it balanced and how well is the wrap made? | /10 |
Animations | How quality and smooth are the model's animations? How effective are they? How fitting are they? | /10 |
Texture | How effective is the texture? How well is it applied to mesh? How does it look aesthetically? Is it clean, understandable and logical? | /10 |
Concept | How creative and unique is the concept? Does it fit the chosen theme? | /10 |
Effects | Does model feature special effects like particle emitters or ribbons? How well do they contribute to overall quality of model? | /5 |
Mechanics | How well does the model works within in-game environment regarding its appearance, its filesize, does it feature sounds, does it feature necessary attachment points? | /5 |
| /50 |
Blizzard style | Is the style similar to standard icons? | /10 |
Concept | How qualitative is the concept, how unexpected and creative is the idea? Originality and uniqueness of icons are judged. How fitting are icons for model/spell? | /25 |
Technical note | Quality of: color, composition, expressiveness, shape, definition, sharpness, clarity, shading, realism, proportions, rendering, details, materials. | /65 |
| /100 |
<Here> is a more detailed explanation of what Cokemonkey does look for!
Coding | Is the skill bug- and leak-free? Does it support multiple instances? Is there a good documentation and are there enough configurable variables to fit the needs of different user? Does it cause performance issues upon effect? Is the code fitting for a decent spell submission, or is it too simple? | /20 |
Concept | Is it unique? How creatively was the idea executed and is it fitting the contest theme? | /10 |
Visuals | How does the whole spell procedure look? Is it overloaded with special effects? How explanatory is the tooltip/description of its functionality? | /10 |
| /40 |
Judgement score is defined like:
FinalScore = (30*PollVotes/POLL_VOTES_TOTAL) + (70*JudgeScore/100)
- Model: 40%
- Icon: 30%
- Code: 30%
- Judgement: 70%
- Poll: 30%
FinalScore = (30*PollVotes/POLL_VOTES_TOTAL) + (70*JudgeScore/100)
The contest shall begin on 10th November 2017 and conclude on 7th January 2018 GMT (day is included).
===============================================
Assigned Staff: @Murlocologist and @IcemanBo
The Poll | Results
