Well Mark, is that an open invitation.. your ports are.. open?

:hide:

(I must get around to stop chasing tail, or gaming, and actually try to do something with PRISM.)

And I fixed the button error not showing up on other peoples screen.

What was wrong with the buttons?

I had a strange problem, then solved it, so Dygear suggested I should post here

Anyone using Windows 7 may experience this problem. Basically I created my "hosts.ini" config file, started "PRISM.bat" and the window just said "Press any key to continue...". So I tried running the "PRISM.bat" in "Run as Administrator" mode, and that just outputed "Couldn't load : PhpInSimMod.php".

My solution was to run PRISM in XP SP3 compatibility mode. (Right click on the file, click "Properties", go into Compatibility mode, select XP SP3)

Note: Don't use this solution with "Run as Administrator" mode, it won't fix the problem.

To Dygear: Can't wait until the release with timers!

Quote from misiek08 :

What was wrong with the buttons?

ISF_LOCAL was hard coded into the IS_ISI packet, making the button packets redirect to my screen always.

A funny bit of back story for you all, Victor stated that he would use stream_select back in 2007 for InSim connections.

Things to fix:
1. The are some undefined function like userGet.....
2. You have 2 classes for handle state. In prism_state.php in prism_statehandler.php (both are required?)
3. In subforum is topic Is_reo you have a discussion about IS_REO packet and I gave there a link for old post where GeForz made patch for IS_REO which is working.
4. Debug cvar is not considerated in the code. For example file: PHPInSimMod.php lines: 172-181

I'll post below new things if I'll found them.

1. It is near getUserNameByPLID and others like this.

Quote from misiek08 :

1. It is near getUserNameByPLID and others like this.

I deprecated that function you should now use getClientByPLID($PLID)->UName, as that works with all data in the PRISM state handler.

whats the status of this? its been over a week

Quote from Dygear :

Just to follow up, there is no really clean way to do this, so I guess I'll push the 0.3.1 update tomorrow with a bunch of fixes to make this possible and clean.

(That's right kids, you heard it here first, 0.3.1 is coming out tomorrow.)

Quote from Fire_optikz001 :

whats the status of this? its been over a week

If you don't like waiting, your more then welcome to download the latest current from github. But it will not be officially supported, only master releases are supported.

unofficial

Timers are the last on the list of things that needed to be fixed before 0.3.1. It should be noted that from 0.3.0 to 0.3.1 there have been around 6,000 lines of code added or changed, so please take your time with this upgrade.

It should also be noted that I've changed alot of my internal functions to reflect AMX Mod X's & SourceMod's syntax of the commands that should make the plugins portable across these platforms. (Or atleast allow for a much easier time converting a AMXX or SM plugin into a PRISM plugin and visa versa.

Lastly, the 0.3.x branch is going to take a VERY long time, as I'm getting much of the underpinnings of the engine locked down and a lot of the core plugin naming conversion for functions, syntax and order of parameters tweaked and locked down. So, after the 0.3.x branch is done all of the core Plugin functions will be complete and won't be changed at all. It should also be noted that the standard callbacks will also be changed in a way to make it easier and more portable acorss all of the interface systems PRISM offers. And the quickest way to do that is to change from a UCID / PLID based system into a UName based system. This way handling of admin functions remains constant no matter where the command is coming from.

So, this is a bad time to start programming for PRISM as a lot of things are going to change.

Quote from Dygear :

So, this is a bad time to start programming for PRISM as a lot of things are going to change.

Exactly why i haven't started on the cruise plugin :angel: i already have the stuff i need to make ... but it will be better to wait

Quote from Fire_optikz001 :

Exactly why i haven't started on the cruise plugin :angel: i already have the stuff i need to make ... but it will be better to wait

Yeah, I would recomend waiting for version 0.4.0 before you start. Everything should be pretty solid API wise at that point at the most bare bone level, and you can make use of the new API functions as they come up. (Like the button interface.)

0.3.1 was just uploaded to github, under my current branch. I'm going to do a diff later on today and produce a change log for you, but first I'm going to sleep because I have work pretty soon. It should be noted that lots of the releases in this branch are going to be like this (slow to be released) while I clean up the API to make it directly compatable with Source Mod's and AMX Mod Xes API, albeit with some PHP flair.

Quote from Dygear :

0.3.1 was just uploaded to github, under my current branch. I'm going to do a diff later on today and produce a change log for you, but first I'm going to sleep because I have work pretty soon. It should be noted that lots of the releases in this branch are going to be like this (slow to be released) while I clean up the API to make it directly compatable with Source Mod's and AMX Mod Xes API, albeit with some PHP flair.

Broken Update, Using to Backtrack Errors. Don't upgrade to this version.o.o was this ment for 0.3.1?

It's working good for me.

Nah it is not...

http://www.cargame.nl/forum/ge ... lid-dimensions-t1812.html

Quote from Fire_optikz001 :

Broken Update, Using to Backtrack Errors. Don't upgrade to this version.o.o was this ment for 0.3.1?

0.3.1 was the update on top of that build. Not all files where updated in that version, so some of the files still have that comment.

Quote from cargame.nl :

Nah it is not...

http://www.cargame.nl/forum/ge ... lid-dimensions-t1812.html

Thanks for the report, I know how it happens, I'm not sure right now WHY it's happening tho.