Problems with Apiarist Database, Genepool, Sequencer in 1.4.9.6

Issue #127 resolved
Nikola Jakic created an issue

Hi,

I noticed some bugs when playing 1.4.9.6 version on Minecraft 1.4.6 in multiplayer.

First is bug with apiarist databank/database, I couldn't craft it, but I could cheat it throught NEI.

Genepool is acting strangely with power supply. I connected 1 combustion engine and it started working normally, then after few minutes it stopped. Removing and placing again genepool reset that bug. Also when bees from main slot are liquefied next bee/bees come to that slot but genepool just stops, need to remove then add again that bee/bees to that slot to continue working. One more problem is that after placing genepool and connecting to combustion engine, it started to oscillate the speed of processing bees, mainly it was extremely slow, and combustion engine collected power more that it distributed. Sequencer can only make template for some, main bees, can't make template for example for dilligent bee or noble bee. I suppose this is intentional, but it should maybe be possible to allow templating any bee, because it becomes hard enough (time) for making some species.

And I have 2 questions. Does Extra Bees for 1.4.7 Minecraft work (will work) for Minecraft 1.4.6? And why isn't this project opened on bitbucket, atleast to view your code, because people could help (I for example have master's degree in software engineering, and I develop applications in c# and Java, and in spare time could view your code and maybe suggest something, because we (I and my friends) love this mode). :D

Comments (2)

  1. Alex Binnie repo owner

    Well I'm working on bugs etc. so most will be fixed soon Question wise - First one, probably not, but a lot of those bugs are fixed in 1.4.7 versions. And two, as forestry is closed source, and my mod is based heavily on Sengir's, I feel mine too should be closed source. That does not mean I don't mind people decompiling it (jd-gui is quite useful ;) ) and seeing if they can spot a bug before me :)

  2. Log in to comment