View Issue Details

IDProjectCategoryView StatusLast Update
0000106Industrial-Craft²E-Net, cabling, storage/transformer blockspublic2013-02-06 08:23
ReporterfrancogpAssigned ToPlayer 
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version 
Target VersionFixed in Version 
Summary0000106: Luminator cant be placed in cables
DescriptionSimple. Try to place a luminator on the floor or on a cable. It appear one block higher.
Tags1.109, 1.110
Minecraft Version

Relationships

duplicate of 0000173 closedPlayer Luminator alignment wrong on placement 
duplicate of 0000290 closedPlayer The luminator is can attached only to the bottom of the any wire or any block. 
related to 0000245 closedPlayer Luminator disappear if you place it next to another 

Activities

biomatter

2012-12-08 13:49

reporter   ~0000400

I can confirm this. Luminators do not attach to my foamed copper wire - or anything, actually. Power is running through them but they do not receive it, and if a luminator is placed adjacent to a glitchy one they both annihilate themselves.

Scors

2012-12-09 23:27

reporter   ~0000410

Luminators may appear one block higher but are actually placed in a ceiling position. They will connect and act normally if the cable is directly above but otherwise will act as if they are being placed on a non-existent ceiling. Energy net supplies power with this setup.

Wild1145

2012-12-20 22:36

reporter   ~0000523

Looks to be a visual bug and not a actual thing that you can fix!

happy2pester

2012-12-21 23:56

reporter   ~0000532

I can confirm this happens to me too. MultiMC's console reports no issues, either when placing the Luminators, cables, etc, or loading a world with glitched luminators already in

musznik

2012-12-25 20:00

reporter   ~0000568

I think its related to RedPower 2 API, and microblocks

immibis

2012-12-26 07:16

reporter   ~0000571

@Wild1145: ...what?
@musznik: ...what?

BC lasers had a similar problem where they were always placed facing down. It was a simple fix, caused by a method changing its name and signature. Perhaps this is related. The BC problem was fixed by this commit: https://github.com/psxlover/BuildCraft/commit/3d612a13333506de16f7415d4cafa291f9ebda20 (ignore the files other than BlockLaser)

musznik

2012-12-26 10:35

reporter  

lum.jpg (59,964 bytes)
lum.jpg (59,964 bytes)

Novalis

2012-12-28 12:16

reporter   ~0000583

I can confirm this. Nothing to do with RP2.(dont use it) Still there in open beta 1.4.6

happy2pester

2012-12-28 17:41

reporter   ~0000587

@musznik: I also don't have RP2 on this installation - It's 1.4.5 - No RP2 for 1.4.5 is available as far as I'm aware.

Player

2013-02-06 08:22

administrator   ~0000768

should be fixed in build 217-lf and later

Issue History

Date Modified Username Field Change
2012-11-25 08:11 francogp New Issue
2012-12-08 13:49 biomatter Note Added: 0000400
2012-12-09 23:27 Scors Note Added: 0000410
2012-12-18 05:00 francogp Tag Attached: 1.109
2012-12-18 05:00 francogp Tag Attached: 1.110
2012-12-20 22:36 Wild1145 Note Added: 0000523
2012-12-21 23:56 happy2pester Note Added: 0000532
2012-12-25 20:00 musznik Note Added: 0000568
2012-12-26 07:16 immibis Note Added: 0000571
2012-12-26 10:35 musznik File Added: lum.jpg
2012-12-28 12:16 Novalis Note Added: 0000583
2012-12-28 17:41 happy2pester Note Added: 0000587
2013-02-06 08:18 Player Status new => closed
2013-02-06 08:18 Player Assigned To => Player
2013-02-06 08:18 Player Resolution open => duplicate
2013-02-06 08:18 Player Relationship added duplicate of 0000040
2013-02-06 08:22 Player Relationship deleted 0000040
2013-02-06 08:22 Player Note Added: 0000768
2013-02-06 08:22 Player Status closed => resolved
2013-02-06 08:22 Player Resolution duplicate => fixed
2013-02-06 08:23 Player Relationship added duplicate of 0000173
2013-02-06 08:23 Player Relationship added related to 0000245
2013-02-06 08:23 Player Relationship added duplicate of 0000290