hi, your probably aware of the lag issues associated with your mod. i think this could be easily improved in 2 ways:
1: your multi-blocks check very rapidly when forming, try adding a longer break between checking to form.
2: your machines EAT RAM when they are first placed, this continues to be an issue untill they have everything in place to function (power, items in the correct slots etc.) so i assume this is due to it checking for power/items and not clearing something fast enough.
perhaps a debug file for the block or something along those lines. it would be handy if you could add in a tool so we can see exactly what the machines are doing so we can give more accurate reports.

allso i would like to take this opertunity to sugest updating the 1.6.4 whilst working on the 1.7, as allot of people are running your mod in the FTB monster pack, however they are not actually accommodating your mod into their playthroughs due to lag.

thanks allot for putting so much time into this awesome mod, i actually prefer your fish to forestry bees :D

Umm, my multi-blocks only check when to form when you place one of their associated blocks... They also only check if they can operate once every 30 ticks... What version of monster are you using? My machines used to constantly check everything in 1.1.4 Mariculture, but don't anymore... And I do plan to update the 1.6.4 once I've finished my 1.7 version. I know plenty of people using my mod :p, The laggy things are actually generally the coral/kelp generation and mainly oysters, as oysters actually have a memory leak issue.

i am using the latest version of monster but manually updated to your 1.2i
sorry if it was unhelpfull, but i can see a verry clear spike in ram usage
whenever i use your machines, which after 5-10 mins becomes unplayable.
thank you for clearing up about the multi-blocks, that's really good to
know. i was suggesting their may be some kind of memory leak rather than
them simply checking to operate to rapidly.

thanks
from seb

On 12 March 2014 02:48, joshiejack [email protected] wrote:

Umm, my multi-blocks only check when to form when you place one of their
associated blocks... They also only check if they can operate once every 30
ticks... What version of monster are you using? My machines used to
constantly check everything in 1.1.4 Mariculture, but don't anymore... And
I do plan to update the 1.6.4 once I've finished my 1.7 version.

Reply to this email directly or view it on GitHubhttps://github.com//issues/18#issuecomment-37370505
.

---from seb---

You know memory leak is a very generic thing... Minecraft has one itself, I can't just randomly guess what the issue is. Especially since, I've had noone else say such a thing, and my machines have a lowish tick time. Where as I've had plenty of reports with oysters and have been able to confirm that myself... Is it happening for you with any specific machines in particular... That would be more useful than 'MEMORY LEAK FIX'

The only 'multiblocks' I could possible for any reason it imagine being is the incubator/crucible furnace, since they have to check to see if they're formed for their texture. But that's a graphical thing. Which is perfectly fine for most computers... I could add a config to disable their textures for lower end... (I've never had any issues on that part though).