Yeah, I still do. I have some plugins that need to run with more then just me AI on a server.
It's the only thing I could think of that would coordinate between everyone's timezones.I don't know man. I claim shenanigans, because I have those files as well, it was a part of the Open Beta. That and you need the web interface, that's closed, for any of it to work.
registerPacket callbacks, and registerSayCommands callbacks.
registerPacket callbacks, and registerSayCommands callbacks.
Due to adding support for the OutGuage packet, I'm taking a second pass on how these callbacks are both initiated, and sent to the callback.
$this->registerPacket(callback $callback, packetEnum $Packet, ...);
$this->registerSayCommand(callback $callback, String 'Command', String 'Description');
Where registerPacket would hand back the packet right away, and the hostID it came from looking like this:
And the registerSayCommand would hand back in the same way.
Or do you think that the Say command should have a level of abstraction attached to it?
Oh while I am at it.
Or should I just leave it alone?
Due to adding support for the OutGuage packet, I'm taking a second pass on how these callbacks are both initiated, and sent to the callback.
$this->registerPacket(callback $callback, packetEnum $Packet, ...);
$this->registerSayCommand(callback $callback, String 'Command', String 'Description');
Where registerPacket would hand back the packet right away, and the hostID it came from looking like this:
<?php
function callback(ISP_ISI $ISI, String $HostID)
?>
<?php
function callback(ISP_MSO $MSO, String $HostID)
?>
Oh while I am at it.
<?php
$this->registerPacket('OutGuage', Out::Guage);
public function OutGuage(OutGuage $OG, $HostID)
{
print_r($OG);
}
?>
Your not. I've not made that function yet.
This is for everyone. If you have requests, please make them in PRISM's GitHub Issue Tracker and tag them under Request.
Release what you have. And then work on version 2.0. It's how the world works 
, just look at PRISM's core.
, just look at PRISM's core.So a bad install of PHP was causing the error?
As far as UName, yes I can do that, it's a simple one line thing.
As far as UName, yes I can do that, it's a simple one line thing.
Apt-get style plugin installs.
Just an idea, might be useful when we get some popular plugin devs.
Installing a plugin would be as simple as:
PRISM should even be able to include and init the plugin during runtime.
Adding popular plugin devs would be as simple as:
This would work off of the HTTP interface, so things like HTTP status codes would be used, and the transport medium for basic information on the plugins available would JSON.
Hip Tip to filur. Who by the way has done something like this for lurLFSd, many years ago. So the idea is not new, obviously, and it's also not new to LFS.
Installing a plugin would be as simple as:
prism plugins install pluginNamePRISM should even be able to include and init the plugin during runtime.
Adding popular plugin devs would be as simple as:
prism plugins repos add http://repo.domain.tld/DygearThis would work off of the HTTP interface, so things like HTTP status codes would be used, and the transport medium for basic information on the plugins available would JSON.
Hip Tip to filur. Who by the way has done something like this for lurLFSd, many years ago. So the idea is not new, obviously, and it's also not new to LFS.
Last edited by Dygear, .
How are you still a demo racer? Someone needs to get this man an S2 license.
Can you compress it to an MP3?
In that case, use this debug.bat script, and post the whole deb.log here. Also, if it closes right after, how do you know where the error is coming from?
debug.bat
debug.bat
@echo off
php -e PHPInSimMod.php %1 %2 > deb.log
pauseOk. I'll keep an eye out for it. But please, once it happens again, post the call stack as reported by PRISM's error handler.
Oh, McLaren could give a **** how Hamilton lives his life. As long as he shows up and does his job that's what matters to them.
I need some testers.
I need some people that are willing to test some of the plugins that come with the next update of PRISM. They are already on the github account, but before I release them in the wild, I would like for 3 or 4 people along with me to get on a server and make sure everything works when running from a client, and running from a dedicated server. If anyone wishes to sign up for this, please just reply below, along with the times you are available (Please include the timezone in your post so I can coordinate times with everyone.)
I've forwarded your request to Victor who is responsible for the packet handling modules with PRISM. If he want's to do it he will, if not, I'll get around to it at some point. But I would not expect it any time soon if I have to do it.
On the subject of installers, I was thinking about this and how some installers cause some Anti-Virus programs to cause a false positive. This would be the case with NSIS when using the Built-in NSISdl plugin that I intend on using. The NSIS Wiki has a warning about this plugin giving a false positive. This is a problem as I've built up a reputation of providing safe applications used by many websites, on many servers, and now many clients. I feel that even the look of impropriety could tarnish that image.
The problem boils down to this. I want to make a installer / updater that uses PRISM's github as a means of keeping everyone up to date. But in order to do that, I would have to use the Built-in NSISdl plugin and that would cause some Anti-Virus plugins to say that my installer / updater in virus. Even tho this is a false positive, I don't like the idea of that at all.
Thoughts?
The problem boils down to this. I want to make a installer / updater that uses PRISM's github as a means of keeping everyone up to date. But in order to do that, I would have to use the Built-in NSISdl plugin and that would cause some Anti-Virus plugins to say that my installer / updater in virus. Even tho this is a false positive, I don't like the idea of that at all.
Thoughts?
I have it and it's merged. I'll work on a release before I leave for you. (In about an hour.)
Yeah, there is no way that I can release this in it's current shape.
Last edited by Dygear, .
I'll have a look at it later, I'm going to sleep now. Just a note, I've never had that problem, so I don't really know what could be causing it. So if you can give me more information about the state of PRISM, and plugins running, the call stack trace that PRISM gives, that would be helpful.
FGED GREDG RDFGDR GSFDG