Summary of Rejected Suggestions: Difference between revisions

From PokéFarm Q Official Wiki
Jump to navigation Jump to search
No edit summary
 
Line 34: Line 34:
*'''Feed All Pokémon''': This would destabilize the game as a whole, both in terms of server load and gameplay/reward balance.
*'''Feed All Pokémon''': This would destabilize the game as a whole, both in terms of server load and gameplay/reward balance.
*'''Hiding Fields Once All Pokémon Have Been Clicked''': Not necessary for the majority of users, and would prevent users from viewing Pokémon that have already been clicked.
*'''Hiding Fields Once All Pokémon Have Been Clicked''': Not necessary for the majority of users, and would prevent users from viewing Pokémon that have already been clicked.
*'''Larger Fields''': If more space for Pokémon is needed, users must buy another Field or release Pokémon from current Fields.
*'''Larger Fields''': Not possible due to engine limitations. If more space for Pokémon is needed, users must buy another Field or release Pokémon from current Fields. <ref>https://pokefarm.com/forum/post/7445636</ref>
*'''Reduce Cost of Purchasing Fields''': Despite the gradual inflation of Pokéfarm's economy, the exponential increase of buying new fields helps maintain game balance.
*'''Reduce Cost of Purchasing Fields''': Despite the gradual inflation of Pokéfarm's economy, the exponential increase of buying new fields helps maintain game balance.
*'''Retain Selected Berry in Next Field''': This would be an official promotion of sorting fields by berry.
*'''Retain Selected Berry in Next Field''': This would be an official promotion of sorting fields by berry.

Latest revision as of 15:39, 11 May 2024

The Summary of Non-Actionable Suggestions is a helpful list of any Suggestions that have been Rejected, as updated by the Staff. This page serves to expand on those rejections, and is maintained by users.

If a suggestion is included on this page, it does not automatically mean it will never be considered again. If any user feels that they have an argument that trumps the reason for rejection, particularly if they can show how the benefits would outweigh the drawbacks, please make a new Suggestions thread about it.

Note: This list only includes suggestions that were outright rejected for the reasons listed. It does not include suggestions that were auto-rejected due to lack of player interest, or suggestions unrelated to PFQ.


Berry Garden

  • Automatic Watering: This would decouple effort from reward. The Water All feature already makes it much easier to keep berries watered.
  • Reduce Waiting Time by Watering when it is Wet/Damp: Subject for abuse; users could press the Water Plant button over and over until the berries can be harvested.
  • Plant All: This would decouple effort from reward. The berry-planting process has already been greatly streamlined.

Currencies

  • Additional Methods of Gaining Zophan Canisters/Gold Poké:
  • Currency Trading as an official site function: Users can purchase Credits and Gold Poké with Zophan Canisters. Aside from that, users may trade between themselves for currencies.

DayCare

  • EXP Delay Item: The daycare itself is free to use; the cost of breeding is that Pokémon gain XP.
  • EXP Lock Blocks Daycare EXP: The daycare itself is free to use; the cost of breeding is that Pokémon gain XP.

Events

  • Keep Any Event's Mini-game Permanently: Mini-games will be vaulted and unvaulted to appear in events as something to look forward to for each event.
  • Make Tournament Prize Egg a Target Score: This would destabilize the Tournament rewards system significantly.
  • Story Events Ideas: Due to legal reasons we cannot accept user suggestions for story content. This falls under the same category as user-suggested Pokémon.
  • Type Race Teams: This suggestion has been asked as both Allowing the users to choose their team and "Signup then be assigned a Team. The short answer to these suggestions is No, Every team is equal. It can also be subject for abuse, drama and toxicity.

Fields

  • Allowing an Egg Field for Extra Eggs: Users can only keep eggs in their party; if a user wants more eggs than they can currently carry in their party, they must hatch some first.
  • Disable Pokémon Movement: Unnecessary. If users would like to stop Pokémon in fields from moving, QOL keeps them in place.
  • Feed All Pokémon: This would destabilize the game as a whole, both in terms of server load and gameplay/reward balance.
  • Hiding Fields Once All Pokémon Have Been Clicked: Not necessary for the majority of users, and would prevent users from viewing Pokémon that have already been clicked.
  • Larger Fields: Not possible due to engine limitations. If more space for Pokémon is needed, users must buy another Field or release Pokémon from current Fields. [1]
  • Reduce Cost of Purchasing Fields: Despite the gradual inflation of Pokéfarm's economy, the exponential increase of buying new fields helps maintain game balance.
  • Retain Selected Berry in Next Field: This would be an official promotion of sorting fields by berry.
  • Stack All Pokémon: Field organization is the purview of the player. No particular organization is promoted by PFQ. Users may use skin CSS or the QoL Userscript to do this instead.
  • Unstack All Pokémon: Field organization is the purview of the player. No particular organization is promoted by PFQ. A grid view was introduced to see all Pokémon without actually changing their locations. Users may use skin CSS or the QoL Userscript to do this instead.

Hunting

These Suggestions are in regards to Shiny, Albino, or Melanistic Hunting.

  • Automatic/Guaranteed Melan: If users are guaranteed a Melan at any point in their hunt, they would be deincentivized to charge their Albino Radar.
  • Hereditary Shinies: Eggs from Shiny Pokémon have the same chance to hatch special as Eggs from non-Shiny Pokémon.

Items

  • Add a Drop Chance for Lucky Eggs through Scours or Boxes: This would unbalance the game.
  • Nature Changing Item: This would unbalance a core aspect of the game economy.
  • Rare Candy: PFQ's equivalent is the Cookie, obtainable from Events.
  • Recharging Uber Charms: The ability to recharge Uber Charms would remove revenue from PFQ.

Mobile Users

  • Mobile App: This would require a significant investment of money and time, as the app's development would need to be outsourced.[2]
  • Toggle Auto rotate: Auto-rotate is controlled by a user's phone settings; websites cannot override that setting.

Public Forums

  • Ability to Delete Own Posts: Forum posts and PMs need to persist for the safety of the players, and to ensure that the Terms of Service are not being violated. Any individual forum post that is deleted is first reviewed by a Moderator.[2]
  • Allowing players other than the Original Poster to edit a forum post: This would invite violations of the Terms of Service, particularly if players had a falling out or otherwise disagreed.[2]
  • BBCode to Count Pokémon in Fields: This would put an extremely heavy load on the server in order for the BBCode to return the correct number.
  • Custom Userbars with Pokémon: This would require designing, programming and maintaining several thousand userbar variants.
  • Downvoting: Downvotes will not be added outside of reviews.
  • Extend Journal Deletion Timeframe: Journals last up to 3 months of inactivity, which is significantly longer than normal threads.
  • Granting Thread-Specific Mod Powers to Users: The Mod team goes through an application and approval process, and users are not permitted to "Mini-mod." If a user sees a post that shouldn't be in a thread, they should use the Report button.[3][4]
  • Search Feature: Full Thread Post of Reasons. **Any internal search function would result in additional site lag. Google Search can fulfill this function by entering "site:pokefarm.com" before your search term(s).[2][5]
  • Subscribing to Entire Forums/Sub-Forums: This would put strain on the server and increase server costs significantly.

Party

  • Egg Locking to Prevent Accidental Hatching: Users are shown a warning before hatching an egg that would break their shiny chain. Users may use Egg Passes to hatch eggs that would break their chain.
  • Instant Hatching: Pokéfarm's core mechanic revolves around interacting with other users' eggs and Pokémon; any item that allowed instant hatching would hurt the game experience. The EXP. Share and Egg Timer can be used to boost hatching speed.

Pokémon

  IMPORTANT NOTE: Pokéfarm DOES NOT accept player suggestions for new Pokémon designs for legal reasons. This includes Megas, Hybrids, Fusions, Exclusives, Variant, New Evolutions, Custom Sprites, and Beta Pokémon Suggestions.[2]
  • Beta Pokémon: Beta Pokémon's designs were changed before their official release for a reason; as a Pokémon fan site, the Staff feel that it would be disrespectful to go against those reasons.
  • Changing Gender: This would make obtaining rare-gender Pokémon much easier, and unbalance the game. [2]
  • Community polling regarding Pokémon sprites: Sprites will be adjusted and/or recoloured as needed in order to keep up with developments in the Pokémon franchise and in accordance with the growing experience of the Art Team. Implementing community polls regarding these visual updates would adversely affect the ability of the Art Team to output content in a timely manner, without being an effective means of addressing the desires of the community as a whole. [2]
  • Disabling Evolution: Users can give their Pokémon an Everstone to prevent evolution.
  • Dynamaxing/Gigantamaxing: The size limitations on Pokéfarm's sprites and the amount of detail needed for the formes make it impossible to implement these while still meeting internal standards for sprite quality. [2]
  • Legendary Breeding: Legendaries cannot be bred, with few exceptions.
  • New Starters:
    • Eevee: Would require too much EXP for a new player to hatch.
  • Radiant/Monochrome/Golden/Rainbow Pokémon: This would either put massive strain on the Art Team, or would sacrifice sprite quality during creation.
  • Reverse Evolution: Evolution is meant to be irreversible and is this way in the main games.
  • Sprite Recoloring Item for Multi-Color Pokémon: This is not possible with the current sprite management system. If a player would like a different colored version of their Pokémon, they are able to trade with other users for it. [6]
  • Toggle Albino/Melanistic Sprites from Before Revamps: Players are free to change which version of a sprite they personally see using their skin's CSS function. PokéFarm will not internally maintain past versions of updated sprites. [2]
  • Transform Ability: Allowing Pokémon such as Ditto or Zorua to form-change to other Pokémon would be too easily abused in Trading.

Scours

  • Make Scours More Interesting/Engaging: While most every other aspect of the site is based on activity, Scours being "passive" helps balance the site and gameplay styles.
  • Shorter/Longer Scours: Due to previous experience with issues this caused on PokéFarm 1 (PF1), we will not be reverting to this Scour model. [2]

Shelter

  • Any Additional Filters to Help Find Eggs/Pokémon: No additional filters other than the Black Flute and White Flute are planned, including a way to limit the number or species of Eggs or Pokémon that appear. Users can use the QoL Userscript to filter the Shelter.

Trades

  • Allow Users to Trade Fused Pokémon: This is not possible for the same reason that players can't trade them in the official Pokémon games: the fusion data wouldn't be transferred correctly, and would lead to issues when unfusing.
  • Direct Item Trading: This would require a complete re-design of the trading system.
  • Egg Trading: Would unbalance the game, and would put additional stress on the server.
  • Mass Pokémon Trading: This would require a complete re-design of the trading system.
  • Trade Evolution Site Feature: Trade Evolution has always been a part of Pokémon, and therefore will remain a part of PFQ. If a user does not return your Pokémon for any reason, please report it, and your Pokémon will be returned to you by the mods.

User Interface

  • Ability to Change Timezone: Keeping PFQ on one universal timezone prevents confusion between players in differing timezones.
  • Additional Notifications: Any suggestions regarding adding more notifications need to explain why the notification would be helpful enough to offset the annoyance of yet more notifications.
  • Clickback Button Registering New Pokémon/Eggs in Party: This would put enormous strain on the server.
  • Hypermode Expiration Reminder: Making it show up less often would make it a less effective reminder.
  • Retain Clickbacks from Previous Day: This would put enormous strain on the server.
  • Tracking Clicks Received from Other Players Over Time: This would put enormous strain on the server. These logs are deleted regularly to free up server space.

Miscellaneous

  • Additional Bonuses from Badges: Badges already give a significant boost to EXP.
  • Additional Methods for Gaining Gems: The current methods of gaining Gems via hatching or Trading are sufficient for current needs.
  • Editing or Deleting Sent PMs: Forum posts and PMs need to persist for the safety of the players, and to ensure that the Terms of Service are not being violated. Any individual forum post that is deleted is first reviewed by a Moderator.[2]
  • Group Chat: Please use the official Discord Server if you would like to have a group chat. PFQ will not be adding additional group chats, as they do not have the means to moderate them all.
  • Make "V~Wave" use each type before repeating: The V~Wave is supposed to be varying and unreliable, therefore it will remain fully random outside of Type Races.
  • New Staff Bonus Counters: There is not room for more bonus counters.
  • Pausing Hypermode: May be subject to abuse.
  • Rivals: Promotes over-competitiveness.
  • Stop Legendary/Mythical/Ultra Beasts PotD: Users hunt these Pokémon just like other Pokémon, and it wouldn't be fair to anyone to not have that boost.
  • Traditional Pokémon Battles: There are no plans to add main-series-style Pokémon battling.
  • Transferring Currency/Items from PF1: This would negatively impact PFQ's economy.
  • Translating PFQ into Other Languages: This would require both a significant and ongoing investment of time and would drastically increase the difficulty of ensuring the Terms of Service are not being violated. [2]
  • YouTube Subtitles: This would require more manpower than currently possible.

References