Here's the idea I have in mind, and have had in mind for a while: Cy-X.net becomes a filesystem-first *NETWORK* site with a small PHP shell for PHP files. The existing forum and webchat will remain the same, but just moved behind smaller interfaces.
Connect page is split into games/ and comms/, and turned into self-serve instead of auto on-demand.
A self-serve Connect page over automatic demand detection system is a better approach because the auto-demand system only turned it on if connections were attempted up to 4 times using the protocol, but doing this is very unreliable; players often get kicked out by failed to connect messages and give up before the server turns on.
Turning down the connection count requirement makes it easy for pingers to turn on servers at random which was the entire point of having a connection count requirement in the first place. So that wasn't a good endeavor.
Perhaps a demand requirement will be forced. X number of IPs needed for server to turn on.
This also makes Gamekeeper work better as a playercount tracker overall than a shitty resource management tool.
The end goal is to reduce maintenance to a minimum, make site management and upkeep incredibly easy, and make the public site should feel like a personal website/network rather than a web application. It also will enforce minimal dependence on SQL, so it should be able to continue working in extremely constrained or degraded/damaged conditions. It also allows me to give people the ability to maintain their own personal "sub-sites" or directories within Cyberix.
More details soon, checkpic rel
Connect page is split into games/ and comms/, and turned into self-serve instead of auto on-demand.
A self-serve Connect page over automatic demand detection system is a better approach because the auto-demand system only turned it on if connections were attempted up to 4 times using the protocol, but doing this is very unreliable; players often get kicked out by failed to connect messages and give up before the server turns on.
Turning down the connection count requirement makes it easy for pingers to turn on servers at random which was the entire point of having a connection count requirement in the first place. So that wasn't a good endeavor.
Perhaps a demand requirement will be forced. X number of IPs needed for server to turn on.
This also makes Gamekeeper work better as a playercount tracker overall than a shitty resource management tool.
The end goal is to reduce maintenance to a minimum, make site management and upkeep incredibly easy, and make the public site should feel like a personal website/network rather than a web application. It also will enforce minimal dependence on SQL, so it should be able to continue working in extremely constrained or degraded/damaged conditions. It also allows me to give people the ability to maintain their own personal "sub-sites" or directories within Cyberix.
More details soon, checkpic rel