Posts by RawCode

go down and check, also reloading miner helps.

it's random, it may stay not hardened literally for ages due random roll.

there is no redpower for 132.

your information outdated

in computer sience same actions lead to same result, no matter how many times you decompile result will be same and it will be with errors.

i will patchout this from 107 ever if devs not provide option to disable, quantum food is gamebreaking.

skylight casting not supported by current chunk format and none will alter chunk format.

Quote

999999999999Eu/t

just use long for this...

everything we need is rod's regenerator made of hurge amount of uran (similar to CF Pack) and when placed inside reactor GUI, time to time regenerate uran rods, this will effectively fix every possible problem with reactor refuel at cost of 1 slot.

outdated? hm lol, i just opened download page and dont see any 107 test download, soo it's perfectly accurate.

ofc you dont need to use search button and report same bug all the time ignoring threads with possible solution or fix.

[106] BUG Compilation thread

you used search button wrong.

they give 2 uses inside CF pack...

sprayer gone async since it's code executed locally, this reported to be fixed in 107

search button

t4 already...

Quote

I'm just going to assume you're trolling.

just do what you want, none trolling here (this thread).

Case 1: you dont know how block works and does not have source, so you not able to implement anything inside it's class, but want to debug this block:
А) You code something generic and execute it, this possibly will reveal data you want.
B) You hardcode params you need from block into your debugger and debug. (CURRENTLY IN IC2)
C) You implement your own "interface" and allow user to map data into it via config or runtime. (HOW BUKKIT AND FORGE WORKS)

Quote

That's complete overkill

This way how forge and bukkit works, it may be overkill but this "industrial" (IRL) standart of software development

nothing to do with console here actually.

Quote

The debugItem then tests the isDebuggable() method return and, if it's true, gets and prints the status message; if it's false, it can safely ignore it and continue on its merry way (for that click).

useless code bloat, single method than return status message on demand, no additional calls, no additional checks request>answer, you going to execute method to check other method output and then again execute other method and again get it's output...

block can choose anything inside status request handler...

Quote

debugItem's code itself and is best left to the mod implementing the interface: which is exactly as it should be

you just completely ignore option to debug blocks that naturally does not support debugger, with your suggested implementation only blocks coded with interface will be debuggable and NONE will download and install your interface if everything that allowed by it is single method with already known name.

reactor style gui te

*we* can do anything, there is no limits, two possible methods exist:

add debug code into TE code
add debug code into Debug code
add eventhandler and register debuggers inside it, on execution enumerate every registered debug handler

3rd method is best, since you may register debug code for one class into other class, ever inside addons, without any need to edit original TE code.

Quote

If you always want to return a status, it's as simple as always returning true from isDebuggable().

without interface method class implementing interface WONT COMPILE and wont return INSTANCEOF

there is COMPLETELY no reason to check isDebuggable after checking instanceof

ps will wait for 107 or possibly other stable version to develop anything larger then 100 lines.

dynamite is useless, too weak to clean up anything harder then netherack.

why you want shortcut recipe for it?

cant confirm, pump working well with world-chunk unloading and normal operation routine.

possibly TS cant understand simple fact - pump will take liquid block from world...

USE			TABS		BTW
			NOT		BTW
			SPACES		BTW
TileEntity te = world.getBlockTileEntity(x, y, z);
assert te != null; //MUST BE HERE
if (te instanceof ICustomDebug)
{
	IC2.platform.messagePlayer(var2, te.execute())
}
package ic2.api;
public interface ICustomDebug
{
    string execute();
}
string execute()
{
	return this.field.toSting()
}

I would implement something like this to allow much more flexible CustomDebug method.

If block lack CustomDebug interface, we can list EVERY field also we can do this with method invocation without use of API or interface, but at cost of speed.

Quote from Kane Hart

Don't worry is was not forgotten. That was a small list of bugs that they have fixed so far. Here is more details on what is done and of course more to come:
Quantum Helm Poison Crash.
Phantom Wires with enet.
Overcharging Infinite Explosions
Superheat on ores
Sheering Sheep
Drained Items
Geothermal Liquids
CF Backpack
Apples Falling From Rubber Trees
Soulsand drill speed
Foam Can Be silk touched

Display More

can't see reason to report again bugs reported from other threads in thread reporting same bugs once again (3rd time)

just
	use
		tabs

it actually already implemented as interface, just hardcoded into base class.

it registered as wooden tool.