Shared via

Otaku Play Ground is a site for all ages dedicated to providing a enjoyable, friendly, fun, and relaxing place for you to play games, chat, make friends, post on our forums, and much much more. Thank you for stopping by and we hope you enjoy your time here.

We have a total of 8,328 games in our Arcade

Primal Defence
Qauterback KO
Quick Cards 3
Railroad BOOM!
Rainbow Spider
Rats & Spears
RhythmBlaster 2
Qwerty Hard
Puzz Pinball
ReBound 3 Headshot Machine Gun Semi-Auto
Quick Brick
Redneck Games – Dynamite Fisher
Renault Mr.X
Radial Snake
Quad Squad 4
RingsS
Blockpolis
Recoil
Castle Of Cards FullVersion
Red Plane 2
ReBound 3 Arcade Handgun
Purp
Neon 2.5
Reet Darts
Rebound

Yeti Sports 1 Blood
Kick Santa
Olympic Discus Throw
Yeti Long Shot
Irritating Game
Blast Billiards
Hamster Flight
Halloween Tiles
Blix
Power Driver
Manjongg Solitare
Jump2
Blocks
Patience Delux
Paperboy
Monkey Cliff Diving
Blocks_2
Square Bear Photo Hunt
Kenoka Slingo
Death Jr – C4 Hamster
Kakato Otoshi
QBeez
Flyplane
9 Ball Pool
Pool Jam – 5 Minute Game

I have been apart of this site from the start and realy like it for the games forum topics and army battle system to play

The following function parses the host

(xxxxxx.dot.com or xx.xx.xx.xx) from a URL.

<?php

function parseHost($address){

$address = str_replace('http://','', $address);

return array_shift(explode('/', $address));

}

$siteURL = 'http://somesite.com/somedirectory
/somesubdirectory/somepage.php';

echo 'The host of ' . $siteURL . ' is ' .
parseHost($siteURL) . '.';

?>

The promise for developers to be able to easily and quickly develop applications appears to have been forgotten. The time spent a ‘modder’ will spend developing an application has increased by quite a good bit.

The new application system has a good basis to it, but the amount of files, all in the name of organization, is ridiculous. A simple modification of the 2.3 and 2.1 days appears to be a much larger task. I’m all for organization and structure, but when coding becomes redundant, it’s a sign of a problem.

The installer system is a pretty nice one, and will hopefully fully work in the second beta. It will replace the need to install a third party installer, e.g. the great Universal Mod Installer by Michael. Ultimately, it will allow users who aren’t too savvy about application installation to install the mod writers’ applications. This could mean an increase in income, but also a greater community and amount of resources.

Hooks were something I was really looking forward to. After seeing the current hook system and access points, though, I find it useless. There are far too few access points. The point of the hooks system was to reduce file edits required to install applications, but the current access points only help out a few, but not too many. If IPS wants a truly powerful hooks system, then please, for the love of PHP, give us more access points.

Classes have changed… a lot. When I first started toying with IP.Board, in the 2.0.x days, the upgrade to 2.1 seemed to be a huge jump. The 2.3 to 3.0 jump is much larger. This is a jump the Evel Knievel would look at twice before making a decision. Upgrading a 2.3 component to a 3.0 application is no simple task because of this. The beta dev docs mention a regExp replace, but in most cases, you’re still going to be redoing a lot of your code. Classes, functions, and members have been changed, removed, or added to a new separate object.

Don’t get me wrong, I like the new set up of the classes, but why change null_function to nullFunction? It’s irritating.

Release date is important to a lot of us. Some people use IPS’s software to earn income. The extremely delayed release of a beta has aggravated a lot of people, and an even longer wait for a stable version looms over all of us like a thunderstorm that we’re not sure when it’s going to let loose torrential rain. I, along with a few others, held off with 2.3 components because a stable 3.0 release was on the horizon, but with the beta and other news, we’re back to writing for 2.3 or being extremely hesitant on upgrading our apps to 3.0.

Even though I’m extremely critical of the new software, I’m very hopeful because of it’s innovative set up and vast possibilities. This will truly revolutionize the forum system software as we all know it. When a final version of 3.0 is released, I hope that all of you will upgrade and push this revolution forward, and not linger in the past with what will be outdated, antique software.

There are two types of BBCodes, the ones I’ll call Simple Buttons, which uses only some content between the tags ( [TAG]{content}[/TAG] ), and others I’ll call Advanced Buttons, which uses an option and some content between the tags ( [TAG={option}]{content}[/TAG] ).
Let’s start with the first (and easier) ones.

Important notices
1 · The changes in the lang_files must be done in every folder you have (every language pack you have installed).
2 · The changes in the skin sections must be done in every skin set you have installed.

The Simple Buttons will act like the Bold, Italic and Underline buttons, oppening and closing the tag in Normal Mode or oppening a prompt for you to type the text to be formatted in Guided Mode.
Files to edit:
/jscripts/ipb_bbcode.js
/lang/*/lang_post.php
and some skin changes…

(* all the folders your have)

1 · /jscripts/ipb_bbcode.js

Open the ipb_bbcode.js file and find:

CODE
var HTML_open = 0;



Add below:


QUOTE
var TAG_open = 0;



Where TAG is the name of the tag you’re adding. If it is a “php” button and the tag format is [PHP]{content}[/PHP] you must add:


QUOTE
var PHP_open = 0;



You need to add that line for every Simple Button you want to add. After all done, save and upload the file back to your server.

2 · Skin Manager: “Post Screen -> postbox_buttons”

Find in this template bit:

CODE
<input type=”button” accesskey=”p” value=” CODE ” onclick=”simpletag(‘CODE’)” class=”codebuttons” name=”CODE” onmouseover=”hstat(‘code’)” />



Add below:


QUOTE
<input type=”button” accesskey=”t” value=” TAG ” onclick=”simpletag(‘TAG‘)” class=”codebuttons” name=”TAG” onmouseover=”hstat(‘tag‘)” />



Replacing all the red values with your custom ones, checking to see if there is no duplicated values in the accesskey part (you can’t use a “b” because it’s used in the Bold Tag ).
Again, if you’re adding a “php” button and the tag format is [PHP]{content}[/PHP] you must add:


QUOTE
<input type=”button” accesskey=”c” value=” PHP ” onclick=”simpletag(‘PHP‘)” class=”codebuttons” name=”PHP” onmouseover=”hstat(‘php‘)” />



I used a “c” for the accesskey because “p” is used in the Code Tag.
You need to add that input for every Simple Button you want to add. After all done, save and close the template bit.

3 · Skin Manager: “Post Screen -> pm_postbox_buttons”

Repeat all the steps listed in the item 2 above to add the button in the PM Post Screen. Although this is optional I think it’s a good idea to add all the buttons there too

4 · Skin Manager: “Post Screen -> get_javascript”

Find in this template bit:

CODE
var help_code           = “{ipb.lang['hb_code']}”;



Add below:


QUOTE
var help_tag = “{ipb.lang['hb_tag']}”;



Where the red values are your custom ones. If it is a “php” button and the tag format is [PHP]{content}[/PHP] you must add:


QUOTE
var help_php = “{ipb.lang['hb_php']}”;



Repeat this process for every Simple Button you want to add. After all done, save and close the template bit.

5 · /lang/*/lang_post.php

Open the lang_post.php file and find:

CODE
check_length        =>    ”Check Post Length”,



Add below:


QUOTE
‘hb_tag‘ => “Insert a tag (alt + t)”,



Where the red values are your custom ones. You may replace the green part with something that fits your needs. If it is a “php” button and the tag format is [PHP]{content}[/PHP] you must add:


QUOTE
‘hb_php‘ => “Insert a PHP code (alt + c)”,



The green code will appear in the “help line”, right below the buttons. Remember to use the same letter you added as an accesskey in the steps 2 and 3 in the “alt +” part
Notice that the first part of code in the lines above ( ‘hb_php‘ ) is the same one used in the step 4 ( {ipb.lang['hb_php']} ). It must be that way or you’ll have problems
Repeat this process for every Simple Button you want to add. After all done, save and upload the file back to your server.

And it’s done! Rebuild your skin set caches using the skin tools and have fun with your new buttons

I’ll add the instructions to Advanced Buttons later

PS: Shame we can only use ten quote tags per post.
I prefer them because I can use colors in the code but had to change some in this post otherwise it would not parse everything…

The Advanced Buttons will act like the http:// buttons, oppening a prompt for you to type the {option} and then the {content}, in both Normal and Guided Modes.

Files to edit:
/jscripts/ipb_bbcode.js
/lang/*/lang_post.php
and some skin changes…
(* all the folders your have)

1 · /jscripts/ipb_bbcode.js

Open the ipb_bbcode.js file and find:

CODE
//==========================================
// URL tag
//==========================================

function tag_url()
{
var FoundErrors = ”;
var enterURL   = prompt(text_enter_url, “http://”);
var enterTITLE = prompt(text_enter_url_name, “My Webpage”);

if (!enterURL) {
FoundErrors += ” ” + error_no_url;
}
if (!enterTITLE) {
FoundErrors += ” ” + error_no_title;
}

if (FoundErrors) {
alert(“Error!”+FoundErrors);
return;
}

doInsert(“[URL="+enterURL+"]“+enterTITLE+”[/URL]“, “”, false);
}



Add below:


CODE
//==========================================
// TAG tag
//==========================================

function tag_tag()
{
var FoundErrors = ”;
var enterOPTION   = prompt(text_enter_option, “Option text”);
var enterCONTENT  = prompt(text_enter_content, “Content text”);

if (!enterOPTION) {
FoundErrors += ” ” + error_no_option;
}
if (!enterCONTENT) {
FoundErrors += ” ” + error_no_content;
}

if (FoundErrors) {
alert(“Error!”+FoundErrors);
return;
}

doInsert(“[TAG="+enterOPTION+"]“+enterCONTENT+”[/TAG]“, “”, false);
}



Where “TAG” is the name of the tag you’re adding, and “OPTION” / “CONTENT” can be replaced with any text (just be carefull to not use duplicated values). If it is a “topic link” button ( added as a Custom BBCode by default ) and the tag format is [ TOPIC={option}]{content}[/ TOPIC] you must add:


CODE
//==========================================
// TOPIC LINK tag
//==========================================

function tag_topic()
{
var FoundErrors = ”;
var enterTID   = prompt(text_enter_tid, “Your topic id”);
var enterTEXT  = prompt(text_enter_text, “Your link text”);

if (!enterTID) {
FoundErrors += ” ” + error_no_tid;
}
if (!enterTEXT) {
FoundErrors += ” ” + error_no_text;
}

if (FoundErrors) {
alert(“Error!”+FoundErrors);
return;
}

doInsert(“[TOPIC="+enterTID+"]“+enterTEXT+”[/TOPIC]“, “”, false);
}



You need to add that function for every Advanced Button you want to add. After all done, save and upload the file back to your server.

2 · Skin Manager: “Post Screen -> postbox_buttons”

Find in this template bit:

CODE
<input type=”button” accesskey=”p” value=” CODE ” onclick=”simpletag(‘CODE’)” class=”codebuttons” name=”CODE” onmouseover=”hstat(‘code’)” />



Add below:


CODE
<input type=”button” accesskey=”c” value=” TAG ” onclick=”tag_tag()” class=”codebuttons” name=”TAG” onmouseover=”hstat(‘tag’)” />



Replacing the onclick value with the name of the function you added in the step one and checking to see if there is no duplicated values in the accesskey part (you can’t use a “b” because it’s used in the Bold Tag ).
If you’re adding a “topic link” button ( added as a Custom BBCode by default ) and the tag format is [ TOPIC={option}]{content}[/ TOPIC] you must add:


CODE
<input type=”button” accesskey=”c” value=” TOPIC ” onclick=”tag_topic()” class=”codebuttons” name=”TOPIC” onmouseover=”hstat(‘topic’)” />



Another small thing is that if you don’t have more accesskeys to use you can just remove that part of the input

3 · Skin Manager: “Post Screen -> pm_postbox_buttons”

Repeat all the steps listed in the item 2 above to add the button in the PM Post Screen. Although this is optional I think it’s a good idea to add all the buttons there too

4 · Skin Manager: “Post Screen -> get_javascript”

Find in this template bit:

CODE
// IBC Code stuff


Add below:


CODE
var help_tag           = “{ipb.lang['hb_tag']}”;
var text_enter_option      = “{ipb.lang['jscode_text_enter_option']}”;
var text_enter_content    = “{ipb.lang['jscode_text_enter_content']}”;
var error_no_option        = “{ipb.lang['jscode_error_no_option']}”;
var error_no_content        = “{ipb.lang['jscode_error_no_content']}”;


Note that the vars are the same ones used in the js function, in the first step.
If you’re adding a “topic link” button ( added as a Custom BBCode by default ) and the tag format is [ TOPIC={option}]{content}[/ TOPIC] you must add:


CODE
var help_topic           = “{ipb.lang['hb_topic']}”;
var text_enter_tid      = “{ipb.lang['jscode_text_enter_tid']}”;
var text_enter_text    = “{ipb.lang['jscode_text_enter_text']}”;
var error_no_tid        = “{ipb.lang['jscode_error_no_tid']}”;
var error_no_text        = “{ipb.lang['jscode_error_no_text']}”;


Again, note the same vars used in the js function
Repeat this process for every Simple Button you want to add. After all done, save and close the template bit.

5 · /lang/*/lang_post.php

Now we just need to add the lines you stated in the step 4 to the lang file.
Open the lang_post.php file and find:

CODE
‘hb_open_tags’ => “Open Tags”,



Add below:


CODE
hb_tag    => “Insert a tag (alt + c)”,
jscode_text_enter_option  =>    ”Enter the option part”,
jscode_text_enter_content  =>    ”Enter the content part”,
jscode_error_no_option  =>    ”You must enter the option part!”,
jscode_error_no_content  =>    ”You must enter the content part!”,



Replace the texts to fit your needs.
If you’re adding a “topic link” button ( added as a Custom BBCode by default ) and the tag format is [ TOPIC={option}]{content}[/ TOPIC] you must add:


CODE
hb_topic    => “Link to a topic (alt + c)”,
jscode_text_enter_tid  =>    ”Enter the topic id”,
jscode_text_enter_text  =>    ”Enter the link text”,
jscode_error_no_tid  =>    ”You must enter the topic id!”,
jscode_error_no_text  =>    ”You must enter the link text!”,



The text between the quotes will appear in the “help line”, right below the buttons and in the prompts. Remember to use the same letter you added as an accesskey in the steps 2 and 3 in the “alt +” part
Notice that the first part of codes in the lines above ( hb_topic, ‘jscode_text_enter_tid‘, etc. ) are the same ones used in the step 4 ( {ipb.lang['hb_topic']}, ipb.lang['jscode_text_enter_tid'], etc. ). It must be that way or you’ll have problems
Repeat this process for every Advanced Button you want to add. After all done, save and upload the file back to your server.

And it’s done! Rebuild your skin set caches using the skin tools and have fun with your new buttons

While Invision Power Board is a commercially sold product, there is a large modding community and many of these modifications are free. In addition, many groups offer the download or design of free and paid skins.

_________________________________________________

History

Invision Power Services (IPS) was created by Matt Mecham and Charles Warner in 2002, after they left Jarvis Entertainment Group (who produced Ikonboard). Their first product was IPB, another forum package, which quickly gathered a community of former Ikonboard users.

Although the software developers originally maintained that it would remain a free package, in 2004 IPB ended its free releases for non-commercial uses. A downloadable trial version of Invision Power Board 2.0.0 PF versions 1 and 2 were made available, but were discontinued on September 27, 2004. It was replaced with a free demo with restrictions of 5000 posts, 1000 threads, 200 members and other restrictions, thus ending its claims that IPB will be free forever.

Many users were upset with this, and some attacked Mecham, making allegations of copyright infringement. On July 1, 2005, IPS changed the demo time frame from 15 days to 5 days, and a few months later, it was again reduced to 24 hours, and now it has been reduced to 8 hours for private use.

IPB 2.1 was released on September 13, 2005. The administrator’s control panel was completely redesigned, and the posting options were renovated to feature viewable text properties (Rich Text Editor), such as bold, italics, underline, etc. The viewing styles were also redone, and a number of various other changes were made including the use of Ajax in many new features.

Version 1.3

The last free full version is Invision Power Board 1.3.1, which is not as widespread as 1.3 because of the short available time before 2.0 replaced it. Since then many known exploits have been found. Patches have been produced by the community.

Version 2.0 and 2.1

When version 2.0 went final, Invision Power Board became a paid product a week later. Just as with IPB 1.3, some users still using the unrestricted trial versions of the 2.0 PF versions but again, contain a lot of security holes and are no longer supported. However, no modifications exist which make IPB 2.0 secure. It was also renamed to IP.Board.

Version 2.2

Invision Power Board 2.2 included many improvements, new features, and security fixes. It was the first version to undergo a security audit by a company named Gulftech to find any security holes missed by the IPS development team as part of their ongoing effort to keep IPB as secure as possible. The new version also includes minor changes to the Administration Panel, and also an entirely redesigned profile system. The Invision’s team also continues to employ AJAX in its software. All versions of IPB from 2.0 and on are commercial software, with no downloadable demo version available. Potential users may request a twelve hour online trial, hosted by IPS.

Version 2.3

Version 2.3 has recently been released and is the latest version of IP.Board. . Starting from this version, the product will ship with 2 skins, the old default light blue skin and a new default darker skin. The release is mainly to assist in forums that have larger traffic and include advanced integration with other IPS product lines. IPS also implemented a new ACP Help System which made it easier to navigate around the Administrator’s Control Panel, along with an ACP “Dashboard” page, showing an overview of the system. This page replaced the “Admin” tab as the default page in the Admin Panel.

Version 3.0

Invision Power Board is the next major release milestone of the Forum Software. It will include many promised features such as a new overall design of the software, a reputation type feature where users can rate individual posts, the PM (Personal Message) system becoming a conversation styled feature (as Google has done with GMail) and many more enhancements. IPS has made an alpha available to the public, and on December 22, they released the first encoded beta to all current IPS customers.

Fringe: Ability

Fringe: The Transformation

Fringe: The No Brainer

Fringe: In Which We Meet Mr. Jones

Fringe: Bound

Fringe: The Dreamscape

Fringe: The Arrival