Suggestion Fluff

[Schwi Dola]

I tried to quote Omni but phone kinda wonky.

Anyway I suggest having two descriptions of a move in move approval. One can be just fluff and the other can be cut and dry mechanics. This may help move approval go through faster by making it easy to parse what the person asking for is fluff or not.

[Trixie]

I tried to quote Omni but phone kinda wonky.

Anyway I suggest having two descriptions of a move in move approval. One can be just fluff and the other can be cut and dry mechanics. This may help move approval go through faster by making it easy to parse what the person asking for is fluff or not.

Why do you need the fluff to have it approved?

[Oleander]

I totally agree with this... I'm 110% for this. XD I wouldn't mind using the spoiler boxes beneath the fodder version for specific details.

Move Title [Price]
Big, fluffy text of beautiful details...
[spoiler]
Range:
Damage Dealt/Blocked:
Speed:
Fatigue:
Charge up:


Legit just the bare bones to judge balance. No minced words.[/spoiler]



edit; Don't need the fluff to be approved, but toss it in and mods can just skim and move on to the stats.

[Trixie]

Why can't you just post cut and dry mechanics in the move approval thread and then fluff it up in your roster?

[Oleander]

If you have an unapproved change between approval and roster it could change how the move is interpreted and leave out vital components.

Another option is to fodder it on the roster, then have all the move mechanics in a single spoiler at the bottom, tucked out of the way.... Again, the mechanical aspect is already there, we're nto adding anything new, we're just kind of narrowing the margin for human error in interpretation.



Palm Shields [300]
These small round shields float just above the palms. They are light, small and easy to maneuver - at the cost of their durability. Palm Shields deflect force instead of absorb it, meaning with the right amount of skill in the proper situation they can deflect an unwitting target's attack right back at them - so long as the attack can't just bypass the shield!

Like all of Stein's charging spells, it begins as a small orb. For Palm Shields, he only has to use one hand and mild concentration for a few seconds. Upon completion, the orb shatters and reforms into the Palm Shield, hovering in position. When the shield breaks, it shatters like glass, the fragments breaking down into glittery dust before vanishing.

[spoiler]
Shield/Defensive move
Charge up: 3 seconds
Focus: Mild
Fatigue: Mild
Durability: Medium-low
Features: deflects attacks, light weight and mobile
[/spoiler]

[Okor]

You can't separate the two. They're both essential to writing the move, in my opinion. I need to know both what a move looks like and how long it'll take to reach my face when I'm writing.

[Oleander]

You can still put details into the fluff, the mechanics just help "quick check" for balance, and allow for reference at a glance. Fluff would be what it looks like and maybe an instance in how it might be used. Maybe even fodder behind the move (though this could be added post approval.)

[Trixie]

Yes, but what you just wrote for that 300 OM move is fine. That's not a wall of text assaulting my eyes. As for your original concern about there being confusion between the roster version and the approved version; If you're adding a move to your roster before it's approved and purchased in your log, you're breaking the rules.

EDIT: You guys seem to be misunderstanding what we're having a problem with. We don't have a problem with fluff. We have a problem when you write 400+ words of it for a simple move.

[Harlan Higgs]

I totally agree with this... I'm 110% for this. XD I wouldn't mind using the spoiler boxes beneath the fodder version for specific details.

Move Title [Price]
Big, fluffy text of beautiful details...
[spoiler]
Range:
Damage Dealt/Blocked:
Speed:
Fatigue:
Charge up:


Legit just the bare bones to judge balance. No minced words.[/spoiler]



edit; Don't need the fluff to be approved, but toss it in and mods can just skim and move on to the stats.

STOP. TRYING. TO. GAMIFY. STUFF.

[Dane Regan]

@Stein: I see what you're saying. Ebony's Elemental Blast move has a quick summary at the top, for example. I also added another quick summary dedicated to the descriptions and appearance of the spell variants.

Having a small block like that for quick checking in moves is probably useful. And if someone wants to do that, they can.

There's no rule against it. But it shouldn't become mandatory in my opinion - not that you were suggesting that.

Just make sure that all the mechanics are also in the move description. In other words, that the spoiler is a quick summary of the move, not an extension to it.

[Oleander]

I meant the way you "fluff" the mechanics need to be approved as I've seen a few of my moves contain all the required info, but be misinterpreted because the way I wrote it was not easy to understand for others - even though I had no issues with it. Fodder (how yo got the move, what the name means, etc) is nonrelevant and can be added later.

Also, that example was not written by me, my sister helped reword my Palm Shield to make it easier to interpret. XD Mine is a bit more... convoluted.

[Oleander]

Didn't see Harlan's post...

I'm not trying to gamify, I'm trying to find a way to translate what I write into a simpler version that everyone else can still understand what I'm trying to get at. I have an issue with jumbled complex explanations. I wasn't suggesting this be a manditory change, I'm saying it could help people understand my OCD/ADHD.

It might not need to be like this through move approvals, but I know it would help me get my point across in the Workshop to help with rewrites. You can call it gamify if you want, but its how I think, and I need help translating.

[Dane Regan]

In other words, I agree with Okor. But there's nothing to stop you adding a quick mechanical summary to the bottom of the move.

[Oleander]

It was never a matter of seperating them, it was more of the second part being a streamlined "this is what I want" summery to help the fluffed version be understandable. I like this idea and I fully support it for the above reasons, though I believe it'd probably be better used for the Workshop than actual Move Approvals. Turns potentially complex moves into simplified by having others help you with wording.

[Trixie]

It was never a matter of seperating them, it was more of the second part being a streamlined "this is what I want" summery to help the fluffed version be understandable. I like this idea and I fully support it for the above reasons, though I believe it'd probably be better used for the Workshop than actual Move Approvals. Turns potentially complex moves into simplified by having others help you with wording.

There is literally nothing stopping you from doing this already. If it helps you convey what you're thinking then do it. Just keep the move description to a nominal length for ease of approval.

[Oleander]

I know, but I didn't really think of it till Schwi's suggestion.

[Omni]

You can just add fluff about a move or other stuff about your character in your roster. That's what the roster is for. Add fluff details under the actual move description, so people skimming (say, against your character in a fight) can just get the quick jist.

/thread