Mega (able - 11):
Cursed Rapidash, Summer Ampharos, Spring Ampharos, Skarigami, Robin
Blaze, Festival Gardevoir, Crystal Aggron, Banettenstein, Sala da
Menci, Easter Lopunny, Lucario-sensei
Perfect IV Spheal - looking for Pokémon with 4+ gold stars from the
Water 1 or Field egg groups, including:
Growlithe, Ponyta (both forms), Cyndaquil, Dunsparce, Houndour,
Torchic, Electrike, Numel, Absol, Shinx, Zorua, Mareep, Buneary,
Lucario, Squirtle, Slowpoke (both forms), Mudkip, Feebas.
Advanced forum search tool
The current forum search link is quite frustrating to use. You can
search by single-word-term(s), in a specific subforum, or by user.
You, however, can't combine a user search with a term search.
This suggestion contains a few new search parameters, as well as
some QoL features. They can be implemented as seen fit - limits may
be necessary to reduce server strain.
New search parameters:
- search by phrase (exact string match)
- search for threads (by title; and also by contents of the first
post)
- search posts by title (individual posts, not a thread)
- search within multiple subforums at once
- search by multiple users at once
- search by date
-
You would be able to combine search parameters.
QoL features
note to self - to suggest:
- voting options
- support ratio formula
- forum search
- hashtag search
- add AH user search to gts suggestion
- forum compact mode, avatar bar
rules:
- general legibility guidelines (excessive bbcode, all caps, zalgo,
other weird fonts, emoji spam, unicode characters, ascii art)
- spam rule applies outside of forums
- stricter legibility guidelines for contests (including
giveaways)
- giveaways cannot require you to repost the same
identical/re-phrased feed (i.e. sharing top 10 pokemon is fine,
sharing the same hashtag repeating the same thing isn't "ai 'art'
is bad because...")
suggestions to make/find for safe mode:
- if on hunt with chain 5+, confirmation needed for all lab eggs,
different species at tall grass
- if on hunt with chain 5+, no confirmation needed for same species
from daycare and gem collector
- if on hunt with chain 5+, confirmation needed for all other
chain-breaking eggs (event shop, ancient cave)
- confirmation pop up for redeeming vouchers
- is there a confirmation for event passes?
- when off, no confirmation for deleting comments
- when off no confirmation for adding berries to seeders
- when on, confirmation for closing palpads
- sending palpads
- gts offers
- set up auction
The suggestion voting system should be changed. It existed before
mod approval, so some options are a bit unnecessary.
"suggested before" and "SPAM" are both no longer needed.
"not well-explained" is also checked during approval. If you don't
understand, you can ask for a clarification.
"simplify an existing feature in an unnecessary way" is really a
matter of opinion. Let's take the suggestion for a "long term
streak system". You could say it's unnecessary as a streak system
already exists, but still use it. The question should be, if it was
implemented, how would it affect you?
New options:
(I would)
"benefit from / utilise"
"be negatively impacted by"
"be unaffected by / not utilise"
(this suggestion)
The current support ratio considers all votes equally. Few negative
votes should have a minor effect, while more negative votes have a
major effect. Neutral votes shouldn't weigh as much. Example
formula:
Support Factor = pos^2 / (pos^2 + 0.2*neg^3 + neut^2)
[x100 for %]
Where pos is the number of positive votes, neg is number of
negative votes, and neut is the number of neutral votes.
Examples:
My BHC rebalancing suggestion with a current 81.3% ratio would
increase to 97.9%.
A suggestion with 9:3:3 votes would have a 84.9% ratio (instead of
60.0%)
11:7:2 votes - 62.5% ratio (instead of 55.0%)
19:12:5 votes - 49.3% ratio (instead of 52.8%)
61:22:3 votes - 63.5% ratio (instead of 70.9%)
5:12:3 votes - 6.6% ratio (instead of 25.0%)
Back to the unnecessary part. Regarding my Currency Exchange
suggestion - "2 users think that this would simplify an existing
feature in an unnecessary way"
I disagree with that; as I stated in the suggestion, it solves 2
issues - no anonymous reselling, and users decide on a “fair”
price, not the stonks system.
"unnecessary" is a matter of opinion, and would be better of being
discussed in the thread itself.
Suggestions - voting options
Suggestions - support ratio formula
Forum search - advanced
Form search - tags
Auctions - user search
Hashtag search - advanced
Safe mode - updated Posts in others’ suggestions:
17/10/24:
Reached ToT Level 3.85
1 Retro Gastly encounter; caught
All upgrades except Odd Ditto Doll bought - 1,100 candies
Current candy amount: 1,927
3,027 candies earnt today
~40,000 interactions made since event started (12:00 server time);
~30,000 made before event started
18/10/24:
Reached ToT Level 6.26
0 Retro encounters
1x Dralucha, 2x Dark Ponyta, and 1x Gastly (Retro) eggs bought -
12,500 candies
Current candy amount: 3,357
13,930 candies earnt today
100,703 interactions made
19/10/24:
Reached ToT Level 7.62
3 Retro Haunter encounters; 2 caught with Ultra Balls
1x Pumple and 2x Plaguekrow eggs bought - 12,000 candies
Current candy amount: 6,013
14,656 candies earnt today
100,556 interactions made (First ~20k with Berries)
20/10/24:
3 Retro Gastly encounters; all caught with Ultra Balls
2x Witch Vulpix eggs bought - 5,000 candies
Current candy amount: 2,317
1,304 candies earnt today
0 interactions made
21/10/24:
Reached ToT Level 8.68
0 Retro encounters
2x Disguised Exeggcute and 2x Zomppet eggs bought - 13,000
candies
Current candy amount: 4,037
15,733 candies earnt today
100,228 interactions made (first ~20k with Berries)
22/10/24:
Reached ToT Level 9.52
1 Retro Gastly encounter; caught with an Ultra Ball
2x Nightmare Munna and 2x Sugar Shock eggs, 1x Misdreavus Cosplay,
and 1x Marshadium Z bought - 19,000 candies
Current candy amount: 746
15,709 candies earnt today
100,341 interactions made
23/10/24:
Reached ToT Level 10
1 Retro Haunter encounter; failed to catch with an Ultra Ball
Current candy amount: 15,111
14,365 candies earnt today
82,145 interactions made
24/10/24:
2 Retro Gastly, 1 Retro Haunter, and 1 Retro Gengar encounter; all
caught with Ultra Balls
1x MissingNo. (Marowak) egg bought - 20,000 candies
Current candy amount: 7,172
12,061 candies earnt today
49,735 interactions made
25/10/24:
2 Retro Gastly encounters; both caught with Ultra Balls
2x Marshadow and 1x Zombeagle eggs, and 1x Giratina Plushie bought
- 20,000 candies
Current candy amount: 2,873
15,701 candies earnt today
100,674 interactions made
26/10/24:
1 Retro Gastly encounter; caught with an Ultra Ball
1x Shiny Giratina Plushie bought - 10,000 candies
Current candy amount: 541
7,668 candies earnt today
15,360 interactions made
27/10/24:
1 Retro Gastly and 1 Retro Haunter encounter; both caught with
Ultra Balls
Current candy amount: 13,569
13,028 candies earnt today
~70,000 interactions made
28/10/24:
2 Retro Gastly, 1 Retro Haunter, and 1 Retro Gengar encounter; both
Gastly and Haunter caught with Ultra Balls
1x Griseous Pearl bought - 15,000 candies
Current candy amount: 14,386
15,817 candies earnt today
100,223 interactions made
29/10/24:
2 Retro Haunter encounters; both caught with Ultra Balls
Current candy amount: 30,174
15,788 candies earnt today
100,440 interactions made
30/10/24:
0 Retro encounters
Current candy amount: 45,910
15,736 candies earnt today
100,502 interactions made
31/10/24:
2 Retro Gastly and 1 Retro Gengar encounter; both Gastly caught
with Ultra Balls
Current candy amount: 61,473
15,563 candies earnt today
100,633 interactions made
1/11/24:
1 Retro Gastly, 1 Retro Haunter and 2 Retro Gengar encounters;
Gastly and Haunter caught with Ultra Balls
1x MissingNo. (Aerodactyl), 1x MissingNo. (Kabutops), and 18
Nightmare Munna eggs bought - 75,000 candies
Current candy amount: 4
13,531 candies earnt today
63,468 interactions made
Event summary:
Lasted 15 days (over 16 different days)
16 Retro Gastly encounters, all caught
10 Retro Haunter encounters, 8 caught
5 Retro Gengar encounters, 1 caught
31 total Retro encounters, 25 caught with Ultra Balls, 0 shiny
35 2% shiny chance eggs bought (+ 1 Retro Gastly egg), 0 shiny
All items/Pokémon/plushies needed for dex bought (+ 18 extra
Nightmare Munna eggs)
Candies earnt: 202,604
Interactions made: 1,225,008
“Visiting Singapore right now, and the
wifi speed is ridiculously fast. One click equals one click;
there’s no lag. I can see how some people manage to reach 100k
clicks in a day now. This means click events like Zeraora and SCS
are quite unfair for those in countries with slow internet. Also
gameplay in general, since interacting is the main way of earning
PD (and powerorbs for eggs).”
Here are the current gem rarities from
DW and Slots:
Common: Bug, Electric, Fighting, Flying, Grass, Ground, Normal,
Poison, Rock, Water
Uncommon: Dark, Fire, Ghost, Ice, Psychic, Steel
Rare: Dragon, Fairy (yes, they’re actually equally rare)
However, since some gems are more sought after due to Legend/SM
hunts:
Common: Fighting, Ground, Poison, Rock
Semi-uncommon: Bug, Grass, Water
Uncommon: Electric, Flying, Normal
Semi-rare: Dark, Psychic, Steel
Rare: Fire, Ghost, Ice
Super Rare: Fairy
Ultra Rare: Dragon
(Bug cannot be obtained from Rumble, except Galar. Grass/Water for
Starter SMs)
Those in the same tiers above should be priced pretty
similarly, but since this is PH, that isn’t the case
¯\_(ツ)_/¯
I'm not going to cover the first three
tunnels, since those are relatively easy, and there's not much
advice to offer for those, since they're pretty short paths. With
the first two (Beginner and Advanced), you could get lucky with
guessing questions you don't know. You don't need the
spreadsheet for those, but it will definitely help.
Split Decision is hell, as the height and weight questions are near
impossible. You need to use the spreadsheet. Which means you need
to be able to type fast. Try memorise as much as you can of the
non-height/weight questions, to give your fingers a break, so
you're not constantly typing.
I have a pretty good memory, so it may either be more difficult or
easier for you. I found that the more I played, the more I could
remember (at least in the short term). I could tell you right now
that Mareanie evolves at level 38, Croagunk has 2805 EHP, and
Drapion is in the Bug/Water 3 egg groups.
Don't get frustrated if you can't do it. Take a break and come
back. The game gives you a break every 100 levels, so you can split
it into 100+100+50 levels. Don't try to answer something if you
think you know the answer, but not 100% certain, especially on the
height/weight ones, since that's how I broke my chain a few
times.
Endless Path is significantly easier. It takes 7 minutes per 100
levels for me, 4m24s was my best. There aren't any height/weight
questions, and egg-group is the hardest, since they can be
misleading.
Other tips:
- On Endless, don't rely too much on the spreadsheet. You can use
it at first, but try get used to not using it. You'll get tired if
you do.
- After multiple runs, you get used to it, you remember more, you
answer questions faster.
- Don't adopt every egg you see. You get tempted to use powerorbs,
then you have none left. Come back when you have a free party
slot.
- When you break your chain, don't immediately start again. You'll
rush through it, and break it again.
- Have the spreadsheet in a separate window, maximised to see all
columns. In the same window, you might lose time when switching
tabs.
- If you aren't good at remembering things, this isn't the game for
you.
- Most (not all) questions are logical - look at the
Pokemon, what features does it have, is it a starter/legendary, how
much of the sprite frame does it fill (size), etc.
FAQ:
- For general information on the minigame, please see the wiki
- The spreadsheet can be found here
- You need to have a free party slot in order to get an egg. You
can't find one first, move an egg into storage, and then adopt it -
it won't show up without an empty slot.
- You have the possibility to get random eggs in Endless every 50th
and 100th level. They show up above the question.
To make a 'toggle all spoilers'
button, you'll need to use the following code:
[img][spoiler][/img]lorem
ipsum[/spoiler]
This leads to the code being converted as: image, start spoiler,
end image, spoiler contents, end spoiler. The {/img} block adds the
broken HTML code {" style="max-width: 100%"/>}. To hide this,
we'll need to make the {/img} block transparent, and reduce the
text size:
(you need the newline after the {/size} block)
Now, there is an 'empty' line before the spoiler contents. To have
the empty line after the contents, but within the spoiler, you can
place the spoiler contents right before the {size} block.
Similarly, to have the empty line outside the spoiler, place the
spoiler contents and {/spoiler} block before the {size} block. This
doesn't work with images, as having a {/img} block ends the first
{img} tag. Other BBCodes should work though (other than spoilers,
see "Nested spoilers" section).
The {img} tag still displays a broken file. To fix this, we can add
any image link, followed by a #, before the {spoiler} block. I have
used a 1x1 transparent pixel, but you can really use anything, such
as your favourite Pokemon's mini-sprite.
Note that you don't need to have any spoiler contents (placeholder
"lorem ipsum") if you want it to be solely a button.
This code can be placed anywhere in your post, though most useful
at the start and/or the end. Note that using text alignment tags
(left, right, center) can be a bit fiddly to get right.
(Or alternative orders mentioned in above
section, if you don't include images within the spoiler)
You could think of these as brackets; Code-A is a 'double open
bracket', while Code-B is a 'single close bracket'.
Using Code-A means that any following content (including spoilers)
are placed within the first spoiler. It also means that all
sub-spoilers are toggled upon opening the main spoiler.
To 'close the first bracket', we use Code-B. This means that any
following content (including spoilers) will be placed outside the
current spoiler. This also acts as a 'toggle-all button' for all
sub-spoilers above.
To 'close the second bracket', we need to use Code-B again. This is
necessary to ensure the 'toggle-all buttons' work properly. This
spoiler is now placed outside, below the main spoiler. It also acts
as a toggle button for the above spoiler (so if you only have one
main spoiler, it technically acts as a toggle-all spoilers
button).
To have a toggle-all spoilers button at the end of the post, when
you have multiple main spoilers, you will need to use Code-B
another time, after 'closing all brackets' correctly. Having one at
the start always works, even with incorrect 'bracket' syntax.
Example usage:
Toggle all spoilers:
[img]//upload.wikimedia.org/wikipedia/commons/c/ca/1x1.png#[spoiler][size=6][color=transparent][/img][/color][/size]
lorem ipsum[/spoiler][spoiler]lorem
ipsum[img]//upload.wikimedia.org/wikipedia/commons/c/ca/1x1.png#[/spoiler][/img][spoiler]lorem
ipsum[img]//upload.wikimedia.org/wikipedia/commons/c/ca/1x1.png#[/spoiler][/img][spoiler]lorem
ipsum[/spoiler][spoiler]lorem ipsum[/spoiler]Toggle all in
current:[img]//upload.wikimedia.org/wikipedia/commons/c/ca/1x1.png#[spoiler][size=6][color=transparent][/img][/color][/size]
lorem ipsum[/spoiler]Toggle
above:[img]//upload.wikimedia.org/wikipedia/commons/c/ca/1x1.png#[spoiler][size=6][color=transparent][/img][/color][/size]
lorem ipsum[/spoiler]Toggle all in
current:[img]//upload.wikimedia.org/wikipedia/commons/c/ca/1x1.png#[spoiler][size=6][color=transparent][/img][/color][/size]
lorem ipsum[/spoiler]Toggle
above:[img]//upload.wikimedia.org/wikipedia/commons/c/ca/1x1.png#[spoiler][size=6][color=transparent][/img][/color][/size]
lorem ipsum[/spoiler][spoiler]lorem
ipsum[img]//upload.wikimedia.org/wikipedia/commons/c/ca/1x1.png#[/spoiler][/img][spoiler]lorem
ipsum[/spoiler][spoiler]lorem ipsum[/spoiler][spoiler]lorem
ipsum[/spoiler]Toggle all in
current:[img]//upload.wikimedia.org/wikipedia/commons/c/ca/1x1.png#[spoiler][size=6][color=transparent][/img][/color][/size]
lorem ipsum[/spoiler]Toggle
above:[img]//upload.wikimedia.org/wikipedia/commons/c/ca/1x1.png#[spoiler][size=6][color=transparent][/img][/color][/size]
lorem ipsum[/spoiler]Toggle all spoilers:
[img]//upload.wikimedia.org/wikipedia/commons/c/ca/1x1.png#[spoiler][size=6][color=transparent][/img][/color][/size]
lorem ipsum[/spoiler]
Simplified visualisation of codes:
Key:
- "A" is Code-A, "B" is Code-B, "s" is a
regular spoiler tag
- numbers refer to number of uses of that code
(0 for starting/ending toggle-alls)
- ">" refers to number of indentations (which [sub-]spoiler)
- "{" and "}" refer to start and end of 'toggle-all' groups; the
'brackets'
- ", " (comma space) to separate terms
Alternatively, you can place a quote tag around the whole code.
This allows you to start a new spoiler without having to 'close'
the previous one(s) using Code-B.
Horizontal rules, {hr}, are commonly
used as dividers to split up posts. However, sometimes they may
appear a bit too thin, when compared to a lot of text. Instead, you
currently can use double {hr}s, or more if you wish. You can also
use multiple code blocks:
You also have the option to use text characters and images of
course. But what if you, for whatever reason, wanted to create
'bold' horizontal rules using just BBCode?
Within spoiler tags, {hr}s come out bold. You can therefore, using
Code-A and Code-B mentioned in above section, create incorrect
syntax, in order to apply spoiler formatting outside of spoilers:
[spoiler]lorem
ipsum[img]//upload.wikimedia.org/wikipedia/commons/c/ca/1x1.png#[/spoiler][/img][img]//upload.wikimedia.org/wikipedia/commons/c/ca/1x1.png#[spoiler][size=6][color=transparent][/img][/color][/size]
lorem ipsum[/spoiler]
[hr]
lorem ipsum
{A1{, B1}
{hr}
one 'bracket' is still open, so while following content is not
placed within the spoiler, formatting still applies.
This does, however, mean you will need to use a spoiler tag, with
at least one sub-spoiler, before the section where you want to use
bold {hr}s in. So a simpler option would obviously be to just place
the content within a regular spoiler tag, if you don't care about
having to open a spoiler, or the background colour.
Text alignment tags, left and right,
end up shifting the entire code block, not just the text. You'll
need to add a line of transparent text above to correct the
length.
There can be quite a few overlap issues, which you'll need to fix
by using newlines (equivalent to the number of lines within the
alignment tag). This isn't really possible to explain, so just
experiment yourself. (These alignment issues apply to regular text
as well, not just code blocks).
Center tags don't change the block's width, only shift it slightly
right and center the text, so they don't require transparent text,
but there can still be some overlap issues that are fiddly to
fix.
Using a spoiler tag doesn't fix the overlap issues (they can
overflow out of the spoiler), but using a quote tag does.
The width of transparent text has to be greater than width of the
whole block, not just the text inside.The width of characters
varies between different devices/OSes, so try and add an extra
character or two to the transparent text, to be safe.
You can increase the width using transparent text, but you cannot
decrease the width; you must use newlines instead:
____________
lorem ipsum dolor sit amet
[left][color=transparent]____________[/color][code]lorem ipsum
dolor sit amet[/code}[/left]
____________
lorem
ipsum
dolor
sit
amet
[left][color=transparent]____________[/color][code]lorem
ipsum
dolor
sit
amet[/code}[/left]
You need to use text alignment tags to
change the code block's width. Same as above section, you'll need
to add a layer of transparent text. Only difference is you're
linking the code block as well.
Example with multiple columns. There is no way to fix the gaps.
First left goes furthest left, second left is placed next furthest;
first right goes furthest to the right, second right is placed next
furthest:
You can also try do something like this, with gaps between each
row, so it is less likely to misalign all the rows (still may
misalign the columns in the next row):
[center][left][color=transparent]______________[/color][code]lorem
ipsum
dolor sit amet, consectetur adipiscing
elit[/code}[/left][color=transparent]_[/color][code]lorem ipsum
dolor sit
amet[/code}[/center][center][left][color=transparent]______________[/color][code]lorem
ipsum
dolor sit amet[/code}[/left][color=transparent]_[/color][code]lorem
ipsum
dolor sit
amet[/code}[/center][center][left][color=transparent]______________[/color][code]lorem
ipsum
dolor sit amet[/code}[/left][color=transparent]_[/color][code]lorem
ipsum
dolor sit
amet[/code}[/center][center][left][color=transparent]______________[/color][code]lorem
ipsum
dolor sit amet[/code}[/left][color=transparent]_[/color][code]lorem
ipsum
dolor sit amet[/code}[/center]
The text replacement isn't working correctly, likely due to
incorrect regex. You need to make sure ITEMNAME is fully
lower-case, has hyphens instead of spaces, and has no special
characters. E.G. "Poké Ball" should be "poke-ball"; "King's Rock"
should be "kings-rock".
No portion of this guide may be reproduced in any form without
written permission from the author. This includes recreating the
contents of this post as another guide.
You are permitted to use quotes/extracts from this post for
educational purposes only, such as answering a question in the Help
forum or the BBCode Guide thread. Credit should be provided by
linking to this post.
The sections "Link shorthands", "Item BBCode", and "Other
resources" are exempt from reproduction restrictions, as they are
not original content. You still, however, cannot use direct quotes
for reproduction purposes, without permission from the author.
You are permitted to use codes provided in this post for personal
purposes, such as stylising a Diary or Shop. Credit is not required
for these purposes.
"1x1.png" sourced from the Wikimedia Commons (Description Page).
HTML snippets written by Riako, from this Site's function
"bb_decode".