[Tee]

I don't agree with it because it's non-legit. You can't see that info in vanilla MineCraft, so why should it be available in MineRealm? Why should a player be able to see the total number of mobs in a realm when they're beyond his/her vision? F3 is a bonus IMO ... really we shouldn't even have that info, and it's just fortuitous that the debug screen shows it.

Part of the design process for building automated farms is considering how you will control mob numbers and deal with items. It's possible to do some very funky stuff with mob numbers using redstone (eg I have a comparator-based mob counter design in SP which will trip a redstone signal once a preset number of mobs pass through it) and hoppers/droppers give you the ability to collect and transport items without worrying about item limits.

-1 from me, I'm afraid.

[Intelli]

The amount of 'no' votes for this suggestion disappoints me. As previously stated, there seems to be literally no downside to implementing something like this. If someone would care to enlighten me as to why this could possibly be considered a bad idea, I'd genuinely appreciate it.

Lag. Plus /realm isn't supposed to be some debug screen.

[Prodigy9]

I don't agree with it because it's non-legit. You can't see that info in vanilla MineCraft, so why should it be available in MineRealm?

Part of the design process for building automated farms is considering how you will control mob numbers and deal with items ...hoppers/droppers give you the ability to collect and transport items without worrying about item limits.

The non-vanilla argument could also be said of the mob/item limiter. I do think the challenge of trying to control those numbers with machinery is a stronger argument against this idea, though I don't think it completely eliminates the use for this proposal.

Lag. Plus /realm isn't supposed to be some debug screen.

Where is the line drawn between a valid information source and a "debug screen?" From the current information in /realm and other existing commands, we have access to various other factoids about realms, including the realm's owner, the guild that a realm belongs to, the date the realm's owner was last online, and a complete list of realm members.

I'm not sure I understand the lag argument. Wouldn't the processing power to display a realm's counts be pretty small compared to the process of doing the counting (and eliminating some of the mobs or items, if necessary) in the first place? Or if you're referring to the lag that would result from players pushing their farms to the maximum level of available mobs/items, that seems like it could be addressed by the limiter system itself rather than by restricting access to information about the system.

[Tee]

The non-vanilla argument could also be said of the mob/item limiter.

The 100 mob/realm cap is a necessary evil to allow the server to run consistently at 20TPS even under heavy load. It's non-vanilla but required to allow a relatively popular server to run on the hardware it's hosted on.

I do think the challenge of trying to control those numbers with machinery is a stronger argument against this idea, though I don't think it completely eliminates the use for this proposal.

This raises an interesting dilemma actually. If the area mob cap proposed by Intelli is implemented and affects the function of spawners then I have some groovy ways of splitting mobs up to fit within the mob cap, but they all involve extensive use of redstone. It does make you wonder at what point the mob cap workarounds negate the benefit of the mob cap itself.

[RyGuy130]

The 100 mob/realm cap is a necessary evil to allow the server to run consistently at 20TPS even under heavy load. It's non-vanilla but required to allow a relatively popular server to run on the hardware it's hosted on.

If something 'non-vanilla' is required to keep the server running smoothly, it only seems like common sense to make it 'more vanilla' by having it impact gameplay less with a feature like this. Since we're being limited to how many mobs and items we can have in a 'non-vanilla' way, why shouldn't we have access to helpful information that would help us play the game more effectively within these imposed restrictions?

Lag. Plus /realm isn't supposed to be some debug screen.

As for this, Prodigy9 has already done a wonderful job of expressing why these don't seem like actual issues to me. Although, you are the programmer here, so if you'd like to elaborate on why this might cause any noticeable amount of lag, I'd certainly welcome the information.

[U2QU]

Okay, I have no vote or really anything to say about this discussion but you guys use some pretty big words. I mean I thought I knew a lot but this is like reading gone with the wind. So big worded and wow some of you guys are probably like in your 20's or 30's:P

This isn't a hate thread at all. Please don't think of it as but some of these arguments get pretty intense with quite technological terms (:

[Rokkrwolf]

Pretty simple suggestion that would be helpful when making sure that you've covered up all the caves in a realm, or making sure that you don't have too many mobs/item stacks floating around in your realms. An example of using this would be if you had a cow farm/pig farm setup in one realm. When you breed the cows, you want to make sure that there are only 50 cows before breeding the pigs. This can be done with F3, but checking mobs that are outside your field of vision cannot be. Item stacks simply cannot be done with F3.

Actually both work with F3...

Item stacks count up the same as the mobs on the F3 screen, whatever you look at visually will pop into the counter, so if you have 50 stacks and no mobs and you were looking it would say 50. I tried this the other day so I know it works.

If you really want to control your mobs there is several things you can do to get your exact numbers, but it doesn't take rocket science to figure them out.

I voted no myself, I don't see a point to it other than making it easier for people to look, but I really don't think we need such a thing in the /realm menu when we already have it with F3.