Recent Posts

Pages: [1] 2 3 ... 10
Help / Re: [SOLVED] Missing country flags column
« Last post by Krillin on July 14, 2022, 03:31:11 AM »
You come here asking for support and you are not even using an official version of VSP and using illegally as well. You really should be ashamed of yourself!!

User has been a member since 2011 and is now banned due to issues posted above.

Help / Re: Missing country flags column
« Last post by Fragenstein on June 04, 2022, 06:50:50 PM »
Nevermind. Figured it out. In Bismark folder>settings.php
Code: [Select]
//change: display/hide country flags
Help / [SOLVED] Missing country flags column
« Last post by Fragenstein on May 31, 2022, 12:04:29 PM »
I see that on this site
the country flags column is listed, but on my stats page there is no country flags column. I checked my log files and the countries are being picked up. Any ideas?
VSP Download / Re: vsp stats processor v0.50 [UPDATED 5/1/2022]
« Last post by Fragenstein on May 31, 2022, 09:55:51 AM »
[UPDATE: 5/1/2022] Replaced attachments due to complaints of file corruption. /pub/configs/sfg-default.php Seems to happen frequently with different files. Fixing issues like these regularlly with different file names.

Hi Krillin,
I just tried to update my  ExcessivePlus Community version 0.45-xp-1.1.2 to your v0.50 version.
It didn't work. I uninstalled everything, and retried. I found out that files are still corrupt. For instance, vsp.php showed nothing but NUL NUL NUL. I tried the .zip and the .7z. Tried unpacking with 7z and PeaZip. Same results.
Downloads / Widescreen 16:10 Menus Offset Fixed
« Last post by Krillin on July 02, 2021, 08:59:01 AM »
This WAS posted at steam community SEVERAL times, and several times it has been taken down. Due to file corruption from my hosting company. I am looking for a new one at this point!

Being as the Engineers / Developers are no longer doing anything to CS 1.6 or CZ these days. We had to come up with a solution for our Screen Interface for our games with a 16:10 RATIO. I am happy to say we did, and did so successfully.

Attached to this post below,, are all the files needed to fix the offsets MOTD + Menus for players with Widescreen 16:10 aspect ratio monitors.

If by some chance these files don't work for you, just delete them and they will go back to square one. (Use with caution with the new HD update in March of 2013, deleting these files can leave your interface blank.)

Place the contents of the /resource folder contained in the .zip file attachment into your "../../counter-strike/cstrike" or "../../condition-zero/czero" installation folder(s). Overwrite the existing files when needed, or make a backup copy of the originals.

You use these files at your own risk. But we assure you there isn't any risk at all. These files are modified from the counter-strike.gcf files delivered to you from steam. Only modified the specific Numeric Values to place the required items on our screens properly. Nothing is inserted into these files or contain anything extra.

Hope you enjoy the 2 days of dabbling around and 14 months of bullshit and runaround from STEAM's NON-TECH SUPPORT and LAME-O DBA's who conveniently lost my account between January and April of 2008 when we hadn't heard any progress of our findings! That is because steam conveniently deleted ALL support tickets on my and many others accounts.

Added screenshots of the layout for the Before MOTD/Select Team And After MOTD/Select Team.


Reason for Edit: Fixed the download, made it easier for players to unzip, cut & paste and go. The no hassle method. Added more info and link to steam forums, tested on Condition-Zero and past. Minor grammar and flow corrections. Updated Links seeing as forum entries were DELETE/REMOVED (first one above). Re-posted in two forums this time around.

Our Apologies for those who are looking for this fix, we did not know the files were missing. This is now been resolved. 7/2/2021
Help / Re: php is changing 7.2 gives errors [SOLVED]
« Last post by Krillin on March 03, 2021, 10:54:53 PM »
So I thought this was a simple fix, but it was the wrong fix. This has been fully addressed properly according to PHP 7 documentation regarding this issue. Though Class and Function still cannot have the same names, there is a right fix for this and it has been implemented in V.S.P. v0.50 properly along with a lot of other fixes.

VSP Download / Re: vsp stats processor v0.50 [UPDATED 3/2/2021]
« Last post by Krillin on March 01, 2021, 03:24:53 PM »
Learned of a slight typo which stopped VSP dead in it tracks. I have addressed this. There is another issue I am dealing with so the files were pulled. I am currently working on the issue but I am chasing down a ghost here.

Files have been reposted with the correct Function() call corrected. This function checked your PHP version number being as this requires version 7.0.0 or later.

I have gotten Xdebug working on my development machine and I was able to see any and all errors within the files as drawn within the browser. All these issues were addressed to get V.S.P. 95% error free in functionality. Updating PHP to 7.4.16 surfaced other issues. Performance for V.S.P is going to have to wait, as I have a lot more learning to do.

There is one last issue:
1) Must run vsp with SAVESTATE 1 or you will get a warning message with Illegal Offset String 'trackID' error. The fix is the same as the SAVESTATE issue, but if the string is placed in the script twice the 'savestate' and 'trackID' is ignored altogether.

0) It was also noted there is an issue with vsp-hl.php in line #97 fread is throwing a warning. This warning was only shown because there was a file in the folder (_YourLogFilesHere) that was EMPTY - 0 Bytes. So this is really nothing to worry about, but may write a code to check the file before processing it as soon as I figure out which variable to check.

Learned of an issue with the password with vsp in web mode. Any password could have been used to run. This was a missing '(' on line 1120. This has been corrected and all password checks work now. So if you downloaded v0.50 before 3/4/2021 at 5:30 PM Eastern then you will need to get the current posted download. Sorry for the mishap. I will keep updating issues as necessary.

I took this for a test run on PHP 8. And I got to say, it doesn't look good, it doesn't look good at all! I have WAMP as my development server with PHP 8.0.0 and 8.0.3 and I tested vsp in web mode, and every single file it was reading & processing had warnings and errors. This is not going to be pretty as we may be talking about a rewrite?! Perhaps the end of (BETA)? That depends on how much help I can get! As I stated, I am not a programmer and I do not know what PHP is doing nor do I understand why, but I am not afraid to tackle projects like this.

There were a hand full of typos in the code for the cosmetics but one mishap had to do with the VSP Version data bits which the /pub/ files pull from the database and it did not match. This was corrected. And I put a new enhancement feature in the /pub/ from the v0.51 release. If you downloaded this before 3/8/2021, I suggests you pull the latest set from above!

If you find any problems, please let me know.

Help / Re: [HELP] PHP Warning: Illegal string offset [HELP]
« Last post by Krillin on February 22, 2021, 12:17:22 PM »
A second reply gave us a clue as to what was needed to in order to get the "savestate" function working once again. I believe this has broken since PHP 7 came out, we just never knew it.

At a user named "kicken" came back and said that the line where the issue was happening #979, needed to be replaced with;
Code: [Select]
Well, I tired that. Nothing changed, except the error message went away. In verifying the /logdata/ folder, nothing was being created in it telling me this was not the fix. So I replaced the line #957 with the above. No change there either. I tired a few more other things, just taking some guesses and nothing seemed to work the way it needed to.

So, I stared at the screen for a few and thought to myself. Yes, it needs they array. So I added the given line above the problem line #979. Saved it, copied the saved file to the production server. Ran the file, and to my surprise, you see the information about Hash file not found. Two lines I have not seen in a very long time. The savestate function is working once again!

One user did warn that this may cause other issues. And he was right. Because this statement is only stated in the "parser-options" section, if SAVESTATE 1 is NOT ran, the error message appears with the 'trackID' now.

Thanks the two users are thanked for their assistance in the _Docs/ChangeLog.html file. (One of the changes coming to vsp-core_v0.50).

Best Regards,
Help / Re: [HELP] PHP Warning: Illegal string offset [HELP]
« Last post by Krillin on February 21, 2021, 10:02:57 AM »
Was given a first attempt to fix this, but the solution was to change a line to code that is already posted on line #957 of vsp.php.

Code: [Select]
Back to waiting for another response, even though the function was posted with the line in there.

Help / Re: [HELP] PHP Warning: Illegal string offset [HELP]
« Last post by Krillin on February 20, 2021, 08:08:59 AM »
I reached out to the wonderful people at for assistance. I will post back here for the record.
Pages: [1] 2 3 ... 10