Thanks, but that did not work either. :(

Please post a screenshot with what you have displayed on your site, related to the hack.
First, search the html code and tell me if you see in the source:
<!-- {vbmicrostats} -->

Then, go to vBulletin Options > BB MicroStats
Make sure the options you desire are enabled (the first option enables the hack).
We will get this baby working, is something minor ore;se it would not work on previous code edits.

Just for the heck of it, what version you had installed before 1.1.0?
Thanks.

Edit: You still have the problem related to installer? It looks like there are some leftovers in the database, you probably installed over the old old hack, without un-installing first.
Is OK we can clean this.

Just post all details here, I need screenshots to your plugin table.

http://img119.imageshack.us/img119/3060/screenvblg2.gif
When i click view source and search for <!-- {vbmicrostats} --> it does not show up(or did you mean in the template?).

I had 1.0.3 installed before 1.1.0.

Plugin table
http://img407.imageshack.us/img407/8616/tablebl7.gif

Ya, in the HTML source, you are all good. :)
Sorry, I was not clear... I presumed you will show me the actual data from the plugin table.
Anyways, the process is really simple to clean your board. Do this:

1. Uninstall the hack.
Plugins & Products > Manage Products > vBMicroStats > Uninstall

2. Revert the footer template to default like before.

3. Upload the original vBulletin 3.6.5 class_core.php and init.php files to your server.
We do this just to make sure there are no code mistakes.

4. Close the board.

5. Open config.php and find the following line:
$config['Misc']['maxheight'] = 1944;

Replace it with:
$config['Misc']['maxheight'] = 1944;
$config['Misc']['debug'] = true;

Mod Debug should be enabled now.
If you have the Admin CP still open, just refresh once (F5) the current admin page in your browser.

6. Run the following queries (yes, you can run them all at once):
[sql]DELETE FROM `phrase` WHERE product LIKE '%vb36_mstats%';
DELETE FROM `product` WHERE productid LIKE '%vb36_mstats%';
DELETE FROM `productdependency` WHERE productid LIKE '%vb36_mstats%';
DELETE FROM `plugin` WHERE product LIKE '%vb36_mstats%';
DELETE FROM `settinggroup` WHERE product LIKE '%vb36_mstats%';
DELETE FROM `setting` WHERE product LIKE '%vb36_mstats%';[/sql]

That will clean your database from all vBMicroStats leftovers. :)

7. Rebuild the bitfields.
vBulletin Options > Rebuild Bitfields

8. Disable Debug Mode.
You can simply set the Debug option to false, it will take care of the rest for you:
$config['Misc']['debug'] = false;

9. Log out and login into Admin CP.

10. Open the board, you are done. :)

Do I have to revert the footer or simply delete the code for microstats?

Delete the microstats code.

I forgot to mention, the above procedure, will simply revert your bulletin board to it's original state, before you ever installed vBMicroStats.
It's like my hack was never there.

Also, keep in mind that all errors you get now are not related to my hack.
vBMicroStats does not affect in any way the vBulletin (forum) options or functionality.
But I wanted you to feel better and make sure the database is cleaned properly, in case we have some code left there.

2. Revert the footer template to default like before.
My templates will not update because of the bug.

4. Close the board.
It would not even save the status of the board being closed.

6. Run the following queries (yes, you can run them all at once):
[sql]DELETE FROM `phrase` WHERE product LIKE '%vb36_mstats%';
DELETE FROM `product` WHERE productid LIKE '%vb36_mstats%';
DELETE FROM `productdependency` WHERE productid LIKE '%vb36_mstats%';
DELETE FROM `plugin` WHERE product LIKE '%vb36_mstats%';
DELETE FROM `settinggroup` WHERE product LIKE '%vb36_mstats%';
DELETE FROM `setting` WHERE product LIKE '%vb36_mstats%';[/sql]
It claims the data was deleted.

8. Disable Debug Mode.
You can simply set the Debug option to false, it will take care of the rest for you:
$config['Misc']['debug'] = false;
Debug mode is still on despite doing this.

This is the only hack that modifys debug mode though so i do not see where else it could come from but I guess i will try my other hacks.

Oh and another note that when i try to click explain, it simply reloads the page which is the bug I notified you of here

Hell i can not even disable hacks manually in the admin cp. Only by editing config. :(