I noticed that on 1.4, OpenComponent will be discontinued. I have 1.3.6 at this moment with OpenComponent installed. What do you recommend me to do at this time? Keeping OpenComponent installed until OpenComputers 1.4 will be released and then remove it? Or remove it now?
And also, I would like to tell you that SGCraft (a really nice mod) now support OpenComputers of its own. ^^
And may I suggest you something? In ComputerCraft, there is PocketComputers. May you add Laptop (portable computers) in your mod? They will use energy with their battery and being capable of communicate in wireless. I don't like ComputerCraft because all is cheap (in the sense of no many ressources and no energy are needed), it's for that reason I use OpenComputers instead. ^^
I also read that the 1.4 will be a bit incompatible with 1.3 and will need some manual action. You really can't make these actions automatic? Because I have a server with few players and it will be really hard for me to take these manual actions, especialy if I have to move into the others players base to make these actions. If you really can create a kind of patch of something like that, it would be really appreciate. Thank you in advance! ^^
Keep OCC while you're on 1.3, remove it once you go 1.4. OCC has basically just been integrated into OC itself in 1.4.
Cool! Thanks for letting me know :-)
There are tablets! You can craft them similar to robots, but using a tablet case as the base component in the assembler.
Well, it is mostly automated - as much as possible, really. The required player interaction should for the most part really be a non-issue; as I wrote above, it's just that a player has to pick the blocks that are items at the moment (e.g. in chests) up once, then they're automagically converted. And I'm assuming in >90% of the use cases that'll happen anyway when the player wants to use/place the block.
Just a question, when you will update your mod to 1.4, is there a rist of crash if SGCraft still uses the 1.3.6 API ?
Have I to wait until SGCraft releases a new version? I ask that because I don't know how is the relation between a mod with its APIs.
What do you will add in the version 1.4 ? I'm curious! ^^
a player has to pick the blocks that are items at the moment (e.g. in chests) up once, then they're automagically converted.
What about items kept in automated storage and crafting systems, that the player doesn't usually pick up directly? Will they get automatically converted when needed?
Graaaah, forum software, why are you so horrible? No quotes then. [/rage]
@ExDomino: See this post; in short, SGCraft will probably have to update to the new API or things will go wrong.
@Greg_Ewing: They won't work in auto-crafting; off the top of my head the only case where OC blocks are used in crafting is the server rack, anyway, though, so I think it shouldn't be... too bad? I'm really sorry for the inconvenience, but the old code was getting quite messy, so I decided to use the API break as an occasion to do this transition, too.
@ExDomino/@JoshTheEnder: It's even RC now (as sneakily mentioned here), and yeah, please report any bugs on Github, but mention which version of OC you're using (which you should anyway! ;)).
The Meaning of Life, the Universe, and Everything.
Location:
Montreal
Join Date:
11/21/2013
Posts:
304
Member Details
Sangar, do you think it would be possible to make that wireless signal of computers (and tablets) could pass through a stargate (of the mod SGCraft) when a vortex is connected? If no, there is an option to make a command and an event in the Computer Interface that SGCraft has already implemented and that already works with OpenComputers. But a wireless solution would be nice, in order to create a kind of GDO. ^^
The Stargates (the TileEntity, presumably) could join OC's wireless network to receive wireless network messages on one end and re-broadcast them from the Stargate the receiving one is currently connected to. The relevant methods in OC's API can be found here.
I just tried making the new tablets, however I can't seem to place them in the disk drive to access their hard drive and when I right click with them it says bo bootable medium found. How are you supposed to access their hard disk? If it is with a disk drive, are they bugged?
You need to install OpenOS on hard drive first, before assembling.
Just place disk in computer and type 'install' command. Then select hard's address and confirm.
Voila! You can assemble a tablet.
You can also place them in a charger to access their first disk from computers connected to the charger. The charger kind of acts as a disk drive for tablets. That also charges the tablets. It seemed more logical than placing them in a floppy disk drive.
second, you can maybe add a recipe support to pneumaticcraft (like you did to gregtech)? just make it replace the transistore and pcb with the pneumaticcraft one, becaust he's crafting make much more sense
I personally don't have any experience with Pneumaticraft, so I won't create one myself.
If someone were to contribute such a recipe set, however, I'll gladly include it!
ok, that good, just thought "hey, they both have that things, and the pneumaticcraft one have a better recipe (in my opinion), why not ask the mod developer to add a support to it?"
also, how i put on a changing rcipe config something that have not oredict? NBT will work?
I can't seem to get the Charger to accept any power so I can charge the robots.
Using Ender IO energy conduits to power everything from a resonant energy cell.
Computer is using power just fine from such a cell but the Charger simply shows "Charge Speed: 0%".
I have even tried putting the energy cell right next to the Charger.
Please tell me I am overlooking something simple here.
Well, you are! You need to apply a redstone signal to the charger. Also, if no energy flows even when the charger speed is > 0%, then you can try to use one power converter instead of pumping the energy directly.
Rollback Post to RevisionRollBack
I am a prehistoric histories and manga / anime fan.
I'm working on getting my stargate interface to relay network messages through a wormhole, and I have a bit of a problem.
It's working, but if the two stargate interface blocks involved are within wireless range of each other, packets get bounced back and forth between them. That's not a problem in itself, since it only lasts until the ttl reaches zero, but it means that any computers listening for those messages receive the packet multiple times.
It seems like it will happen in any situation where packets can get gatewayed from one network to another and back again. Is there a way to prevent it? Or do networking programs just have to be prepared to handle duplicate packets?
I'm working on getting my stargate interface to relay network messages through a wormhole, and I have a bit of a problem.
It's working, but if the two stargate interface blocks involved are within wireless range of each other, packets get bounced back and forth between them. That's not a problem in itself, since it only lasts until the ttl reaches zero, but it means that any computers listening for those messages receive the packet multiple times.
It seems like it will happen in any situation where packets can get gatewayed from one network to another and back again. Is there a way to prevent it? Or do networking programs just have to be prepared to handle duplicate packets?
What kind of message you want to pass through the wormhole? Wired message (from a stargate interface to another only) ? Or wireless messages, like the stargate relays the wireless message through the wormhole?
What kind of message you want to pass through the wormhole? Wired message (from a stargate interface to another only) ? Or wireless messages, like the stargate relays the wireless message through the wormhole?
Both. The way I have it at the moment, the stargates themselves relay wireless messages, and the interface will relay wired messages to an interface on the other side.
Either kind of relaying seems to be prone to loops, resulting in packets being received multiple times.
In real life, that kind of thing is handled by protocols like TCP that detect and reject duplicate packets. But I guess OC networking is more like UDP, where the application has to be prepared to handle packet duplication -- is that right?
The Meaning of Life, the Universe, and Everything.
Location:
Montpelier
Join Date:
9/18/2014
Posts:
51
Minecraft:
valaraukador
Member Details
Do you know if this mod is compatible with Resonant Induction? I've noticed issues when both of them try to run at the same time, they will block startup until one of them is removed. I'm presuming it's an API problem?
Creator of OpenComputers. My Twitter. My Patreon.
That's his website: http://www.cosc.canterbury.ac.nz/greg.ewing/minecraft/mods/SGCraft/
Just a question, when you will update your mod to 1.4, is there a rist of crash if SGCraft still uses the 1.3.6 API ?
Have I to wait until SGCraft releases a new version? I ask that because I don't know how is the relation between a mod with its APIs.
What do you will add in the version 1.4 ? I'm curious! ^^
What about items kept in automated storage and crafting systems, that the player doesn't usually pick up directly? Will they get automatically converted when needed?
@ExDomino: See this post; in short, SGCraft will probably have to update to the new API or things will go wrong.
@Greg_Ewing: They won't work in auto-crafting; off the top of my head the only case where OC blocks are used in crafting is the server rack, anyway, though, so I think it shouldn't be... too bad? I'm really sorry for the inconvenience, but the old code was getting quite messy, so I decided to use the API break as an occasion to do this transition, too.
@ExDomino/@JoshTheEnder: It's even RC now (as sneakily mentioned here), and yeah, please report any bugs on Github, but mention which version of OC you're using (which you should anyway! ;)).
Creator of OpenComputers. My Twitter. My Patreon.
Creator of OpenComputers. My Twitter. My Patreon.
Just place disk in computer and type 'install' command. Then select hard's address and confirm.
Voila! You can assemble a tablet.
Creator of OpenComputers. My Twitter. My Patreon.
second, you can maybe add a recipe support to pneumaticcraft (like you did to gregtech)? just make it replace the transistore and pcb with the pneumaticcraft one, becaust he's crafting make much more sense
If someone were to contribute such a recipe set, however, I'll gladly include it!
Creator of OpenComputers. My Twitter. My Patreon.
also, how i put on a changing rcipe config something that have not oredict? NBT will work?
Using Ender IO energy conduits to power everything from a resonant energy cell.
Computer is using power just fine from such a cell but the Charger simply shows "Charge Speed: 0%".
I have even tried putting the energy cell right next to the Charger.
Please tell me I am overlooking something simple here.
Well, you are! You need to apply a redstone signal to the charger. Also, if no energy flows even when the charger speed is > 0%, then you can try to use one power converter instead of pumping the energy directly.
I am a prehistoric histories and manga / anime fan.
It's working, but if the two stargate interface blocks involved are within wireless range of each other, packets get bounced back and forth between them. That's not a problem in itself, since it only lasts until the ttl reaches zero, but it means that any computers listening for those messages receive the packet multiple times.
It seems like it will happen in any situation where packets can get gatewayed from one network to another and back again. Is there a way to prevent it? Or do networking programs just have to be prepared to handle duplicate packets?
What kind of message you want to pass through the wormhole? Wired message (from a stargate interface to another only) ? Or wireless messages, like the stargate relays the wireless message through the wormhole?
Both. The way I have it at the moment, the stargates themselves relay wireless messages, and the interface will relay wired messages to an interface on the other side.
Either kind of relaying seems to be prone to loops, resulting in packets being received multiple times.
In real life, that kind of thing is handled by protocols like TCP that detect and reject duplicate packets. But I guess OC networking is more like UDP, where the application has to be prepared to handle packet duplication -- is that right?