i really want this too work :( any ideas?

Your path seems likes it is wrong, make sure the line in index.php:

points to your main forum install directory.

Just added this to the install file:

The explanations for the eirc template configuration options:

* mainbg
Most components background color. Defaults to system settings.

* mainfg
Most components foreground color. Defaults to system settings.

* textbg
Text area and field background color. Defaults to system settings.

* textfg
Text area and field foreground color. Defaults to system settings.

* selbg
Selected text background color. Defaults to system settings.

* selfg
Selected text foreground color. Defaults to system settings.

* channel
What channel should be automatically opened when a connection is established.

* titleExtra
This is concatenated to the channel or user's name to form the window's title.

* username
What "user name" -sometimes called userid or ident- will be passed to the server. Defaults to vbulletin users usersname.

* realname
What "real name" will be passed to the server.

* nickname
What "nick name" will be put in the nick field at start up. If the character '?' is used somewhere in the VALUE field, it will be changed to
a random number by the client on load. Defaults to vbulletin users usersname.

* login (requires "nickname")
If it's set to anything but "0", it will try to establish a connection to the server on start up.

* spawn_frame
Whether to launch the main window on a separated frame, thus reducing the space needed by the Applet on the webpage and allowing the window
to be resized dynamically.

* frame_width
Sets the width used by the spawned frame.

* frame_height
Sets the height used by the spawned frame.

Then why release it as a full release? Didn't you test (&beta) it?

it worked for me from his first release... if u have a lil bit brain it will work from 1st time... no offence...

What cause I try and help someone with a problem I cop a earfull??? Oh no, I had to tell someone to chmod a file... oh my, its the end of the world... There was/is nothing wrong with the hack itself, it works fine and yes I tested it, I simply forgot a couple steps in the install docs.. sheesh sorry.

I've been hanging around this forum since it opened and maybe it's people's like you and your attitude around here when posting, which is slowing down the release of hacks. I for one will think twice before releasing anything again here, I had hoped sinced so many where after this hack and its was downloaded 30+ times in the first 12 hours of release, that I may have had more than 1 user thank me, but I guess this place has changed alot since vbulletin.com days. After reading some other hack threads on here, My next hack I may just keep to my little circle of friends and not release at all....

That is noncense.

andrew67, Xiphoid asked a perfectly valid question, on perfectly valid grounds, yet you insult him and go off shouting stuff like "this place has changed a lot" and what not.

I won't miss it when you will think twice before releasing another hack. I can't say your attitude is likeable at all, and you admitted to having forgotten a few steps in the install. Nice going. Remind me not to look at your hacks until all problems are solved and people got it working, with proper instructions.

Thanks & Gratitute go along way in this world. Woopee I made a mistake, you must never make mistakes, you are so perfect... Frigg this, I am removing this hack, I will release it to a more gratefull bunch of people.

Andrew... allow me to be the voice of reason: Many of us were happy to see an EIRC integration hack come onto the scene and many of us don't see it as necessarily being a life and death issue if the hack doesn't work perfectly right out of the box.

However, the proper order of things is to place a new hack in Beta before you announce it as a full release. Even if the hack works flawlessly on your site, it is wise to put it into beta for a few days just to work out any kinks that may arise.

In this case, you obviously had to go back and re-address some issues with the documentation. Not a big deal, but there are always going to be people who want to bust your balls about this sort of thing. Having put this into beta would have given you that opportunity to work the kinks out with the users understanding that there might be problems in the release.

Putting a hack into beta before you release it to the public is just a smart practice to adhere to and, if done, gives you a basis to tell people to STFU whenever the whining begins. ;)

So don't let a few complaints spoil this for you. Keep releasing your work knowing that there are people who appreciate it, but follow through with a beta cycle first.