+
+
+
diff --git a/parts/titletable.php b/parts/titletable.php
index a2eea87..3e2fed3 100644
--- a/parts/titletable.php
+++ b/parts/titletable.php
@@ -1,18 +1,18 @@
-
-
+
+
-
-
+
+
|
-
+
-
+
|
diff --git a/parts/topmain.php b/parts/topmain.php
index 31f0419..478fb8f 100644
--- a/parts/topmain.php
+++ b/parts/topmain.php
@@ -1,18 +1,8 @@
-' .
- '' .
- ' ' .
- ' | ' .
- ' ' . $pagename . '' .
- ' | ';
- }
function iconLink ( $url, $img, $desc, $border )
{
@@ -38,16 +28,27 @@
echo ' ';
}
- textBar($pagename);
- echo ' ';
- iconBar($focused);
- echo ' | ';
- echo ' ';
- echo ' ';
- tableSpacer( 1, 4, 1, "black");
- echo ' ';
- echo ' ';
- tableSpacer( 2, 1, 2, "white");
- echo ' ';
- echo ' ';
+ function topBar($pageName)
+ {
+ global $focused;
+
+ tableHeader("100%", "black");
+ echo ' |
-
-
-
+
+
+
+ |
+
-
-
-
- |
-
- | | | ' .
- ' ' .
- ' | | | ';
- }
-
- function progressMeter( $name, $pct, $comments )
- {
- $result = '';
- $result .= '| ' . $name . ' | | ';
- $result .= ' ';
- $result .= barGraph( $pct );
- $result .= ' | | ' . $comments . ' |
|---|
';
- echo $result;
- }
+ function progressKey() // Display key for progress bar
+ {
+ echo '| | | ' .
+ '' .
+ ' | | | ';
+ }
- tableBoxHeader( 'black', $tableHeadColor );
- tableTitle( 'Progress', 3, $tableHeadColor );
-// tableBoxHeader("Progress", 3, 'white', '#737b9c', 'black');
- echo '| ';
- tableHeader(3, 'black');
- progressKey();
- progressMeter('3Dfx MiniGL', 85, 'Being replaced by Mesa where possible');
- progressMeter('DOS', 65, 'Working on DJGPP cross-compilation');
- progressMeter('GGI', 90, 'New cross-platform software standard?');
- progressMeter('GLX', 95, 'Working properly');
- progressMeter('MGL', 80, 'No comments');
- progressMeter('SDL', 90, 'New cross-platform software standard?');
- progressMeter('Sun XIL', 50, 'Unknown status');
- progressMeter('SVGAlib', 85, 'No comments');
- progressMeter('WGL', 70, 'No comments');
- progressMeter('X11', 95, 'Working properly');
- progressKey();
- tableFooter();
- tableBoxFooter();
- ?>
- |
-
-
-
- |
-
-
-
- |
- | ' . $name . ' | | ';
+ $result .= '';
+ $result .= barGraph( $pct );
+ $result .= ' | | ' . $comments . ' | ';
+ echo $result;
+ }
+
+ tableBoxHeader( 'black', tableHeadColor );
+ tableTitle( 'Progress', 3, tableHeadColor );
+ echo '| ';
+ tableHeader("100%", 'black');
+ progressKey();
+ progressMeter('3Dfx MiniGL', 85, 'Being replaced by Mesa where possible');
+ progressMeter('DOS', 65, 'Working on DJGPP cross-compilation');
+ progressMeter('GGI', 90, 'New cross-platform software standard?');
+ progressMeter('GLX', 95, 'Working properly');
+ progressMeter('MGL', 80, 'No comments');
+ progressMeter('SDL', 90, 'New cross-platform software standard?');
+ progressMeter('Sun XIL', 50, 'Unknown status');
+ progressMeter('SVGAlib', 85, 'No comments');
+ progressMeter('WGL', 70, 'No comments');
+ progressMeter('X11', 95, 'Working properly');
+ progressKey();
+ tableFooter();
+ tableBoxFooter();
?>
|
+
+
diff --git a/search.php b/search.php
index f054fd4..172f018 100644
--- a/search.php
+++ b/search.php
@@ -1,35 +1,9 @@
-
+This page is still under construction. Please check back later.
+
-
-
-
- |
-
-
- This page is still under construction. Please check
- back later.
- |
-
-
-
- |
-
- |
-
-
diff --git a/sotc.php b/sotc.php
index 36b7ef6..6692309 100644
--- a/sotc.php
+++ b/sotc.php
@@ -1,80 +1,97 @@
-
-
-
-
- |
-
- The State of the Code address is a not-frequently-enough updated
- article written by Knghtbrd
- primarily for QuakeForge developers and other people who consider
- themselves to be knee deep in the code, whether they happen to be
- writing it or just testing it. What you won't find here is a lot of
- the fluff news that tells the casual onlooker that the project is
- actually doing stuff without really telling you what the state of
- things are.
+
+
+ The State of the Code address is a not-frequently-enough updated article
+written by Knghtbrd primarily for
+QuakeForge developers and other people who consider themselves to be knee-deep
+in the code, whether they happen to be writing it or just testing it. What
+you won't find here is a lot of the fluff news that tells the casual onlooker
+that the project is actually doing stuff without really telling you what the
+state of things are.
- No attempt will be made to soften technical issues so anyone can
- understand them. If you want to really know what's going on, you
- probably don't want details left out because they might not make a
- whole lot of sense to a non-coder. Feedback is always welcome. So
- are corrections if they're necessary - contrary to popular (with him)
- belief, Knghtbrd has in fact been known to be wrong sometimes. He
- isn't afraid to admit it either (most of the time..)
- No attempt will be made to soften technical issues so anyone can understand
+them. If you want to really know what's going on, you probably don't want
+details left out because they might not make a whole lot of sense to a
+non-coder. Feedback is always welcome. So are corrections if they're
+necessary - contrary to popular (with him) belief, Knghtbrd has in fact been
+known to be wrong sometimes. He isn't afraid to admit it either (most of the
+time..)
+
-
- | ';
- tableHeader(3, 'black');
- $index = 1; $filename = "sotc/sotc1.html";
- while(file_exists($filename)) {
- $fp = fopen($filename, "r");
- $str = fgets($fp, 4096);
- fclose($fp);
- $str = ereg_replace("","",$str);
- echo ' SotC #' . $index . ' - ' . $str;
- $index++;
- $filename = "sotc/sotc" . $index . ".html";
+ closedir ($dirHandle);
+ rsort ($sotcList);
+ include ('sotc/' . $year . '/' . $sotcList[0]);
}
- tableFooter();
- tableBoxFooter();
- ?>
-
- |
-
-
-
- |
-
- |
-
-
+ }
+
+ function sotcYears() {
+ $i = 0;
+
+ $dirHandle = opendir('sotc/');
+ if ($dirHandle) {
+ while ($year = readdir($dirHandle)) {
+ if (is_dir('sotc/' . $year) && $year != '.' && $year != '..' && $year != 'CVS') {
+ $years[$i++] = $year;
+ }
+ }
+ closedir ($dirHandle);
+ rsort ($years);
+ return $years;
+ }
+ }
+
+ function sotcListFiles( $year ) {
+ $i = 0;
+
+ $dirHandle = opendir('sotc/' . $year );
+ if ($dirHandle) {
+ while ($fileName = readdir($dirHandle)) {
+ if ($fileName != '.' && $fileName != '..' && $fileName != 'CVS') {
+ $sotcList[$i++] = $fileName;
+ }
+ }
+ closedir ($dirHandle);
+ rsort ($sotcList);
+ if (count($sotcList) > 0) {
+ tableBoxHeader('black', tableHeadColor);
+ tableTitle('SotC Archives for ' . $year, 3, tableHeadColor);
+ for ( $i = 0; $i < count($sotcList) ; $i++) {
+ $file = fopen('sotc/' . $year . '/' . $sotcList[$i], 'r');
+ $line = fgets($file, 4096);
+ fclose($file);
+ $line = ereg_replace('', '', $line));
+ echo ' |
| ' . $line . ' |
';
+ }
+ tableBoxFooter();
+ }
+ }
+ }
+
+ if (!$year) {
+ $year = date('Y', time());
+ }
+ $years = sotcYears();
+ for ( $i = 0; $i < count($years) ; $i++) {
+ echo $years[$i];
+ }
+
+ sotcShowLatest($year, 999);
+ echo '';
+ sotcListFiles($year);
+?>
+
+
diff --git a/speed_cheat.php b/speed_cheat.php
index 595aba3..98233d3 100644
--- a/speed_cheat.php
+++ b/speed_cheat.php
@@ -1,79 +1,52 @@
-
+
+
How does it work?
+ The "time cheat" relies on the client lying to the server
+ about how much time has passed since the last packet was sent. Knowing
+ this, detecting the time cheat is simple. For a period of say, 30 seconds,
+ the QuakeForge server adds up the times from all the movement packets
+ received from a specific client. If the client says that more then 30
+ seconds have passed in 30 seconds, a red flag is raised.
+
+
Are there any problems with this?
+ Sadly, the Windows QuakeWorld clients before 2.33 had a bug in keeping
+ track of time (This is not really a bug in QuakeWorld, but Windows 95 and
+ 98). The longer Windows is up, the faster time will seem to pass. While
+ there is not a noticeable speed boost from this until it has been up for
+ more then a day or so, it is detectable even after the system has been up
+ only a few hours.
+
+
This, along with other factors including lag and packet loss, can cause
+ the time reported by the client to be over the time the server expects.
+
+
Well, what can I do?
+ QuakeForge's cheat detection is adjustible within the server, so that
+ administrators can decide what settings work best. Here are descriptions
+ of some of the config variables ("cvars") that you can use to
+ configure time cheat detection on your server.
+
+
sv_timekick: This cvar controls the number of times a
+ player has to be caught "cheating" before they get kicked. sv_timekick
+ shows up in serverinfo if it is changed from the default. If
+ sv_timekick is less than 1, speed cheat detection is disabled. Default
+ is 3.
+
+
sv_timekick_fuzz: This cvar affects how strict the
+ protection is. The higher the number, the more "fuzz" gets applied,
+ and the less strict the detection code is. Raise this if your players
+ are being kicked for packet loss and lag. The values of this cvar are
+ in tenths of a percent. Default is 10, giving a fuzz factor of about
+ 1 percent.
+
+
sv_timekick_interval: This cvar controls how often, in
+ seconds, the time tally is counted. Lowering this value increases the
+ chance of false positives, but helps to minimize the amount of damage
+ a time-cheating player can cause. Default is 30 seconds.
+
+
-
-
-
-
-
- How does it work?
-
- The speed cheat works by the client lying to the server
- about how much time has passed since the last packet
- was sent. Therefore, the cheat detection is simple.
- For a period of say, 30 seconds, QuakeForge adds up the
- times from all the movement packets received from a
- specific client. If the client says that more then 30
- seconds have passed in 30 seconds, a red flag is raised.
- Are there any problems with this?
-
- Sadly, the Windows QuakeWorld clients before 2.33 had a
- bug in keeping track of time. The longer Windows is up,
- the faster time will seem to pass. While there is not a
- noticeable speed boost from this until it has been up
- for more then a day or so, it is detectable even after
- the system has been up only a few hours.
-
- This and several other factors, including lag and packet
- loss, can cause the time reported by the client to be
- over the time the server expects.
- Well, what can I do?
-
- QuakeForge's cheat detection is adjustible, so that
- server admins can decide what settings work best. Here
- are descriptions of some of the cvars that you can use
- to configure cheat detection on your server.
-
- sv_timekick: This cvar controls the number of
- times a player has to be caught "cheating" before they
- get kicked. sv_timekick shows up in serverinfo if it is
- changed from the default. If sv_timekick is less than 1,
- speed cheat detection is disabled. Default is 3.
-
- sv_timekick_fuzz: This cvar affects how strict
- the protection is. The higher the number, the more
- "fuzz" is applied, and the less strict the detection
- code is. Raise this if your players are being kicked for
- packet loss and lag. The values of this cvar are in
- tenths of a percent. Default is 10, giving a fuzz
- factor of about 1 percent.
-
- sv_timekick_interval: This cvar controls how
- often, in seconds, the time tally is counted. Lowering
- this value increases the chance of false positives, but
- helps to minimize the amount of damage a speed-cheating
- player can cause. Default is 30 seconds.
- |
-
-
-
- |
-
- |
-
-
diff --git a/template.php b/template.php
index c6fc06c..d8cb334 100644
--- a/template.php
+++ b/template.php
@@ -1,5 +1,5 @@