View Issue Details

IDProjectCategoryView StatusLast Update
0002054Industrial-Craft²tools / electric itemspublic2016-12-08 22:36
ReporterDullSpoonAssigned ToChocohead 
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionno change required 
PlatformPCOSWindowsOS Version8.1
Product Version 
Target VersionFixed in VersionBuilds for MC 1.10.x 
Summary0002054: Can't change modes on Mining Laser
DescriptionRemapped the key binding from 'm' to 'q', but that didn't help. Tried every combo of the shift and control keys with it too. Am I just missing something?
I can hover with the jetpack, so its use of the mode key works.

The GUI isn't listing any key binding conflicts with any other mods.

Reviewing the other bug reports, I can confirm that I can now recharge my Mining Drill with right-clicking on a RE Bat, but only at 0000027:0000050 EU/sec (perhaps 32 EU/t?). So at that rate it would take approx 3.33 minutes(or 5.2 mins) to empty the battery. This seems too slow. Would this be a another bug? Or are batteries used in this fashion suppose to be for emergencies only and instead the player should use the BatPack?
Steps To ReproduceForge 1.10.2-12.18.3.2185
Mod: industrialcraft-2-2.6.125-ex110.jar
(Ok, this bug breaks the posted rules about posting 1.7 bugs only, but build 0000105 is the version up on Curse. I pulled down build 0000125 and its still happening.)
Additional InformationRunning the following mods:
Bookshelf1.10.2-1.4.3.338.jar
EnchantingPlus-1.10.2-4.1.0.115.jar
industrialcraft-2-2.6.125-ex110.jar
journeymap-1.10.2-5.3.1.jar
Railcraft_1.10.2-10.0.1.jar
TagsNo tags attached.
Minecraft Version1.10.2

Activities

Chocohead

2016-12-08 22:36

developer   ~0004921

The mining laser's mode is switched by holding down the mode key then right clicking.

RE-Battery charging is naturally quite slow as it has a low transfer rate, which when the drill's is quite low too means it will take a while. Batpacks or charging batteries are better options if you're trying to store extra energy for your tools.

Where's the rule about only reporting 1.7 bugs? It should definitely be changed by now as 1.10 is where the dev focus is now.

Issue History

Date Modified Username Field Change
2016-12-08 19:28 DullSpoon New Issue
2016-12-08 22:36 Chocohead Note Added: 0004921
2016-12-08 22:36 Chocohead Status new => resolved
2016-12-08 22:36 Chocohead Fixed in Version => Builds for MC 1.10.x
2016-12-08 22:36 Chocohead Resolution open => no change required
2016-12-08 22:36 Chocohead Assigned To => Chocohead