- Welcome to K|W Gaming Community.
We are Simply the Best!
Recent posts
#41
Help / Re: VSP requires PHP Version 7...
Last post by Fragenstein - August 13, 2024, 02:34:47 PMOkay, I upgraded my xampp PHP to v8.2.12 (their latest) and implemented your fix. I was able to get vsp to run, but am getting a bunch of errors:
Code Select
Deprecated
: stristr(): Passing null to parameter #1 ($haystack) of type string is deprecated in
C:\xampp\htdocs\vsp.servegame.com\vsp-q3a.php
on line 697
Warning
: Undefined array key "gameversion" in
C:\xampp\htdocs\vsp.servegame.com\vsp-q3a.php
on line 352
Deprecated
: Creation of dynamic property VSPParserQ3A::$original_log is deprecated in
C:\xampp\htdocs\vsp.servegame.com\vsp-q3a.php
on line 129
Notice
: Only variables should be assigned by reference in
C:\xampp\htdocs\vsp.servegame.com\vsp.php
on line 1086
Skill Definitions not found.
pub/games/q3a/skillsets/default/default-skill.php
[parser options]: Array
(
[savestate] => 1
[gametype] => xp
[backuppath] =>
[trackID] => guid
[xp_version] => 200
)
#42
Help / Re: VSP requires PHP Version 7...
Last post by Krillin - August 13, 2024, 12:26:36 AMHere is a possible solution.
Find (line #1249):
And replace it with:
This will correct the issue with the subversion numbers with 8.2.xx as it was limited to 8.2.00 for some reason. This has NOT yet been published, this will be applied in the next version.
Thank you for your report.
-Krillin
Find (line #1249):
Code Select
function Fff0125cs()
{
if (php_sapi_name() === 'cli') {
if (!defined('PHP_VERSION_ID') || (PHP_VERSION_ID < 70400 || PHP_VERSION_ID >= 80200)) {
echo "Error: VSP requires PHP Version 7.4 to 8.2 to run.\n";
echo " - Your version is: \"" . PHP_VERSION . "\"\n";
echo " - Please upgrade your PHP installation.\n";
echo " - Thank You!";
F4e6F902f();
exit;
} else {
echo "\nYour PHP Installation Will Work With VSP!\n";
}
}And replace it with:
Code Select
function Fff0125cs()
{
if (php_sapi_name() === 'cli') {
if (!defined('PHP_VERSION_ID')) {
// Fallback if PHP_VERSION_ID is not defined
$version = explode('.', PHP_VERSION);
$versionId = ($version[0] * 10000) + ($version[1] * 100) + ($version[2]);
} else {
$versionId = PHP_VERSION_ID;
}
if ($versionId < 70400 || $versionId >= 80300) {
echo "Error: VSP requires PHP Version 7.4 to 8.2.xx to run.\n";
echo " - Your version is: \"" . PHP_VERSION . "\"\n";
echo " - Please upgrade your PHP installation.\n";
echo " - Thank You!\n";
F4e6F902f();
exit;
} else {
echo "\nYour PHP Installation Will Work With VSP!\n";
}
}
}This will correct the issue with the subversion numbers with 8.2.xx as it was limited to 8.2.00 for some reason. This has NOT yet been published, this will be applied in the next version.
Thank you for your report.
-Krillin
#43
Help / Re: VSP requires PHP Version 7...
Last post by Krillin - August 13, 2024, 12:07:25 AMSorry for the delay. There are a few ideas. I will look into this and see what is going on as our development is done using Windows Server 2022 using Apache 2.4.62 with PHP 8.2.16 and there aren't any issues. As it seems your system is not verifying your php version properly.
You need to give me more information on what you are doing rather than this tidbit of information you provided.
Also, update your version of PHP 8.2.4 to 8.2.16. There is no harm in keeping your PHP engine updated to the current version as there could be some minor version detection constant changes in your early version of 8.2.4, because of this there is a fallback written into the PHP Version Detection.
-Krillin
You need to give me more information on what you are doing rather than this tidbit of information you provided.
Also, update your version of PHP 8.2.4 to 8.2.16. There is no harm in keeping your PHP engine updated to the current version as there could be some minor version detection constant changes in your early version of 8.2.4, because of this there is a fallback written into the PHP Version Detection.
-Krillin
#44
Help / [USER ERROR]VSP requires PHP V...
Last post by Fragenstein - August 05, 2024, 01:57:22 PMReceiving the following error when trying to parse the logs:
"Error: VSP requires PHP Version 7.4 to 8.2 to run.
- Your version is: "8.2.4"
- Please upgrade your PHP installation."
VSP v1.0.51
Windows 11 Apache Server PHP 8.2.4
Any ideas?
"Error: VSP requires PHP Version 7.4 to 8.2 to run.
- Your version is: "8.2.4"
- Please upgrade your PHP installation."
VSP v1.0.51
Windows 11 Apache Server PHP 8.2.4
Any ideas?
#45
VSP™ Download / Media Files Half Life (UPDATED...
Last post by Krillin - August 04, 2023, 11:47:01 PMThese are the HALF LIFE media kits in ZIP and 7z form. These are the base game map, icon and weapon sets.
#46
Downloads / Widescreen 16:10 Menus Offset ...
Last post by Krillin - July 02, 2021, 08:59:01 AMThis 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, fix_widescreen_alignments.zip, 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.
Sincerely,
Krillin
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 Steampowered.com 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
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, fix_widescreen_alignments.zip, 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.
Sincerely,
Krillin
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 Steampowered.com 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
#47
Help / Re: php is changing 7.2 gives ...
Last post by Krillin - March 03, 2021, 10:54:53 PMSo 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.
Thanks.
Thanks.
#48
Help / Re: [HELP] PHP Warning: Illega...
Last post by Krillin - February 22, 2021, 12:17:22 PMA 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 phpfreaks.com a user named "kicken" came back and said that the line where the issue was happening #979, needed to be replaced with;
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,
Krillin
At phpfreaks.com a user named "kicken" came back and said that the line where the issue was happening #979, needed to be replaced with;
Code Select
$V0f14082c['parser-options']=array();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,
Krillin
#49
Help / Re: [HELP] PHP Warning: Illega...
Last post by Krillin - February 21, 2021, 10:02:57 AMWas 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.
Back to waiting for another response, even though the function was posted with the line in there.
Krillin
Code Select
$V0f14082c['parser-options']="";Back to waiting for another response, even though the function was posted with the line in there.
Krillin
#50
Help / Re: [HELP] PHP Warning: Illega...
Last post by Krillin - February 20, 2021, 08:08:59 AMI reached out to the wonderful people at phpfreaks.com for assistance. I will post back here for the record.
phpfreaks.com
phpfreaks.com