Jump to content

Recommended Posts

Posted

I am using the recipe of 4 Obsidian, 4 TNT, and 1 Diamond Block, to try to make a craftpacket for the diamond shards, but instead the recipe is showing that I will get a:

fub3ir.jpg

any ideas on this?

This is a tekkit lite server... also happens in single player...

Posted

DON'T PUT THOSE IN FACTORIZATION MACHINES, it bluescreened our server and destroyed all privileges to place blocks for all players. We had to completely reinstall the server after putting that packet into a craftpacket stamper. It also ALWAYS crashes attempting to make ANY packet in a craftpacket maker. I think the standard install for all of factorization is flawed to some degree and should not be used until fixed or at least someone from the official creators explains what is going on with this. Further information can be found at this bug thread, http://forums.technicpack.net/threads/craftpackets-always-crash.34892/ .

Posted

If something that critical happens, i seriously ask myself about the competence of the tekkit lite team releasing something like that. This is more than negligent.

Posted

Hopefully it is a simple mistake in the version of factorization or somesuch, but as of now i have not gotten any official explanation on anything. Keep checking the bug report i posted above for the latest info on this, hopefully they will respond there.

Posted

This is explained in the bug report thread, the server is using standard tekkit lite server install, and all players are using tekkit lite client install so there is no ID conflict for standard tekkit lite installs, though as you mentioned in the bug post that it is an item ID conflict which makes sense. This bug seems to happen single player and multiplayer as if anything requiring craftpackets is severely bugged using tekkit lite. Though i am quite new to minecraft mods, i have only done terrafirmacraft and tekkit(independently and on different windows installs), but again this affected all players on the server simultaneously and destroyed all privileges regardless of the init files for permissions, OP status, etc. The only fix we found was to reinstall the server.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...