This is nice but becca's pgm-multiloc, that many people use, does not order the hex the same way then you. 0 middle, 2 on top of it rotating clockwise.

Your 2 should be a 1, and your 9 should be the 7

@drallieiv I didn't changed the way we generate hives location, they were being generated this way: counter clockwise starting from the North-East position. Currently if you use -bh without sufficient workers to fill the beehive, i.e. -bh -w 5 - the positions 5 and 6 won't be populated.
I'm not changing this since it would require the rework of some functions I don't want to touch on.
Note that beccasafan's pgm-multiloc can be used to setup a "beehive of beehives" but it requires manual work as it is not designed to be used with --beehive.

This is really awesome! :-) I acknowledge your -bwh parameter offers the most flexibility but have you thought of a parameter that just gets a list of hives to be used and in the end evenly distribute all workers among the used hives? For example --beehive-include 0,3,6,11,17 --workers 15 will produce a diagonal list of hives according to your numbering assigning each hive 3 workers. Might be easier to setup. :)

Anyways, this is great and long overdue. ;)

@sLoPPydrive You can achieve what you're asking with this PR. If you don't force workers-per-hive it will distribute available workers evenly across enabled hives ;) You just need to disable the hives you don't want populated and everything goes as you're thinking.

You could renumber your hives. First, starting with 1 (so 0->1) might be bad programming but is probably a better user experience. Further, iirc beccasafan location hive generator orders them clock-wise so 2->2, 1->3 and so on for each leap, this feels also the most intuitive for me.

How so? I have to give parameters like -bhw 0:0. Do you mean I just have to mention those who shall be empty and all workers will be distributed among the non-empty hives?

@aRengo Please read what I've said... it's not "my hives" and as I said in the post before: I won't change this because it affects code I didn't do and wasn't required to be modified to implement the new features.

@sLoPPydrive Yes, exactly what you said... disable unwanted hives with -bhw <index>:0 and then supply how many workers -w you wish to be split between the remaining hives.

Hope to see this soon merged, will be awesome to distribute workers more where they belong 👍

Is this still being looked at? A bunch of people are still using pgm-multiloc (including me) but this PR has some inherent benefits. neskk already mentioned the memory usage (my server uses 10GB with 35 -st 14 instances at this point)

But more importantly, if #1980 or something similar gets merged, people using pgm-multiloc won't be able to use it since you'd need seperate level 30 accounts for each instance, this could be a fix.

@Qualimiox, you want something done? Talk to @sebastienvercammen... he's the dictator around here.
I've submitted this PR a very long time ago and I will maintain it since I'm currently using it.
Seb's probably been too busy writing blog posts or working on devkat to review it... Plus, he was very rude to me and kicked me out Discord just because I talk about stuff he doesn't like or want to. This made me lose the remaining motivation to keep giving back to RM, specially considering he's getting paid on devkat to work on RM.

@neskk A reminder to stay professional, or at the very least not spread unnecessary lies that other people then have to correct.

You were kicked out of #pr on Discord due to your rude behavior. It wasn't because "I was being rude to you" or because you "just talk about stuff". It was even put to a vote and it was unanimously agreed that it was better not to have you around anymore. You've only been behaving irrationally and you can't stay professional when confronted with a decision that disagrees with your opinions.

If you find it necessary, I'm sure @FrostTheFox will confirm. His Discord bot logs all chats.

As for devkat, it has been explained several times what devkat is exactly, and it's disappointing to see a fellow open source contributor react so strongly against an organization that was set up to contribute to open source in a sustainable manner. But your opinions are yours to have, I'll just have to ask you to either be more professional about them or to keep them for yourself entirely.

@sebastienvercammen I would post some print screens of your "professionalism" in that discussion, but then you would probably remove them. I've already saw that you edited multiple phrases from that discussion so don't try to spin this around. I wasn't rude, you kicked me out without notice. I don't care about the poll you did, most people don't know me so why would they vouch for me and risk going against the all might, all powerful dictator Seb, knowing that their fate would probably be the same as me.

@neskk Reminding you to please stay professional on GitHub (including outside this thread), otherwise I will have to prevent you access on the repository.