http://pastebin.com/BensX0JL

Using a day old source ( https://github.com/MrTJP/ProjectRed/tree/33783bf2940b252b4b4213104f37d172477b8f64 )
With auto-installed versions of CCL,CCC,FMP,NEI.
Using forge 9.10.0.829 (same as in build.xml) kindly provided by rosshadden instead of running install-forge, because the decompilation step is just doing strange things for me.
That is unfortunately preventing me me from compiling the current github version, since it's using new forge.

I do have the same versions of CCL,CCC,FMP in minecraft as in build.xml
But forge is 9.10.0.847.
no NEI. It's optional, right?

Did I do something wrong?
There were no changes to timers/Guis since that version.
Rest of the mod including an alloy smelter gui is working fine.

Update:
Now running https://github.com/MrTJP/ProjectRed/tree/414974d699ad1083797d80aa862d9200a8598cee
"Made bus transceiver bundled cables connect internally."

Which means I am only these commits behind:
Just fix a little OOP convention thing.
Updated versioning
Update name mappings
Added neighbor tile change response to comparators. (This one needs newer FMP than in build.xml, I guess)

The error has not changed

I would rarely update forge if it wasn't needed. The problem is that in the latest forge, method names for loading assets changed. So, when the GUI tries to access the background png file that it needs, it crashes. You'll need to update Forge.

Did you test on any Linux?
(Those doubled-up slashes were not causing trouble on windows..)

It could of course be the way I am building them.
But I can never know unless someone sends me finished jars that are supposed to work.

Perhaps if you can either send me a crash report or tell me specifically where the double slashes are..

The crash report is in the very first post, but OK, I made a fresh one with current versions:
http://pastebin.com/KMrCygAP

It's probably not about slashes, it just could be Linux-only like as with the slashes

I still crash on opening counter GUI
This time using up-to-date github version and versions of things from build.xml (except not-installed NEI)
correction: I was unable to find ccc 0.9.0.5_d1, so I am using 0.9.0.5 in MC

My forge source could be installed with --no-assets, could that be it?

What about doubled-up slashes as in the past with textures?

As far as i know, there aren't anymore double slash textures anymore.

And you need the latest FMP and CCLib.

name="mc.version" value="1.6.2" />
name="forge.version" value="9.10.1.849" />
name="ccl.version" value="1.0.0.29" />
name="ccc.version" value="0.9.0.5_d1" />
name="fmp.version" value="1.0.0.158" />
no NEI

so these are not new enough?
OK, will try with current latest

Latest FMP (1.0.0.161)
Latest CCL (1.0.0.29)
no NEI

Nothing changed, still crashes the same way.

I looked at MC console output, but found no clues.

Just tested, all working. Must be an issue with your setup.

I tried commenting out TimerGUI's lines that use "mc"
And I got "noSuchMethod: fontRenderer"

But it works fine for GuiBackpack.
I drew (for sure useless for you) map of classes for GuiBackpack and GuiTimer up to the common ancestor

This could be important
I un-jarred all the jars and did this:

grep -rl fontRenderer .
./mrtjp/projectred/integration/GuiCounter.class
./mrtjp/projectred/integration/GuiTimer.class
./mrtjp/projectred/core/BasicGuiUtils.class

Note that GuiBackpack (where fontRenderer works) is not listed
While fontRenderer fails for GuiCounter and GuiTimer which are listed

Quick question to MrTJP, when you say it works fine for you, do you mean
running debug in dev environment? Cause it works fine for me that way, but
gives the same crash

java.lang.NoSuchFieldError: mc
at
mrtjp.projectred.integration.GuiTimer.drawBackground(GuiTimer.java:44)
at
codechicken.core.gui.GuiScreenWidget.func_73863_a(GuiScreenWidget.java:65)
at
net.minecraft.client.renderer.EntityRenderer.func_78480_b(EntityRenderer.java:1036)
at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:942)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:834)
at net.minecraft.client.main.Main.main(SourceFile:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:57)
at net.minecraft.launchwrapper.Launch.main(Launch.java:18)

when compiled and run through actual play, not dev debug. Also the same
crash for Sequencer (exact same) and Counter
(GuiCounter.drawBackground(GuiCounter.java47) for the first line, only
difference). I'm using Forge 9.10.1.852, ChickenLib 1.0.0.29, CCC 0.9.0.5,
and FMP 1.0.0.161

On Fri, Sep 6, 2013 at 3:58 PM, Iree [email protected] wrote:

Another thought: Could going through CCC confuse the reobfuscation?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/99#issuecomment-23965277
.

I get the same error. I did not spend much time on it (just wanted to see if @Iree was alone), but these are the versions of the dependencies I was using with Minecraft itself to test:

• Forge 9.10.1.853
• ForgeMultipart-universal-1.6.2-1.0.0.161.jar
• CodeChickenCore 0.9.0.5.jar
• CodeChickenLib-universal-1.6.2-1.0.0.29.jar (auto-downloaded by forge)

If it helps, I am using java-6-oracle on Ubuntu 13.04 to compile.

Well, THANK YOU, for that crucial piece of information. Now since i know its working in dev and not in an actual installation, i think i know whats causing it. I have a fix in local branch, but can't test it until Chickenbones' web site is back up.

Yeah, I figured there was a little misunderstanding/miscommunication
there. Glad to hear you think you've got it, looking forward to the push!

On Fri, Sep 6, 2013 at 7:52 PM, MrTJP [email protected] wrote:

Well, THANK YOU, for that crucial piece of information. Now since i know
its working in dev and not in an actual installation, i think i know whats
causing it. I have a fix in local branch, but can't test it until
Chickenbones' web site is back up.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/99#issuecomment-23976550
.