[Jasonbourne]

Originally Posted by 8088 Ereg is deprecated and will throw a notice warning if you enable error, warning and notice reporting. Use preg_match for regular expressions.

Originally Posted by Jasonbourne Thanks ill.fix that up

Originally Posted by Zephyrus why would you use ereg, its deprecated

i dont -> i changed it

[Zephyrus]

Originally Posted by Jasonbourne i dont -> i changed it

sorry i didnt read previous comments, i just saw this:

"should be ereg instead of preg_match"

[Jasonbourne]

Im still learning (arnt we all ?) and the community reviewing and scrutinizing my code is the way i learn best

[Horsedick]

I'm really curious as to what advantages this is for use on sourcebans as it is now? What if any changes to the current build of sourcebans will this improve?

[Jasonbourne]

Originally Posted by Horsedick I'm really curious as to what advantages this is for use on sourcebans as it is now?

Its mainly so that people can build web apps that hook into the sb database.

1. Build your own UI for SB with all the program logic and db work taken care off
2. Automate systems such as payment with paypal ( im adding in an ipn)
3. link hlstatsx and sb for various functionality

things along those lines

[Horsedick]

Originally Posted by Jasonbourne Its mainly so that people can build web apps that hook into the sb database. Build your own UI for SB with all the program logic and db work taken care off Automate systems such as payment with paypal ( im adding in an ipn) link hlstatsx and sb for various functionality things along those lines

hmm, yeah sounds good...although I do hope someone builds upon what you've done so it doesn't go to waste.

[Zephyrus]

tbh i think sb is a piece of ... and that it should be completely rewritten instead of writing an API for it. It's ridiculous that you have to add the sb include to all your plugins to make it compatible while theres an OnBan forward in sm...

[Jasonbourne]

Originally Posted by Zephyrus tbh i think sb is a piece of ... and that it should be completely rewritten instead of writing an API for it. It's ridiculous that you have to add the sb include to all your plugins to make it compatible while theres an OnBan forward in sm...

If we were to code a sourcebans replacement

what features are we looking at from scratch ?

[Laplace]

hmm .. sourcebans is not as bad as stated by Zephyrus. I use it for years now and it does its job so far - the API will be helpfull to integrate other pages (specially user- and ban management) like spraytracker, donate interface, reserved slot interface and so on.

BR Laplace

[Zephyrus]

Originally Posted by Laplace hmm .. sourcebans is not as bad as stated by Zephyrus. I use it for years now and it does its job so far - the API will be helpfull to integrate other pages (specially user- and ban management) like spraytracker, donate interface, reserved slot interface and so on. BR Laplace

Because you are not a developer. Developers have to spend time just to add sourcebans compatibility to plugins because they were unable to use the OnBan forward, the sb page is really hard to modify because its all hardcoded + imho the file structure is a mess as well

+ sb is one of the main reasons why the sql lag happens on a lot of servers, it does so many sql queries that it blocks other plugins