• Check out the relaunch of our general collection, with classic designs and new ones by our very own Pissog!

Process Guide Workshop for Create-A-Pokemon.

Status
Not open for further replies.
I disagree, art should be open as long as possible and if the art and base stats dont fit perfictly is not that much of a problem.

Also where can i find a bigger or more clear vertion of that timetable? I find it hard to read.

Art and Base Stats have pretty much nothing to do with each other. Style and Build are much more important.

I point you to the Pixies. I point you to Starters, I point you to starter birds. You look at Pidgeot's Dex and see it flies at Mach 2, then you see it gets outsped by Miltank. Dragonite can travel the world in a day. Salamence is faster than it, and Garchomp is faster than Mence.

Cloyster is a shellfish underwater every day and Aggron lives in a cave, yet Aggron has more special defense, despite them both having the same defense.

There's next to nothing to suggest Glalie has all 80 Base stats, and yet it does. Froslass seems to have lower defenses and HP, but somehow picked up speed, yet it just looks... weird.

Doing Art before Base Stats Just gives us more time to reflect on Art while we sort Base Stats out.

I can't do a direct link thanks to fat Angelfire, but I do have an upsized version of the Calendar: http://bkennedy86.angelfire.com/Deck_Knight_Stuff/Deck_Knight.html
 
Nice. What do you think of the shorten polls and force spillover idea? I think it would save time.
What exactly are the "features"?

Could you add a "pre-evo thread begins" bit on day 25? I think I/someone else can fit all the pre-evo info into one thread.
What do the rest of you think of this?
 
Nice. What do you think of the shorten polls and force spillover idea? I think it would save time.
What exactly are the "features"?

Could you add a "pre-evo thread begins" bit on day 25? I think I/someone else can fit all the pre-evo info into one thread.
What do the rest of you think of this?

Most of the shortened poll times are in there. As a matter of fact, my Calendar only has 26 days total per pokemon, with 28 for Topic Leader Selection and restart, the extra days are just for spillover whenever, but it maxes at 35 days. TBH I didn't want to be so rigid, but by the time I sat down to make the calendar, it just made sense and gave the time-consuming things (e.g. art) some leeway.

For instance, the calendar even includes spriting and coding time. I don't know how long it takes to code, I assumed 3 days, but obviously thats up to DJD or whoever. It isn't like he won't see it coming.

Etc. Features are the Height and Weight stuff. Its just a general outline, I don't want everything set in stone, but that is how the process would look like if we streamlined it to the maximum extent possible. It gets very hairy in the middle.
 
One more thing how would we do the "part of a trio" or "starter" "legidery" dicitions? I would recomend a poll at the start with those and "normal pokemon" as options, but I am not sure if many other people would agree. "new poke" and "evo of old poke" do not need to be chosen till after the type poll.
 
ok well if you want to live with the numerous complaints about the artwork looking too fast,not bulky, looking too much like a new evo or whatever else was rightfully picked up on in the mummy thread.

I don't see why everyne is so eager to get the art thread started so soon it wouldn't even increase the creation time if it came after
 
But they're pretty much only on things that have a very high chance of having spillover anyway. Other than the two stat ones, I could easily see all of the others almost having guaranteed spillover threads whether they were forced or not.

It's basically just taking some time off the initial polls for the spillovers that are highly likely to happen anyway.
And.....
true, but in realty those spillovers would happen anyway, my proposal would just shorten the first part of the poll to account for it.

I'm not questioning your reasoning over those spillover polls, I'm merely pointing out the fact that they're alot of them.

One more thing how would we do the "part of a trio" or "starter" "legendary" dictions? I would recommend a poll at the start with those and "normal pokemon" as options, but I am not sure if many other people would agree. "new poke" and "evo of old poke" do not need to be chosen till after the type poll.
Personally I think you could stick them in the new pokemon/evo discussion as well.
 
ok well if you want to live with the numerous complaints about the artwork looking too fast,not bulky, looking too much like a new evo or whatever else was rightfully picked up on in the mummy thread.

Heaven alive! How does something as cute and cuddly as Jirachi get 100 base stats in everything? Really, the artwork holds some connection with the base stats, but when it comes down to it, it's not really all that important. If you'd be able to connect Shuckle's artwork with those massive base defenses without knowing Shuckle, I applaud you.
 
Deck Knight, one of the things I noticed on that calendar was the Base Stat thing. It seems like there's two days of discussion on the base stats, one day of submitting spreads, and then the "overall stat spread" poll. Is it basically just removing the Base Stat Total poll in favor of a discussion, and kind of merging it with the Overall Stat Spread poll for more varied choices there?

Another was art time. Is 5 days enough time to get the art submissions in? I'm not sure since I'm not really an artist myself. I would say one day isn't enough time to vote on art, but it's likely to get a spillover poll anyway so that's fine.

On to the "Name" section of the calendar. Do we really need a day between Name discussion and Name submission? I'd say they should start on the same day, since there isn't too much to discuss without having any submissions.

Is there any reason for a day between Movepool Poll (which I assume is for debated things, such as the elemental punches and WoW on Revenankh, or is it more like "Here's 4 movepools, vote on which you like more"?) and Movepool Finalization? What would the finalization consist of, or is it basically just a compilation thread? If this was moved back to have finalization start when the poll ends, then the analysis could start a day earlier as well.

Other than those few points, I like it. Much easier to read and follow than the chart I had made up.
 
Deck Knight, one of the things I noticed on that calendar was the Base Stat thing. It seems like there's two days of discussion on the base stats, one day of submitting spreads, and then the "overall stat spread" poll. Is it basically just removing the Base Stat Total poll in favor of a discussion, and kind of merging it with the Overall Stat Spread poll for more varied choices there?

Another was art time. Is 5 days enough time to get the art submissions in? I'm not sure since I'm not really an artist myself. I would say one day isn't enough time to vote on art, but it's likely to get a spillover poll anyway so that's fine.

On to the "Name" section of the calendar. Do we really need a day between Name discussion and Name submission? I'd say they should start on the same day, since there isn't too much to discuss without having any submissions.

Is there any reason for a day between Movepool Poll (which I assume is for debated things, such as the elemental punches and WoW on Revenankh, or is it more like "Here's 4 movepools, vote on which you like more"?) and Movepool Finalization? What would the finalization consist of, or is it basically just a compilation thread? If this was moved back to have finalization start when the poll ends, then the analysis could start a day earlier as well.

Other than those few points, I like it. Much easier to read and follow than the chart I had made up.

The thing with the calendar is that while these are "official" benchmarks, nothing precludes anyone from thinking about what to design long before we get to Base Stats. Once they get Type the ideas start flying, and then Style and Build serves as a feedback mechanism.

A lot of the "Finalization" stuff is basically code for spillover days. Movepool Finalization is essentially just summing up the movepool after you have everything together (abilities, art, etc.) Essentially its a compilation thread, and then we do the etc. stuff, which are also compilation threads. By the time you get to the 4th week, you're pretty much done and know what the pokemon is like. The spillover days are there for the express purpose of more time. They're just put at the end because I am very lazy.

As for Movepool Discussion being so long, lots of people submit movepools and discuss flavor issues and try to balance it with ability. Movepool is easily the most contentious part of the process, so it has plenty of days to be worked over and mulled over. Art secelction really should be done before ability or movepool, so I've tried to maximize the amount of information artists have before officially starting, but again, this isn't going to be chiseled into a stone tablet, if you want to start the art thread earlier, go ahead.
 
"CAP 3, Smogon's Return"...okay in all seriousness "CAP 3, Part X" with X being normal numbers like 1, 4.5, 5 billion, etc.

GT I like this thread naming scheme you proposed earlier, with one of Dane's suggestions woven in. When you make the next set of threads please name them with the following format:

CAP 3 - Part X (Poll or discussion description)

So, I believe the first thread will be named:

CAP 3 - Part 1 (Main type)

If we follow the same convention for the entire project, it will be much easier to keep track of the threads.
 
Deck Knight, Dane, Time Mage, whoever....

Please collect all this stuff together and post it as one big post. I am planning on collecting several stickies together and making one "Create-A-Pokemon Information" thread. The top post of that thread will have and "index" to several other posts that contain CAP Project information. That way we won't have too many stickies, but we'll still have easy access to all the key project information. I want this process guide to be a part of that. But I need it gathered together in usable form. If you want to separate it into a couple of different posts that's fine too.
 
Deck Knight, Dane, Time Mage, whoever....

Please collect all this stuff together and post it as one big post. I am planning on collecting several stickies together and making one "Create-A-Pokemon Information" thread. The top post of that thread will have and "index" to several other posts that contain CAP Project information. That way we won't have too many stickies, but we'll still have easy access to all the key project information. I want this process guide to be a part of that. But I need it gathered together in usable form. If you want to separate it into a couple of different posts that's fine too.
Here you go.

Or a non embedded link: http://www.smogon.com/forums/showpost.php?p=1094077&postcount=96

It's the one I've been updating for a page or so, just updated to remove the timetables and added a link to Deck Knight's calendar, since it's much easier to follow overall than the timetable was.

One note though, you might have to hit refresh on Deck Knight's angelfire thing to get it to load.
 
If we decide that a new pokemon should be an evo, how will we decide from what to evolve it? Also, is this accounted for in the calendar?
 
That would have to be done in time for art to be made of it. I'd say it would just be a concurrent poll/thread based on available choices, and decide as soon as possible, but must be done by the time style and build are done.

I would normally say before those two start, but honestly looking at some of the evolutions (Scizor, Gallade, Magmortar, Electivire, etc), the stats and such only have to vaguely reference the pre-evolution.
 
So, can we consider this section done for the most part? I think we have debated mostly everything, and there seems to be a decent agreement on what's right now compiled on Dane's post. Nothing stops us from revising it later, of course.
 
Yea, can we please have a total collection post? I want to chime in with some suggestions but I have no idea what has already been decided on. Also, if I mention something that has been discussed, kindly link me to the appropriate post ^_^

Three immediate concerns for me are originality / creativity, Polling implementation processes, and new move implementations.

I'll discuss the first, as it is the most significant to me. I remember reading that Doug already said that we would work within the skeleton of Gamefreak's mechanics, so originality in that sense is discouraged. However, what are the checks in place to ensure "fanboy" type Pokemon aren't created? Since the polls are accumulations of popular votes, how will we prevent something like a Fire / Dragon or a Steel / Ghost with Levitate / Heatproof? Also, I see that polls decide if a Pokemon should be Offensive, Defensive or mixed...but what if we have continuous choices of Offensive Pokemon? I recognize that that would be popular choice, but it seems like the creativity factor would then be compromised, correct? I'd just like to have some feedback regarding how this vital factor will be prioritized in the future.

The next concern I have is the polling implementation process. It seems like an "initial" poll is held (for example, to decide the Pokemon's initial type), and then a few polls are held after this in case a majority isn't reached in the first poll. Without stringent restrictions, I could see how this would significantly slow down and muddle the process. It seems like, to me anyway, that the CaP Project's allure is its momentum and its active participation from the community, so slowing it down would be obviously detrimental. I might suggestion something like, "initial" polls are held for a designated period of time, say 2 or 3 days, and "confirmation" polls are only held for 24 hours or something like that, and there is a limited amount of confirmation polls. This might be happening already in terms of application, but I would like to see it "legislated."

The third is new move implementation...are we going to bother with this? Syclant had a new ability, but I haven't seen many moves towards new moves. Is this a possiblity?
 
Everything collected so far is in the link in my sig.

There aren't any fanboy checks in place, but hopefully there are enough sane minded people to prevent Fire/Dragons with Sacred Fire, etc.

Well, people alternate on opinions. First we had offensive, then mixed, and now who knows what we'll end up with.

See the calendar in my sig for the basic schedule. Spillover threads only last a day, so that they don't kill momentum.

Moves and Abilities are discussed in their threads, and whether something gets a new ability/move is based on the Pokemon itself, though making new ones aren't something done lightly.
 
An Expectation Problem

I am afraid that the current order, of going from the base of type through job, stats, and moves and abilities, while intuitive, is flawed. I am going to divide posters into two categories. Voters and Contributors.

Voters primarily participate in polls in the Create-A-Pokemon project.

Contributors add choices to polls where every individual cannot create a concept. These are limited to movepools, stat arrangements, and art design.

Optimally, contributors will realize the voters' goals, but this is not always the case. Consider this theoretical scenario:

The voters decide for a sunnybeaming special sweeper as their pokemon's job. However, most of the voters want chlorophyll as an ability. The contributors make a pokemon with a speed stat of over 100, and it is voted for. Chlorophyll is then overpowered on the pokemon, and the voters feel cheated. This could also happen with subseeding, (not in the list of jobs) HP (bad consideration of leech seed) , physical movepool, and many other things. And it happened to Syclant when megahorn was deemed to powerful on it.

There needs to be a mechanism to ensure that voter's expectations are not accidently undone. Therefore I propose 3 new polls:

A think tank topic for voters to bounce ideas around.

Two checklist polls, one asking which proposed features are wanted, and which features aren't wanted

These polls would make sure that artists, stat writers, and movepool writers dont accidently fail to address community goals. These topics would be instituted at the end of the second type poll, when ideas are probably the freshest for the new pokemon.

The early schedule would then be something like this

TYPE
SECONDARY TYPE
GROUP BRAINSTORM
(continues through)
BASE STATS LEVEL (because they are less effected by the brainstorm than job)
JOB POLLS
ART DESIGN (continues through)
STAT DISTRIBUTION
MOVE DISTRIBUTION
ART POLLS
ABILITY
FINAL DETAILS

SPRITE POLLS

DONT THINK WE CANT STILL DO THIS! THE TYPE POLL HASNT ENDED! WE CAN TRY THIS AND NOT SUFFER ANY MISUNDERSTANDING.
 
Not a bad idea. However, it starts from a wrong premise: The premise that people have agreed on some role before the role has been decided. If you vote for Fire/Grass, you'll get a Fire/Grass, and no more, no less. You are not voting for a Fire/Grass with 60 Speed for Clorophile, or a Fire/Grass with 40 HP for subseeding. Those are maybe the reasons you wanted to vote that type, but the process has a series of steps that will later determine what can and what can't that pokémon do with the specified typing.
 
I am afraid that the current order, of going from the base of type through job, stats, and moves and abilities, while intuitive, is flawed. I am going to divide posters into two categories. Voters and Contributors.

Voters primarily participate in polls in the Create-A-Pokemon project.

Contributors add choices to polls where every individual cannot create a concept. These are limited to movepools, stat arrangements, and art design.

Optimally, contributors will realize the voters' goals, but this is not always the case. Consider this theoretical scenario:

The voters decide for a sunnybeaming special sweeper as their pokemon's job. However, most of the voters want chlorophyll as an ability. The contributors make a pokemon with a speed stat of over 100, and it is voted for. Chlorophyll is then overpowered on the pokemon, and the voters feel cheated. This could also happen with subseeding, (not in the list of jobs) HP (bad consideration of leech seed) , physical movepool, and many other things. And it happened to Syclant when megahorn was deemed to powerful on it.

There needs to be a mechanism to ensure that voter's expectations are not accidently undone. Therefore I propose 3 new polls:

A think tank topic for voters to bounce ideas around.

Two checklist polls, one asking which proposed features are wanted, and which features aren't wanted

These polls would make sure that artists, stat writers, and movepool writers dont accidently fail to address community goals. These topics would be instituted at the end of the second type poll, when ideas are probably the freshest for the new pokemon.

The early schedule would then be something like this

TYPE
SECONDARY TYPE
GROUP BRAINSTORM
(continues through)
BASE STATS LEVEL (because they are less effected by the brainstorm than job)
JOB POLLS
ART DESIGN (continues through)
STAT DISTRIBUTION
MOVE DISTRIBUTION
ART POLLS
ABILITY
FINAL DETAILS

SPRITE POLLS

DONT THINK WE CANT STILL DO THIS! THE TYPE POLL HASNT ENDED! WE CAN TRY THIS AND NOT SUFFER ANY MISUNDERSTANDING.

I think that the artwork and visual concept should be chosen for the Pokemon before the stats and the moves. Because depending on what type of monster it ends up being by body type, etc, that will also be able to better justify what stats and move pool it should have.
 
Not a bad idea. However, it starts from a wrong premise: The premise that people have agreed on some role before the role has been decided. If you vote for Fire/Grass, you'll get a Fire/Grass, and no more, no less. You are not voting for a Fire/Grass with 60 Speed for Clorophile, or a Fire/Grass with 40 HP for subseeding. Those are maybe the reasons you wanted to vote that type, but the process has a series of steps that will later determine what can and what can't that pokémon do with the specified typing.

First, I am very afraid of what a Clorophile is.

Second, people have voted for early polls with later concepts in mind, like Sylcant, who was bug PRIMARILY because of a want of STAB megahorn on a pokemon not named Heracross. The concept of another megahorn user is likely what made bug/ice a success in the first round of voting, but his attack stat with STAB megahorn was considered overpowered, which made many people feel cheated.

Yes, if you vote fire/grass, you get fire/grass. But the person who voted for it usually had an intent for the end result.

These topics would not be here to design the pokemon before it is finished; it would be so that when the contributors submit base stat designs, movepools etc. even though they know it is supposed to be a, say, mixed sweeper, the can approximate what moves and abilities are going to be wanted. So instead of having a post 100 speed stat, too fast for chlorophyll, it might have a 75 or 80 base stat.

Regardless, it should help ensure that the intent of the voters goes along with the votes. Its not an extra design topic, more like a check or balance, a barometer of how closely the output reflects the input.

Honestly, with all of this early talk about sunnybeaming and chlorophyll and subseeding, I think that having a checklist of what Stats and movepools must consider will be especially important in this CAP 3.


@ Aki- Hmm... Art is really flexible in its position, though I would prefer that people only start submitting art when there is at least some community consensus on what the final product should and should not be able to do. I am fine with Art being at the same spot as brainstorm though, Its really up to Doug and Gothic Togekiss.

EDIT:

@ Time Mage: Final thought: I see what you're saying, but we really can't stop people from getting ahead of themselves when voting. Look what happened at the tangent on CAP 3 pt. 2 that both you and I participated in.
 
As a result of the ruckus I caused by warning people about off-topic posts, I've been thinking about what constitutes an off-topic discussion. There's nothing wrong with mentioning ideas that are part of future polls. Heck, it's a requirement in most of the early polls in the project. How else can you support your type choice, without mentioning things that are part of later polls?
"I like Grass/Fire because I like those types."
That's a crappy discussion post. Yawn...
"I like Grass/Fire because I can envision it with Chlorophyll and Subseed support moves. It would look cool if we could make it look like a blazing Sunflower. Heck maybe even make it a Sunflora evo!"
That's a decent discussion post, even though it touches upon topics that will be covered in four different polls later on in the process. That is not an off-topic post.

But, if the next 20 posters spin off on a tangent about the viability of Chlorophyll with Subseed on the same pokemon -- that's off-topic. Since the point of the thread is not to discuss the ability and the movelist. We are supposed to discuss the typing.

This is obviously a gray definition and must be administered with good judgment. I think "off-topic -ness" is determined by two factors -- Momentum and/or Specificity of the posts.

Momentum is determined by the number of posts that are centered on the off-topic concept. That's pretty easy to judge. When a few people start going back and forth on an off-topic concept, it drags the rest of the thread with them. Next thing you know everyone is talking about the off-topic concept, and they may create the perception that the "conclusions" they reach are in some way binding to the project as a whole. The discussion participants themselves may be fully aware that their conclusions are meaningless until the actual poll is conducted. But all of these threads have many more lurkers than posters. All those lurkers may get a very different impression of the meaning of off-topic "decisions". Even more so, if they are new to the project.

Specificity refers to how general the off-topic concept is presented.

For example, if someone mentions Subseed with Sunny Day as an interesting move combo. Those are specific moves, but it's presented in a general context. If someone decides to "support their argument" by posting a complete level-up moveset, with egg moves and TM's -- that's bullshit. No one needs to get that specific to back up their argument.

Another example, if someone mentions that a pokemon should have something like 110 Special Attack and 102 speed to beat all the base 100's. Those are specific numbers, but they are used in general terms. If someone presents a full BST spread with justification as to where the pokemon should fit in the overall BST tiering list -- there's no reason for that in a typing poll.

I don't think there is a way to write rules for determining when a thread has gone off-topic. Nor do I want to stifle people's enthusiasm and discourage lively discussion. The point of the project is to discuss things.

I think we should probably mention somewhere that off-topic information is inevitable in all the CAP discussions. However, if an entire thread veers into specific debate about off-topic concepts -- then the discussion will be moderated. This isn't a CAP project rule, this a rule of every moderated forum in existence. But, for some reason, people were surprised when I moderated the secondary typing poll. I think some people thought, "What's wrong with having a long detailed discussion about BST's in the typing poll?" So maybe we need to make this rule clearer in our process guide. Also, a short summary of the rule should be added to the forum rules. Since the existing rule was written primarily to discourage people from making new pokemon threads.

I know some people disagree with me on this. So I want to throw it out for debate here in a thread dedicated to discussing the CAP process, rather than discussing it in detail in the polling threads -- which, ironically, would be an off-topic discussion in itself. ;-)
 
We spent two weeks and 160 posts figuring out this set up. Polls for the third CAP have only been open for three days and people already want to change it. We must not do that. If we change the system now, there is nothing to stop us from just rewriting the rest of it too. The brainstorming we already did in this topic will just be a load of bureaucratic waffle that delayed us from starting the third project, and no one will be able to take the project seriously if we change the rules at the drop of a hat. Imagine if in the middle of a battle someone wanted to revoke sleep clause.

Also, it has only been three days. We need to see how things will turn out. We don't know what will ultimately happen. With more regulation of discussion, this frenzy of assumptions and misunderstandings might smooth over.
 
First, I am very afraid of what a Clorophile is.
...
I meant "Clorophyll". At times like this is when I realize I have a long journey ahead in making my English good.


Anyway, what Doug says seems reasonable. As long as the discussion doesn't derail from the main topic much, it's cool to illustrate your decisions with examples that would correspond to later parts of the project.
 
Status
Not open for further replies.
Back
Top