Talk:Beehive

Naming
, the in-game name of this block is "Bee nest" (lowercase N). Should this page be at this title or the current one?-EatingSilencerforBreakfast (talk) 18:10, 22 August 2019 (UTC)
 * Yes, it should. FVbico (talk) 18:13, 22 August 2019 (UTC)
 * Okay thanks!

For future readers: the page was moved to "Bee nest". -EatingSilencerforBreakfast (talk) 18:14, 22 August 2019 (UTC)

Well, as for the "merge (article[s])" suggestion,
As just-above, since "Bee nest" is like "Bee hive" - both lower-case - it's easier to just make it one or the other. One's Naturally Generated, one's artificially-Crafted.

As for the specifics, someone could argue that's a quality. Or that there's a quantity issue of "how many there typically are of each?"

If one's replaceable-since Craftable, there's another quality. So the main reason even to merge is just to redirect people to the one more-commonly "abuzz," or noticed (somehow, depending on person). - Yilante. 8 /23 /19 5:28 p.m. 76.209.248.192 00:29, 24 August 2019 (UTC)


 * I generally think they're similar enough that the differences can just be noted in the article. They have the same basic functionality. I'd also say move them to "Bee hive" as the game uses "hives" to refer to both blocks. -PancakeIdentity (talk) 06:30, 24 August 2019 (UTC)


 * Many other pages say that something applies to “bee nests or bee hives”. It would be easier to just refer to “bee hives”. The BlobsPaper.png 22:39, 24 August 2019 (UTC)
 * ; should the page title be nest or hive?  Nixinova  T  C  22:44, 24 August 2019 (UTC)
 * Hive. It's the more common name and the one the game seems to prefer (see the tag). -PancakeIdentity (talk) 23:09, 24 August 2019 (UTC)


 * How are the two related in the game code? If the devs are treating them as basically the same object, for example inheriting from the same hive object, then to me that would strongly support merging.  If they are completely separate in the code, then I would expect the potential for them not to stay in lockstep, either intentionally or as an unintentional bug.  If that were the case, it may lead to a ugly block of clarifying footnotes, eg 'nest does This in 19w36a but box does This in 19w36b', or 'as of 19w35c only nest does That'.  72.196.148.70 22:46, 24 August 2019 (UTC)
 * Outside of history sections, old behavior shouldn't be mentioned in articles. If their uses get vastly different in the future, we can reconsider splitting. As of now though, they're almost identical. -PancakeIdentity (talk) 23:15, 24 August 2019 (UTC)


 * Both have the same usage, block states, block entity, and basic model, and are both in the beehives block tag, as such this should be merged into the bee hive page. If their uses get more different at a later point again, then we can always split the article again. Right now, this is basically a duplicate page. FVbico (talk) 23:08, 24 August 2019 (UTC)


 * Should I go ahead with this? -PancakeIdentity (talk) 17:40, 25 August 2019 (UTC)


 * Only one opposition, which gave basically no argumentation, Ivd say go gor it. FVbico (talk) 17:45, 25 August 2019 (UTC)

Renewable "No"?!?
If Bee's nests have a chance of spawning on oak trees, shouldn't it be marked as renewable? 108.220.161.172 17:34, 26 August 2019 (UTC)
 * That should say generated, not spawn; they can only be made by world generation, not randomly out of nowhere or saplings . FVbico (talk) 17:36, 26 August 2019 (UTC)
 * Edit: you're right, changing. FVbico (talk) 17:37, 26 August 2019 (UTC)
 * This is apparently a Java only feature. Bee nests don't generate from saplings in Bedrock, they only generate during world generation, so on Bedrock, Bee Nests should be Non-renewable 86.191.221.115 23:29, 6 February 2020 (UTC)

Pending merging
Greetings, I see some users wanting to merge the bee hive with the bee nest and I want to express my opinion towards this subject.

Bee hive and bee nest of course are different. if we merge them we should merge cobblestone and stone or merge Popped end fruit with the uncooked one or perhaps the salmon item and the salmon fish, since they're the same too. They have different pattern and of course different crafting recepe, they shouldn't really be merge with another page, what name do you plan to put it? You need both of the names to pop up,

That why I consider merging them unneccesary. Silviu200530 (talk) 17:40, 25 August 2019 (UTC)


 * The examples you gave a very different from this; these blocks are extremely similar, everything execpt the drop and obtaining is the same.
 * Stone and cobblestone have many more differences, hardness, usage, etc. chorus fruit and popped chorus fruit also have major differences, mainly the lack of edibility; lastly salmon entities and items have nothing in comon except for the name and that the entity drops salmon when killed.
 * Please also see the Bee nest talk page for the rest of this discussion. FVbico (talk) 17:44, 25 August 2019 (UTC)


 * I oppose this idea only because of the crafting recepe, drop and the texture difference and the name. I suppose I shouldn't have started this discussion because it seem it is already merged. Sorry if I caused anything. Silviu200530 (talk) 18:12, 25 August 2019 (UTC)


 * A lot of other pages (see Stone) contain blocks that have only those differences. What really matters is how they function, and they're identical in that regard. -PancakeIdentity (talk) 18:36, 25 August 2019 (UTC)


 * The two blocks function exactly the same. The drop is explained in half a sentence and the crafting and textures don't matter. The articles are too similar not to be merged. As per your original example, cobblestone and miss stone are merged even though they have different cragting, drop and texture because they're very similar though not as similar as beehives (which both share the entity id "beehive" implying that they act as the exact same block but with a different texture).  Nixinova  T</b> </b> C</b> </b> 19:55, 25 August 2019 (UTC)

Block image
Currently the block image render is flipped, showing the front face on the left rather than the right half. - tryashtar (talk) 06:01, 2 October 2019 (UTC)
 * The furnace also does so. It doesn't have anything wrong and is also visually balanced (it "looks" into the page). Lê Duy Quang (Make some words | Contributions) at 6h04:07 | 2/10/2019 (UTC)
 * Huh, somehow I never noticed. You're right, it's better this way. - tryashtar (talk) 02:04, 3 October 2019 (UTC)

Generated Structure
Isn't a beehive technically a generated structure when it naturally generates? It isn't the only 1x1x1 structure (buried treasure is the other), or is it one with the tree structure?73.208.227.101 16:28, 26 October 2019 (UTC)


 * We can add it to Terrain features maybe? -PancakeIdentity (talk) 19:37, 26 October 2019 (UTC)
 * It is definitely more a terrain feature than a generated structure. Both by the definition as explained on the latter page, as well as in the logical assumption that generated structures are supposedly only artificial constructions as opposed to naturally occurring features in nature. – Jack McKalling [ Grid Book and Quill.png Grid Diamond Pickaxe.png ] 07:51, 27 October 2019 (UTC)

Bees going in and out of the beehive
From my experience it seem like the bees can enter in the behive from every side but can only exit from one side: the side from which the honey come out when the beehive is full. I don't feel confident enough to edit the page, I don't know where to put this information and how to phrase it. So I'm leaving it to someone else. –Preceding unsigned comment was added by 46.193.66.157 (talk) at 16:09, 20 December 2019 (UTC). Please sign your posts with

Fires v. Campfires
"If there is a lit campfire; or fire directly underneath the hive ..." My experience (Java edition, 1.15.1) is that fire on Netherrack does not pacify the bees, and also it catches the tree / beehive on fire, whereas campfires do pacify the bees and don't light wood plank blocks (or trees / beehives in short exposure) on fire. I'm hesitant to edit the article in case I'm just doing something wrong. But I think that should just say "If there is a lit campfire directly underneath ...", removing "or fire". 209.6.91.214 02:02, 8 January 2020 (UTC)