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

Data ASB Feedback & Game Issues Thread (New Proposal Handling System in OP)

Status
Not open for further replies.
Double post b/c I'm a baaaad man.

Why do we keep threads like Battle Tower MkI, Arcade signups MkI, etc that are closed; in the Network Center? All they do is take up space. We should set them adrift on an iceberg a la referee training grounds with links in the new threads in case anyone wants to go back and look at w/e. I see the point in keeping things like Gym threatlist that are still a handy reference, but I see no point in keeping Battle Tower MkI in the Network Center.

Also, alternative Iron Barbs proposal:
Current Iron Barbs said:
Iron Barbs
Type: Innate

When struck with a contact attack, this Pokemon’s abrasive skin causes pain to the opponent, doing 25% of the damage it received to the opponent.

Pokemon with this ability: Ferroseed, Ferrothorn.
Current Rough Skin said:
Rough Skin
Type: Innate

When struck with a contact attack, this Pokemon’s abrasive skin causes pain to the opponent, dealing 25% of the damage received to the opponent.

Pokemon with this ability: Carvanha, Sharpedo, Gible, Gabite, Garchomp, Druddigon.
New Iron Barbs said:
Iron Barbs
Type: Innate

When struck with a contact move, this Pokémon's spiny shell causes pain to the opponent, dealing three (3) damage to the opponent (flat).

Pokémon with this ability: Ferroseed, Ferrothorn
New Rough Skin said:
Rough Skin
Type: Innate

When struck with a contact move, this Pokémon's abrasive skin causes pain to the opponent, dealing three (3) damage to the opponent (flat).

Pokemon with this ability: Carvanha, Sharpedo, Gible, Gabite, Garchomp, Druddigon.

Proposed changes:
Added recoil became flat damage
Minor flavor for Iron Barbs (not relevant whatsoever)
 
Same thing dogfish said

No support/ no Discussion

Can you just count that as a no support, no doscussion vote on any proposed Iron Barbs/Rough Skin proposal? I still think nothing is wrong with them.
 
What if we just don't change it at all, because there's nothing wrong with it?

No support, no discussion
 
[13:54:08] <akela> random idea for those that wish to change Iron Barbs and Rough Skin: Have it be 25% of the BAP of the move used, instead of some kind of fixed damage.

I don't think there is anything wrong with Iron Barbs/Rough Skin per se, but something like this is an interesting idea, because what Simon brought up about how Fire Punch returns less recoil than Ice Punch on a Druddigon does seem silly to me. It does fail to account for things like Counter and Bide, but it's a good starting point. It could also be a different %, like 50%, 75%, 69.696969696969%, 0.01%, or whatever people find reasonable.
 
I don't think there's a way to change Iron Barbs / Rough Skin without it being either nerfed against SE attacks or overpowered against regular ones, for reference most contact SE attacks right now do around 6 dmg back every time you get attacked, this being mainly Fighting attacks and the Elemental Punches
 
Static

I proposed this on IRC, and it gained considerable support. Anyways, here we are.

the old static said:
Static: (Innate)
This Pokemon’s body is surrounded by an electric field that has a 30% chance of paralyzing opponents that use contact moves on this Pokemon.
Now this version of static is okay, but I honestly think that it could be a little more realistic. For example, an "effects on" mechanic for it that allows the pokemon with static to paralyze the opponent. I think that this follows the flavor text of the ability, as contact paralyzes the attacker. So why not allow it to paralyze the defender? Static's field charge should also empower electrical moves by 1 BAP, due to the electrical charge. Also, I think that it should have an energy drain to use these extra effects to empower the attacks, to counteract the buffs we may give it.
tl;dr said:
Static: (innate, can be enabled)
This Pokemon’s body is surrounded by an electric field that has a 30% chance of paralyzing opponents that use contact moves on this Pokemon.

ON ENABLE: this pokemon increases the intensity of it's electric field at the cost of 3 EN per action. The charge in the field grants 1 BAP to electric-typed attacks, and the contact moves also gain a 25% chance to paralyze the opponent.

Any questions?
 
I oppose the Static proposal and feel that it needs discussion.

To be honest, this seems like trying to make Static similar to Poison Point. If that's the idea, then I think a better way to do it would be like this:

[box]Static:

Type: Can be Disabled

This Pokemon’s body is surrounded by an electric field that has a 30% chance of paralyzing opponents that use contact moves on this Pokemon. When disabled, all of this Pokemon’s Electric-type attacks that inflict paralysis will inflict 25% paralysis (with the same chance of effect).

Pokemon with this ability: Pikachu, Raichu, Voltorb, Electrode, Electabuzz, Pichu, Mareep, Flaaffy, Ampharos, Elekid, Electrike, Manectric, Emolga, Stunfisk, Monohm, Duclohm, Cyclohm.[/box]

Poison Point has situations in which you would want it enabled and situations in which you would want it disabled, depending on whether you would rather try to inflict toxic poison or catch them off guard with regular poison. This version of Static provides a similar trade-off: would you rather try to inflict 25% paralysis or catch them off guard with 20% paralysis?
 
Something real quick that's been bugging me because it violates common sense

Why do people vote "no discussion" after people have posted an opposite opinion? If you have two disagreeing opinions, there must be discussion. The "no discussion" option should only be for stuff like fake out which are obvious to an extreme degree, or "guys let's give wobbufett 100 atk". If there are two differing opinions outside of the original poster's, there should always be discussion.

So for the sake of having stuff making sense, I propose that the "no discussion" button can only be pressed when there is unanimous support or opposition.
 
To orcinus's proposal: Opposing, no discussion.

It's come to my attention that Moonlight is currently the worst healing move in ASB, working well only in flavour arenas, and well... Sucking horribly outside of them. I propose a change to Morning Sun as well, distinctly to have them match.

DAT said:
Moonlight: The Pokémon absorbs moonlight to restore health. If the moon is not out, Moonlight heals half its normal value. Moonlight restores 35 HP in strong moonlight, 25 HP in normal weather, and 15 HP in other weather or a poorly lit indoors arena.

Attack Power: -- | Accuracy: -- | Energy Cost: 6 + (Max HP / 10) | Attack Type: Other | Effect Chance: -- | Contact: N/A | Typing: Normal | Priority: 0 | CT: Passive

Morning Sun: The Pokémon looks up to the sun to restore health. If the sun is not out, Morning Sun heals half its normal value. Morning Sun restores 35 HP of maximum health in strong sunlight, 25 HP in normal weather, and 15 HP in other weather or a poorly lit indoors arena.

Attack Power: -- | Accuracy: -- | Energy Cost: 6 + (Max HP / 10) | Attack Type: Other | Effect Chance: -- | Contact: N/A | Typing: Normal | Priority: 0 | CT: Passive

I believe that they should say something along the lines of "in strong lighting", "in non-bright weather" and "in the absense of weather and strong light sources"
Obviously these are just examples, but I feel that they should be considered.
 
I would like to propose an alternative to EspyOwner's proposal:

Objection's idea said:
Moonlight: The Pokémon absorbs moonlight to restore health. If the moon is not out, Moonlight heals half its normal value. Moonlight restores 35 HP in strong moonlight, 25 HP in normal weather, and 15 HP in other weather or a poorly lit indoors arena. Unless the arena description specifies otherwise, it is assumed that the moon is out if the arena is outdoors and not out if the arena is indoors.

Attack Power: -- | Accuracy: -- | Energy Cost: 6 + (Max HP / 10) | Attack Type: Other | Effect Chance: -- | Contact: N/A | Typing: Normal | Priority: 0 | CT: Passive

Morning Sun: The Pokémon looks up to the sun to restore health. If the sun is not out, Morning Sun heals half its normal value. Morning Sun restores 35 HP of maximum health in strong sunlight, 25 HP in normal weather, and 15 HP in other weather or a poorly lit indoors arena. Unless the arena description specifies otherwise, it is assumed that the sun is out if the arena is outdoors and not out if the arena is indoors.

Attack Power: -- | Accuracy: -- | Energy Cost: 6 + (Max HP / 10) | Attack Type: Other | Effect Chance: -- | Contact: N/A | Typing: Normal | Priority: 0 | CT: Passive

This way, those who want to add day/night flavour to their arenas can do so, while the neutral arenas like the ASB arena remain neutral.

EDIT @ Orcinus' proposal: It is perfectly fine for person A to think something should obviously be implemented (they support it and do not think there should be discussion) while person B thinks person A is a complete moron and the thing should obviously not be implemented (they do not support it and do not think there should be discussion), and person A thinks person B is a complete moron to boot. The council is quite capable of judging which of the two (if either of them) is a complete moron and making a decision accordingly. Plus, if two votes say support and three say oppose then, even if all five votes say no discussion, the council would probably go to discussion anyway.

With that in mind, I oppose that proposal and do not feel that it needs discussion.
 
Regarding Morning Sun and Moonlight: Support without need for discussion. As long as the proposed codified implementation works explicitly in all contingencies (standard conditions, flavour arenas, etc.) without changing the meaning implied by the norm (I always regard those healing moves to be normal should there be no specific weather), I'm for it.

Also, I think Feedback thread is clogging up due to the fact that we still have unresolved Discussion threads that needs attention. While I think I may know the reasons behind this backlog, I'd still implore a projmod or a Councillor to list out what's awaiting us in here, with Council's decision on certain issues that had garnered enough votes from posters.
 
I support without need for discussion every single proposition that in any way nerfs Endeavor+Endeavor, up to and including changing it to CT: None and make it like explosion in regards to energy.

Can someone please do something about it now?
 
I support without need for discussion every single proposition that in any way nerfs Endeavor+Endeavor, up to and including changing it to CT: None and make it like explosion in regards to energy.

Can someone please do something about it now?
Yeah, about that, I put up a non-CT: None proposal here that did not get enough votes because of the whole Rough Skin/Iron Barbs fiasco, which will prolly be vetoed at any rate.

Who here supports the proposal in the link I posted?
 
Personally I think Endeavour=CT: None is a no brainer. Also I would like to see some kind of a damage cap on it akin to what we have on Pain Split (hint: 25 is a good number)
 
I'd probably also vouch for a reduction in Moonlight and Morning Sun healing; to be honest 35 HP is an extremely large chunk (compared to other moves' 20 HP) and imo they should only be around 25 at best.
 
I'd probably also vouch for a reduction in Moonlight and Morning Sun healing; to be honest 35 HP is an extremely large chunk (compared to other moves' 20 HP) and imo they should only be around 25 at best.
imo, just bring Moonlight & Morning Sun in line with Synthesis (10/20/30 HP), & that would do.

At any rate, I support changing said moves, but I think a short, sharp discussion could be needed? idk.

EDIT: On the topic of Endeavour, if the BEC of Endeavour + Endeavour is based on Endeavour > Endeavour (Which it should be), the HP Threshold for the combo to work is a whopping 180, with a BEC of 16+(180÷1.75^2)+((180-(180÷1.75))÷1.75^2)=~99.97 EN, dealing 180×(9÷7)=~231.43 DMG, & costing (16+((180×(9÷7))×2))×1.75=838 EN. Proof that Mega Endeavour is pretty dumb, lol.
 
Regarding Endeavour and Helping Hand: Support without need for discussion. Every option listed before - from Explosion-like Energy requirements, to CT:None, etc. etc. are clear cut and does not merit a Discussion thread to me - the Council can simply hold a Multiple Bold Voting or IRV to decide which facets of those two moves need be nerfed. Its not like Block, where people come up with different formulae and try to convince each other that theirs is the best - we all have one goal, and all we need is a vote on how to achieve it, since all roads lead to Rome.

EDIT:
<Deck_Knight> Things shouldn't take more than 24hrs or so to be approved. If it's less than that it isn't an issue.
<Zt> Well, by that definition, Deck... The currently earliest unapproved thread is posted approximately 23 hours, 50 minutes ago.
<Deck_Knight> Do we have an active listing of all the approvers?
<Deck_Knight> Mostly I'm interested in figuring out if people that were made approvers long ago are now inactive
<Zt> If that's your question, then yes.
<Deck_Knight> And rather than asking me I'd prefer we use the Policy Center or something to make sure we actually have a decent self-refreshing set of approvers.
So, uh, when your lord and benefactor relegates the responsibility to you, you do your best to not screw it up?
General Approvers' Proposal said:
  • The term "General Approver" refers to users on the ASB forums that have the right and responsibility to approve ASB profile registrations and Prize Claims.
  • The objective of this proposal is to create a self-sustaining, constantly-updating General Approvers' list, and to minimize backlog in Reg Tower and PCT.
  • The current Council will elect a single Councillor to oversee the appointment of new General Approvers, as well as the terminations of their statuses. (Similar to how MK is in charge of the Hall referees)
  • Existing General Approvers who are still active (it's a subjective list, but it probably includes EMma, dogfish, Obj, Engi, Ralex, etc.) may retain their status.
  • Projmods on the ASB forum are automatically granted the General Approver status, and are also charged to update the OP's list weekly.
  • The General Approver status is automatically granted to every Council member, as well as members of the RP/Gym Approval Committee, but it will be revoked if the said Council/Committee Member terminates his/her term.
  • The General Approver status may also be temporarily granted to reliable, upstanding ASB forum users, subject to conditions and current situations.
  • A General Approver may willingly terminate his/her own status as one, as long as they nominate a suitable replacement candidate.
  • Should a General Approver be inactive for more than 3 months (from the last approving post made), his/her status will be terminated.

Fire away the votes.
 
[box]The term "General Approver" refers to users on the ASB forums that have the right and responsibility to approve ASB profile registrations and Prize Claims.
Sure

The objective of this proposal is to create a self-sustaining, constantly-updating General Approvers' list, and to minimize backlog in Reg Tower and PCT.
Sure

The current Council will elect a single Councillor to oversee the appointment of new General Approvers, as well as the terminations of their statuses. (Similar to how MK is in charge of the Hall referees)
Sounds good

Existing General Approvers who are still active (it's a subjective list, but it probably includes EMma, dogfish, Obj, Engi, Ralex, etc.) may retain their status.
03:58 Texas I think we have like 8 active approvers or something?
03:58 Texas active meaning not dead
03:59 Texas me, glacier, ralex, df, iar, engi, em, obj


Projmods on the ASB forum are automatically granted the General Approver status, and are also charged to update the OP's list weekly.
Sure. Proj mods have to be good with data.

The General Approver status is automatically granted to every Council member, as well as members of the RP/Gym Approval Committee, but it will be revoked if the said Council/Committee Member terminates his/her term.
Iffy on this. Future council members may not be good approvers. Also no to gym/rp approvers being able to approve claims, different beasts (yea i know in this case gym are approvers anyway)

The General Approver status may also be temporarily granted to reliable, upstanding ASB forum users, subject to conditions and current situations.
Sure

A General Approver may willingly terminate his/her own status as one, as long as they nominate a suitable replacement candidate.
Eh, terminate, but it should be up to the council member to deem if a replacement is necessary and to find one if so.

Should a General Approver be inactive for more than 3 months (from the last approving post made), his/her status will be terminated.
Sure, subject to other posts such as councilman inactive for one month being removed.[/box]
 
Status
Not open for further replies.
Back
Top