OniGalore - User contributions [en]

AE talk:OTA

2008-05-31T05:57:47Z

Your Mom: /* Chars */

This area is for reporting or documenting crashes or other bugs for [[AE:OTA|Oni Team Arena]].

==Crash reports==
==Chars==
:I crashed on compound even with the Daodan dll in. I was using the plugin version of the EXE if it matters
::[[User:Gumby|Gumby]] 00:00, 27 May 2008 (CEST)
:Did you use the cache fix? I don't know if it was fixed in Daodan dll. I know for sure it's fine with the cache fix EXE. It'd be troublesome if the plugin EXE didn't have the cache fix...
::[[User:Your_Mom|Your_Mom]] 10:47, 27 May 2008 (PST)
:Indeed, not many people are aware of the issue with the pathfinding grid cache, and I'm not sure who released the plugin-ready EXE. Could you guys link to it?
:The latest version of the [[Daodan DLL]] takes care of the pathfinding grid cache (and enables plugins, too), so you can use it with the original "Engrish" EXE.
::[[User:Geyser|geyser]] 16:25, 28 May 2008 (CEST)
:Another issue that systematically causes crashes is Loser's latest contribution to the Edition (TRAM hacks). Roll back to the New Year's release and report.
:I feel really sorry for not tracking down those of the upgrades that cause memory corruption, but Loser's TRAM are a lot of stuff to go through. Patience...
::[[User:Geyser|geyser]] 16:25, 28 May 2008 (CEST)
:The plugin EXE was posted by EdT [[http://oni.bungie.org/community/forum/viewtopic.php?id=508 here]]. The plugin EXE is hosted on Paradox's oni2.net site.
::[[User:Your_Mom|Your_Mom]] 22:55, 30 May 2008 (PST)

----

==Bug reports==
===Players that just stand and stare===
:This apparently has to do with the number of "duels" that Oni can handle simultaneously. 2x7 players usually work out fine, but for more players it can happen that some characters are singled out and can't start a fight with anyone, because the rest of the players already form a network that has the maximum number of "duels". This could be fixed by making some players forget their opponents, allowing for new awareness/duel links to be created.
::[[User:Geyser|geyser]] 16:25, 28 May 2008 (CEST)

==Resolved issues==
===Insufficient pathfinding grid cache===
:This used to cause crashes for battles spanning a few [[AKVA|BNV]]s cumulating too many pathfinding grid squares. Typically, this happens in the TCTF parking lot, in some areas of the Airport, and in some multi-storey areas of the Bio-Research Lab. The fix is either to lock out a few areas (e.g. lock the doors between the TCTF parking lot and the main building) or, ultimately, to increase the size of the pathfinding grid cache. This has been available as an in-place patch for the EXE, and is now handled by the Daodan DLL.
::[[User:Geyser|geyser]] 16:25, 28 May 2008 (CEST)

===Inconsistent pathfinding data===
:The only example of that so far is the main gate of the Bio-Research Lab. Even though it's closed, the pathfinding graph is the same as if it was wide open. Therefore, the AI may attempt to pathfind through it, and Oni may crash when they are blocked by the gate. This used to occur in the acid room: enemies falling to the "garage" side would start running out the garage and around the block and through the main gate and up the aisle and into the lobby and up the stairs and into the acid room again. The obvious fix to this was to lock a few doors.
::[[User:Geyser|geyser]] 16:25, 28 May 2008 (CEST)

AE talk:OTA

2008-05-31T05:56:23Z

Your Mom: /* Chars */

This area is for reporting or documenting crashes or other bugs for [[AE:OTA|Oni Team Arena]].

==Crash reports==
==Chars==
:I crashed on compound even with the Daodan dll in. I was using the plugin version of the EXE if it matters
::[[User:Gumby|Gumby]] 00:00, 27 May 2008 (CEST)
:Did you use the cache fix? I don't know if it was fixed in Daodan dll. I know for sure it's fine with the cache fix EXE. It'd be troublesome if the plugin EXE didn't have the cache fix...
::[[User:Your_Mom|Your_Mom]] 10:47, 27 May 2008 (PST)
:Indeed, not many people are aware of the issue with the pathfinding grid cache, and I'm not sure who released the plugin-ready EXE. Could you guys link to it?
:The latest version of the [[Daodan DLL]] takes care of the pathfinding grid cache (and enables plugins, too), so you can use it with the original "Engrish" EXE.
::[[User:Geyser|geyser]] 16:25, 28 May 2008 (CEST)
:Another issue that systematically causes crashes is Loser's latest contribution to the Edition (TRAM hacks). Roll back to the New Year's release and report.
:I feel really sorry for not tracking down those of the upgrades that cause memory corruption, but Loser's TRAM are a lot of stuff to go through. Patience...
::[[User:Geyser|geyser]] 16:25, 28 May 2008 (CEST)
:The plugin EXE was posted by EdT [[http://oni.bungie.org/community/forum/viewtopic.php?id=508 here]]. The plugin EXE is hosted on Paradox's oni2.net site.
::[[User:Your_Mom|Your_Mom]]

----

==Bug reports==
===Players that just stand and stare===
:This apparently has to do with the number of "duels" that Oni can handle simultaneously. 2x7 players usually work out fine, but for more players it can happen that some characters are singled out and can't start a fight with anyone, because the rest of the players already form a network that has the maximum number of "duels". This could be fixed by making some players forget their opponents, allowing for new awareness/duel links to be created.
::[[User:Geyser|geyser]] 16:25, 28 May 2008 (CEST)

==Resolved issues==
===Insufficient pathfinding grid cache===
:This used to cause crashes for battles spanning a few [[AKVA|BNV]]s cumulating too many pathfinding grid squares. Typically, this happens in the TCTF parking lot, in some areas of the Airport, and in some multi-storey areas of the Bio-Research Lab. The fix is either to lock out a few areas (e.g. lock the doors between the TCTF parking lot and the main building) or, ultimately, to increase the size of the pathfinding grid cache. This has been available as an in-place patch for the EXE, and is now handled by the Daodan DLL.
::[[User:Geyser|geyser]] 16:25, 28 May 2008 (CEST)

===Inconsistent pathfinding data===
:The only example of that so far is the main gate of the Bio-Research Lab. Even though it's closed, the pathfinding graph is the same as if it was wide open. Therefore, the AI may attempt to pathfind through it, and Oni may crash when they are blocked by the gate. This used to occur in the acid room: enemies falling to the "garage" side would start running out the garage and around the block and through the main gate and up the aisle and into the lobby and up the stairs and into the acid room again. The obvious fix to this was to lock a few doors.
::[[User:Geyser|geyser]] 16:25, 28 May 2008 (CEST)

User:Your Mom

2008-05-28T05:52:32Z

Your Mom: /* Website */

*Real Name: <Unknown>
*Birthday: February
*Job: <Unknown>
*Email: rcmpyourmom@hotmail.com

== Website ==
[http://your-mom.oni2.net/ Link]
After a year and three months, I have resumed work on the website. Hopefully, I can remeber enough finish the Analysis and Secrets, though those should really be, and are, here. If I can find my old TXT files, I'll upload em all...

And...I seem to not have gotten much of it done... *sigh*

== I'M NOT DEAD! ==

I haven't played Oni in a while, I forgot what scripts and HEX-edited things I had and ended up giving up trying to restore it (all me levels came out blank). I've forgotten most of the stuff, thank goodness for programming at school keeping me in tough with my FUNCs and VARs. Else i'd be totally lost into HTML and XML /CSS that I'd have no room left in my brain for um...actual coding? Scripting? whatever.

If you people ever check this, its not that I don't want to register on the new forums, I've tried several times, it just keeps giving me an error, something about timing out. Anyhow, don't expect anything from me anytime soon, but I'm feeling all nostalgic. I feel like opening up those *.BSL files and writing a new story script. I feel like running Un-Packer and making my own weapons. I can't do that anymore though. I have my obligations and deadlines to hold up both in life and the modding world (mod teams), as well as a community to please over at Star Wars Empire at War. I've never forgotten this game, Oni, and its lure - it dragged me into modding and into intrest in coding and programming. In a sense, this started my current career path. Ify ou ever manage to get those models exported, or if someone with 3D-Studio max would liek to model for me, I'd make a mod for that game, though its not the best engine, I'm wasting the space engine and the galactic map, but hey, I'd like to see the troops and heroes again. Maybe I can spark interst and make a squad-based FPS. Anyhow, good on this community for trying without mod tools. Makes it so only the most elite can produce high-quality mods. I haven't seen a n00b here yet ;)

Well, there's much I want to write, but hey, why right it if noone's going to read it? this is probably going to be buried under centuries of dust with noone to take a look at it.

I'll check back in a week or so, and that may be the last time. Not sure. Depending on what I feedback I get here.

Bye for now,

Your_Mom (What a fool I was choosing this name, I would much rather sign "D803" or "Droid #803" or even Unit-803 (Star wars thing)). Well, it goes to show how one changes.
----
:Hm, what kind of feedback are you expecting?
:I remember you, if that's what you're asking.
:3D stuff ''might'' be exportable... Soon(TM).
:But I tend to promise less rather than more.
:Good to know you're not dead, anyway.
:Weird how you can't register on the new {{OCF}}
::(looks like job for the Troubleshooter in Chief)
:Cheerios
::[[User:Geyser|geyser]] 19:13, 12 February 2007 (CET)

----
That (^) would have done.
Not gone and forgotten, might pick up modding this again. A great game, I want to go beat up some strikers again...
Well, anyhow, I need a refresher as to what's new in the way of the BIP, or if it died or something. Same with OTA.
I'll try registering again to see if it makes a difference...

Specifically, this is what it says:

An error was encountered
Error: Could not connect to smtp host "bungie.org" (60) (Operation timed out).

Thats two account names and two emails tried...no cigar. Apparently it creates the account, but it doesn't send me my confirmation email, therefore I can't login since I don't know my password... :(

-Y_M
----
:Harry says you should try and register again.
::[[User:Geyser|geyser]] 01:43, 15 February 2007 (CET)
:No can do for a thorough update on the projects...
:Too busy working on them ^^ Public overviews are the way.
:Basically, BIP and OTA are all part of [[ONK:ONK|ONK]] now.
:They're not dead by any means. There's a lot of hot new OBD stuff.
:However, there's no proper release apart from Loser's [[ONK:Warehouse|Warehouse Minus]] (beefed-up level0_Final)
:OUP still can't patch DAT stuff in a user-friendly (cross-version-compatible) way.
:But RAW stuff (BINA, TRAM tracks can very well be released as neat bundles).
:Loser has released a few such things, but nothing close to a "release" ^^
:(putting those together is probably more annoying than "experimenting")
:Loser has done a lot of things apart from that: moveable furniture, ''much'' smarter AI...
::but none of that has been relelased yet. Loser tries to cram it all into Warehouse Too
:::(unfortunately not in a modular and globally useful way, I'm afraid; we should talk)
:As for OTA, I hate to say that I didn't release anything since the Dev Mode came out.
::nothing but the pre-alpha of OTA2 that you had already seen.
:::I'm working on a completely new core, though. OTA3 or something.
::Looks really cool, but unfortunately it's mostly in my head, so you can't really enjoy it ^^
:::I'm distilling primary features (interface) one by one, and actual gameplay is secondary ATM.
::But it will be there. Will have to. I want OTA to totally rock by the end of the year.
:(it's already praised as the best Oni script mod "evah" by independent critics... congrats ^^ )
:EdT and you have really done a great job on that one... Thanks again, and welcome back...
::[[User:Geyser|geyser]] 01:43, 15 February 2007 (CET)

----
Affirmative, I'll try registering again...or...just sending that email to me :) EDIT: Worked :D

I'll just opt for a clean re-install of the game and hope it works again...
Modding in the other community has died down for now, its hit a dead phase. So, mght as well [ick up work again here, unless I forget about it again (I'm absent-minded of thing's I'm not immediately aware of need of doing). If you're still in need of a porter, there might be something I can do, giving its not too complex...I hope I remeber which values to change... So a combined thing, nice. OTA was fun with BIP-improved levels...in fact, I found it the easy way of testing the changes, rather than just play through the level...

Good to be back,
-Y_M

AE talk:OTA

2008-05-28T05:51:50Z

Your Mom:

==CRASH REPORTS==

This area is for reporting or documenting crashes on OniTeamArena (OTA)
Please report ANY CRASHES to this area.

Thank You

CRASH REPORTS :
----
The following crash report is for BRL arena 1.0 (Bio Research Lab)

Crash Occurs : During Game-play, time varying

Crash Origin : (Quote geyser): 'At the moment I "positively assume" or "definitely guess" or (whatever it's called) that the problem is with pathfinding on overlapping quads where AI can be simultaneously. Like being on the stairs, then falling and instantaneously being on the quad that goes under the stairs. It all apparently depends a lot on how it's done in a particular level. Big spaces covered with overlapping quads, ramps that emerge in the middle of a quad, stairs without railings... those are my "usual suspects" of the moment.'

Crash History : Similar crash experienced in <Airport Arena> all 1.X verions

Debugging Status : Completed Contact [[User:geyser|geyser]].

----

I crashed on compound even with the Daodan dll in. I was using the plugin version of the EXE if it matters [[User:Gumby|Gumby]] 00:00, 27 May 2008 (CEST)

Did you use the cache fix? I don't know if it was fixed in Daodan dll. I know for sure it's fine with the cache fix EXE. It'd be troublesome if the plugin EXE didn't have the cache fix... [[User:Your_Mom|Your_Mom]] 10:47, 27 May 2008 (PST)

AE:OTA

2008-05-28T05:46:40Z

Your Mom: /* Where do I get it? - fixed a broken link */

{|align=right
|[[Image:ONK.png]]
|}
{|align=right border=1 cellspacing=0
|
{|cellspacing=0
!OTA TALK ON [http://oni.bungie.org/forums/ OCF]
|-
|*[http://oni.bungie.org/forums/index.php?threadid=142 Major releases]
|-
|*[http://oni.bungie.org/forums/index.php?threadid=121 Dev talk]
|}
|-
|
{|cellspacing=0
!CONTACT US
|-
|*[[User:Geyser|geyser]]
|-
|*[[User:Your_Mom|Your_Mom]]
|-
|*[http://edt.oni2.net EdT]
|}
|}

==Oni Team Arena (or OTA)==
Oni Team Arena is a series of scripts oriented on multiplayer gameplay. You don't get to fight human opponents, but Oni's AI are treated as respawning bots.

The interface is much inspired by that of existing FPS-shooters and other games supporting multiplayer.

Smart bot behaviour, challenge and entertainment are the main objectives. OTA is also a playground allowing us to test complex combat situations before they get implemented in projects like Oni 2.

We try to implement as many popular multiplayer features as possible: random spawn positions, random weapons and powerups, frag-related messages, sounds and visuals, bot model selection etc. In the case of advanced features like teleporters and jump platforms, we're limited by the original AI. Otherwise, anything goes.
--------
"We" is [[User:geyser|geyser]] for the core scripting, [[User:Your_Mom|Your_Mom]] for cross-level porting on PC, and (since recently) [http://edt.oni2.net EdT] for porting 1.1 onto Mac OS9. [http://script10000.oni2.net/ Script 10000] provided the initial idea.
-----------

==What exactly is Oni Team Arena?==
What we do is a large number of comparatively small arena-like setups in appropriate spots throughout Oni. There are two teams of bots, you get to lead one, and a boss character gets to lead the other.

The number of players can vary, but we try to make it large, starting at 16 (which is the number of network/online players supported by Serious Engine 2).

Teams don't just fight with each other, they score points and the first team to reach a set amount of points wins. There can be neutral characters who attack either team or just annoy everybody.

===Game modes===
*Team Deathmatch : teams score a frag every time a player of the opposite team dies. - IMPLEMENTED, currently in final stage of development
*Tag a.k.a. Oni : the player is "it" (a.k.a. the Oni), alone against the AI. When an AI dies, it becomes the Oni : it respawns, and the player gets to control this new character. The old Oni becomes an enemy AI. - IMPLEMENTED, being added to release versions
*Capture The Flag : teams score points by stealing the enemy flag and bringing it home. - IN PROJECT
*Oni Rugby : teams score points by carrying an object (the ball) and marking a point with it in the enemy camp. - IN PROJECT
*Bonuses : Stuff like a fun shooting range with a score, not really an arena, but something we might want to throw in a pack.
*More bonuses : Advanced scripting choreography and camera management (fighting/dancing/moviemaking)...
*Other stuff, not clearly defined yet

Both time limit and frag limit are supported in the most recent DM packs.

===Fighting modes===
*total melee : no weapons
*balanced gameplay : limited number of randomly chosen weapons.
*single-weapon gameplay : limited number of weapons of one given type.
Weapons can be given at respawn-time or they can be spawned on the ground.

==Where do I get it?==
The downloads section is in construction.

These are stand-alone scripts that install in a level's script folder and don't have [[IGMD/global|IGMD/global]] elements.
{| border="1" cellpadding="5" cellspacing="0" align="center"
|+'''ONI TEAM ARENA 1.0 (TEAM DEATHMATCH) OUTDATED'''
|-
!Available
!Certified (YES/NO)
!Stable (YES/NO)
!Readme file
|-
|[http://geyser.oni2.net/OniTeamArena/ota_1/roof_arena.zip ROOFTOPS DM PACK]
|YES
|YES
|[http://geyser.oni2.net/OniTeamArena/ota_1/roof_arena/README.TXT README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/ACC2.zip ATMOSPHERIC PROCESSORS 2 DM PACK]
|YES
|YES
|[http://your-mom.oni2.net/Help%20and%20Troubleshooting%20Items/readme_acc2.txt README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/SMC.zip SYNDICATE MOUNTAIN COMPOUND DM PACK]
|YES
|YES
|[http://your-mom.oni2.net/Help%20and%20Troubleshooting%20Items/readme_smc.txt README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/TSP.zip TCTF SCIENCE PRISON DM PACK]
|YES
|YES
|[http://your-mom.oni2.net/Help%20and%20Troubleshooting%20Items/readme_tsp.txt README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/RSB_arena.zip REGIONAL STATE BUILDING DM PACK]
|YES
|YES
|[http://your-mom.oni2.net/Help%20and%20Troubleshooting%20Items/readme_rsb.txt README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/Brl_Arena.zip BIO RESEARCH LAB DM PACK]
|YES
|NO
|[http://your-mom.oni2.net/Help%20and%20Troubleshooting%20Items/readme_brl.txt README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/ACH.zip AIRPORT CARGO HANGARS DM PACK]
|YES
|YES
|[http://your-mom.oni2.net/Help%20and%20Troubleshooting%20Items/readme_ach.txt README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/TRH.zip TCTF REGIONAL HQ DM PACK]
|YES
|YES
|NOT AVAILABLE
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/MMP.zip MUSASHI MANUFACTURING DM PACK]
|YES
|YES
|NOT AVAILABLE
|-
||[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/DHL.zip KONOKO'S DREAM WORLD DM PACK]
|YES
|YES
|NOT AVAILABLE
|}

{| border="1" cellpadding="5" cellspacing="0" align="center"
|+'''ONI TEAM ARENA 1.1 (TEAM DEATHMATCH)'''
|-
!Available
!Certified (YES/NO)
!Stable (YES/NO)
!Readme file
|-
|[http://geyser.oni2.net/OniTeamArena/ota1_1/roofDM1_1.zip ROOFTOPS DM PACK]
|YES
|YES
|[http://geyser.oni2.net/OniTeamArena/ota1_1/roof_arena/README.TXT README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20V.1.1/ACC(2)_1.1.zip ATMOSPHERIC PROCESSORS 2 DM PACK]
|YES
|YES (?)
|NOT AVAILABLE (Included in ZIP)
|-
|[http://geyser.oni2.net/OniTeamArena/WIP/HQfixed.zip TCTF REGIONAL HQ DM PACK]
|YES
|YES
|NOT AVAILABLE (Included in ZIP)
|-
|[http://geyser.oni2.net/OniTeamArena/WIP/ABPbis.zip AIRPORT ASSAULT DM PACK]
|YES
|YES
|[http://geyser.oni2.net/OniTeamArena/ota1_1/AirportBatteryPack/README.TXT README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20V.1.1/SMC1.1.zip SYNDICATE MOUNTAIN COMPOUND DM PACK]
|YES
|YES* Requires Cache Fix [http://oni.bungie.org/community/forum/viewtopic.php?pid=2243#p2243 Here]
|NOT AVAILABLE (Included in ZIP)
|}
Global version coming soon...

[http://oni.bungie.org/forums/index.php?threadid=121&page=40#pager HERE] are a few recent builds. Check them out :)

==How can I help?==
Beta-testing of any available OTA release listed above is welcome. We have a stability issue (read : we get "Blam! Oni crashed") on some levels with the most recent and full-featured versions of OTA (1.1)

Please check back on this page now and then, download and test everything that doesn't have a YES/NO "Stable" label.
Any level labeled as "unstable" will get a dedicated crash report and discussion page.

Also, if you're interested in helping to cross-level port or debug, please contact us (contact links are at the top of the page).

[[Category:Scripts]]

Talk:Oni (folder)/GameDataFolder/IGMD

2008-02-11T02:37:31Z

Your Mom:

== What does IGMD stand for? ==

The only thing I can come up with is In-Game Meta Data... '''-YM'''

AE:OTA

2008-02-10T07:03:11Z

Your Mom: /* Where do I get it? */

{|align=right
|[[Image:ONK.png]]
|}
{|align=right border=1 cellspacing=0
|
{|cellspacing=0
!OTA TALK ON [http://oni.bungie.org/forums/ OCF]
|-
|*[http://oni.bungie.org/forums/index.php?threadid=142 Major releases]
|-
|*[http://oni.bungie.org/forums/index.php?threadid=121 Dev talk]
|}
|-
|
{|cellspacing=0
!CONTACT US
|-
|*[[User:Geyser|geyser]]
|-
|*[[User:Your_Mom|Your_Mom]]
|-
|*[http://edt.oni2.net EdT]
|}
|}

==Oni Team Arena (or OTA)==
Oni Team Arena is a series of scripts oriented on multiplayer gameplay. You don't get to fight human opponents, but Oni's AI are treated as respawning bots.

The interface is much inspired by that of existing FPS-shooters and other games supporting multiplayer.

Smart bot behaviour, challenge and entertainment are the main objectives. OTA is also a playground allowing us to test complex combat situations before they get implemented in projects like Oni 2.

We try to implement as many popular multiplayer features as possible: random spawn positions, random weapons and powerups, frag-related messages, sounds and visuals, bot model selection etc. In the case of advanced features like teleporters and jump platforms, we're limited by the original AI. Otherwise, anything goes.
--------
"We" is [[User:geyser|geyser]] for the core scripting, [[User:Your_Mom|Your_Mom]] for cross-level porting on PC, and (since recently) [http://edt.oni2.net EdT] for porting 1.1 onto Mac OS9. [http://script10000.oni2.net/ Script 10000] provided the initial idea.
-----------

==What exactly is Oni Team Arena?==
What we do is a large number of comparatively small arena-like setups in appropriate spots throughout Oni. There are two teams of bots, you get to lead one, and a boss character gets to lead the other.

The number of players can vary, but we try to make it large, starting at 16 (which is the number of network/online players supported by Serious Engine 2).

Teams don't just fight with each other, they score points and the first team to reach a set amount of points wins. There can be neutral characters who attack either team or just annoy everybody.

===Game modes===
*Team Deathmatch : teams score a frag every time a player of the opposite team dies. - IMPLEMENTED, currently in final stage of development
*Tag a.k.a. Oni : the player is "it" (a.k.a. the Oni), alone against the AI. When an AI dies, it becomes the Oni : it respawns, and the player gets to control this new character. The old Oni becomes an enemy AI. - IMPLEMENTED, being added to release versions
*Capture The Flag : teams score points by stealing the enemy flag and bringing it home. - IN PROJECT
*Oni Rugby : teams score points by carrying an object (the ball) and marking a point with it in the enemy camp. - IN PROJECT
*Bonuses : Stuff like a fun shooting range with a score, not really an arena, but something we might want to throw in a pack.
*More bonuses : Advanced scripting choreography and camera management (fighting/dancing/moviemaking)...
*Other stuff, not clearly defined yet

Both time limit and frag limit are supported in the most recent DM packs.

===Fighting modes===
*total melee : no weapons
*balanced gameplay : limited number of randomly chosen weapons.
*single-weapon gameplay : limited number of weapons of one given type.
Weapons can be given at respawn-time or they can be spawned on the ground.

==Where do I get it?==
The downloads section is in construction.

These are stand-alone scripts that install in a level's script folder and don't have [[IGMD/global|IGMD/global]] elements.
{| border="1" cellpadding="5" cellspacing="0" align="center"
|+'''ONI TEAM ARENA 1.0 (TEAM DEATHMATCH) OUTDATED'''
|-
!Available
!Certified (YES/NO)
!Stable (YES/NO)
!Readme file
|-
|[http://geyser.oni2.net/OniTeamArena/ota_1/roof_arena.zip ROOFTOPS DM PACK]
|YES
|YES
|[http://geyser.oni2.net/OniTeamArena/ota_1/roof_arena/README.TXT README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/ACC2.zip ATMOSPHERIC PROCESSORS 2 DM PACK]
|YES
|YES
|[http://your-mom.oni2.net/Help%20and%20Troubleshooting%20Items/readme_acc2.txt README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/SMC.zip SYNDICATE MOUNTAIN COMPOUND DM PACK]
|YES
|YES
|[http://your-mom.oni2.net/Help%20and%20Troubleshooting%20Items/readme_smc.txt README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/TSP.zip TCTF SCIENCE PRISON DM PACK]
|YES
|YES
|[http://your-mom.oni2.net/Help%20and%20Troubleshooting%20Items/readme_tsp.txt README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/RSB_arena.zip REGIONAL STATE BUILDING DM PACK]
|YES
|YES
|[http://your-mom.oni2.net/Help%20and%20Troubleshooting%20Items/readme_rsb.txt README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/Brl_arena.zip BIO RESEARCH LAB DM PACK]
|YES
|NO
|[http://your-mom.oni2.net/Help%20and%20Troubleshooting%20Items/readme_brl.txt README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/ACH.zip AIRPORT CARGO HANGARS DM PACK]
|YES
|YES
|[http://your-mom.oni2.net/Help%20and%20Troubleshooting%20Items/readme_ach.txt README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/TRH.zip TCTF REGIONAL HQ DM PACK]
|YES
|YES
|NOT AVAILABLE
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/MMP.zip MUSASHI MANUFACTURING DM PACK]
|YES
|YES
|NOT AVAILABLE
|-
||[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20v.1.0%20Scripts/DHL.zip KONOKO'S DREAM WORLD DM PACK]
|YES
|YES
|NOT AVAILABLE
|}

{| border="1" cellpadding="5" cellspacing="0" align="center"
|+'''ONI TEAM ARENA 1.1 (TEAM DEATHMATCH)'''
|-
!Available
!Certified (YES/NO)
!Stable (YES/NO)
!Readme file
|-
|[http://geyser.oni2.net/OniTeamArena/ota1_1/roofDM1_1.zip ROOFTOPS DM PACK]
|YES
|YES
|[http://geyser.oni2.net/OniTeamArena/ota1_1/roof_arena/README.TXT README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20V.1.1/ACC(2)_1.1.zip ATMOSPHERIC PROCESSORS 2 DM PACK]
|YES
|YES (?)
|NOT AVAILABLE (Included in ZIP)
|-
|[http://geyser.oni2.net/OniTeamArena/WIP/HQfixed.zip TCTF REGIONAL HQ DM PACK]
|YES
|YES
|NOT AVAILABLE (Included in ZIP)
|-
|[http://geyser.oni2.net/OniTeamArena/WIP/ABPbis.zip AIRPORT ASSAULT DM PACK]
|YES
|YES
|[http://geyser.oni2.net/OniTeamArena/ota1_1/AirportBatteryPack/README.TXT README.TXT]
|-
|[http://your-mom.oni2.net/Downloads/Arena%20Scripts/Arena%20V.1.1/SMC1.1.zip SYNDICATE MOUNTAIN COMPOUND DM PACK]
|YES
|YES* Requires Cache Fix [http://oni.bungie.org/community/forum/viewtopic.php?pid=2243#p2243 Here]
|NOT AVAILABLE (Included in ZIP)
|}
Global version coming soon...

[http://oni.bungie.org/forums/index.php?threadid=121&page=40#pager HERE] are a few recent builds. Check them out :)

==How can I help?==
Beta-testing of any available OTA release listed above is welcome. We have a stability issue (read : we get "Blam! Oni crashed") on some levels with the most recent and full-featured versions of OTA (1.1)

Please check back on this page now and then, download and test everything that doesn't have a YES/NO "Stable" label.
Any level labeled as "unstable" will get a dedicated crash report and discussion page.

Also, if you're interested in helping to cross-level port or debug, please contact us (contact links are at the top of the page).

AE:Warehouse

2007-08-10T03:51:15Z

Your Mom: /* Change log */

==Warehouse Mod==
===Download directory===
[http://geyser.oni2.net/ONK/warehouse/WarehouseMod HERE] (pay attention to the file sizes : it's over 30 megs...)
*level0_Final.rar holds level0_Final.dat and level0_Final.raw : they go in your [[GameDataFolder]] (backup the originals)
*OniLevel1a.rar holds level1_Final.dat and the level logic folder : the former goes in [[GameDataFolder]] (backup the original), the latter in [[GameDataFolder]]/[[OSL:IGMD|IGMD]], replacing the original [[OSL:IGMD/EnvWarehouse|EnvWarehouse]] folder (which you should backup too : rename it or move it away)
*OniLevel1b.rar holds level1_Final.raw, which goes in [[GameDataFolder]] as well (backup the original)
===Sorta change log===
Adding text files to the download directory above some time, maybe...
====level0_Final====
Globally effective changes
*Swapped run/dash anims for Strikers and Comguys (affects everyone except Thugs, Tankers, Ninjas, Elites and Mutant Muro)
*Swapped particle tracks (flashier combos)
*Striker front throw replaced with Comguy disarm (flashier, looks like a Fury throw)
*Konoko's front kick throw replaced with stepping disarm (no crowd-clearing effect)
*One of Konoko's running kick throws replaced with a Running Lariat
*Something with the Sledgehammer Heel
*Konoko's combos ''not'' unlocked
*Other stuff
====level1_Final====
*Relocated (hidden) datapad
*Much healthier AI
*Ninja particles for "Ninja Bots"
*Thugs fight like Griffin
*Other stuff
====EnvWarehouse====
Completely rewritten level logic, surprise, surprise!
*Scripted combo overrides for boss fight
*Scripted weapon holstering for some AI
*Locked doors (must seek alternate routes)
*(Annoyingly) hard fights
*Plenty ways to lose (e.g. warehouse manager can die...)
*Controllable warehouse manager (nice, but buggy)
*Other stuff

----
==Warehouse Mod Too==
===Planned changes aka "what I WANT in it", not "what WILL be in it"===
[[ONK_talk:Warehouse|DISCUSSION]]
====level0_Final====
Globally effective changes
*edit some melee files for new experience (we are used to old patterns)
''(Don't minimize the impact of scripting and exotic MELE/TRAC pairing. I wouldn't touch the "old" melee patterns without a '''very''' good reason. [[User:Geyser|geyser]])
*edit some combat files for better AI behavior
*edit some weapon files, add secondary fire mode (tribute to Geyser), make AI smarter with guns and aganist guns*
''(Those two are complementary, and further complemented by level-and-ONCC-specific [[OBD:ONCC#0x15C_-_0x293|AI skills]]. Handle with care. [[User:Geyser|geyser]])

''(In particular, secondary fire modes need to have consistent AI skill ID, for the AI to use appropriate fire rate etc. Every ONCC needs to be edited accordingly, which is a lot of work. And ONCC are not patch-friendly. Dunno. [[User:Geyser|geyser]])
*flashy attacks again but this time better used particles (I hope)
*maybe something else
*try a little experiment: take A_t48 thug in EnvWarehouse and make him invincible. Then get w1_tap(Equalizer) or w2_sap(Black adder) and turn on superammo cheat. Now startle thug, don't shoot. Lead him to the side opposite of the locked door which leads out of the building. Now dash to the door (so there is big hole between you and thug) and start permanent fire. You will see that after second or two he begins to strafe and he's trying to hide behind corners and objects. If he's too close, he will attack you. Problem is that w1_tap and w2_sap are only guns with that effect. Aganist other ones he just run towards his death.

''(Actually (see [[OBD:ONWC|HERE]]), the weapons originally using that feature are w1_tap, w2_sap and w4_psm. The effect is harder to notice with w4_psm, because AI often get knocked down before they can dodge or run for cover. [[User:Geyser|geyser]])
====level1_Final====
Changes to level 1 binaries
*edit characters ONCC files, add idle animations for some chars, health correction, some AI events(rotation, getups etc)
''("correction", heh... not feeling too good about that, somehow... [[User:Geyser|geyser]])
*mix few textures and models to create Casey Shanagan character ''(obstinately misspelling him, huh? [[User:Geyser|geyser]])''
''(I'd say Karen's head mesh, definitely, with a slightly modified female skeleton, upscaled. [[User:Geyser|geyser]])
*edit thug TRAC so it will be Casey's TRAC. try to edit some thug TRAMs into Casey's unique fight style*
''(You can handle Casey the same way as a boss, script-mixing anims from different TRAC, without changing anything to the binary. [[User:Geyser|geyser]])
*TRAC game: Thugs will receive Comguy TRAC, Casey will receive changed Thug TRAC, Kojiro and his minions will have Ninja TRAC
''(I'd say make it low priority. Unless it's not too time consuming, just leave it : we may have an animating pipeline Soon(TM). [[User:Geyser|geyser]])
*'''edit character bina file in way I need (renamed characters, changed patrols, switched character classes etc.)
*'''edit flag bina file in way I need
*'''edit patrol paths bina file, again try to refresh game experience
*'''edit some trigger volumes bina files in way I need(mainly positions)
''(Those four : a) are most important for custom level logic; b) can be released as 100% PC/Mac-compatible OUP patches. High priority. Edit the RAW part, export from OUP, share. [[User:Geyser|geyser]])
*edit some TXMPs and TXANs, try to create some moving monitors as it was in trailer
''(Eye candy. Not too portable at the moment. Low priority. [[User:Geyser|geyser]])
*probably all ^_-
*I welcome any tips and hints for his moves.Please write them to {{OCF}}. But remember: Those moves can't be as clean and perfect as original because I can only reverse hack them (I don't have Bungie's animation program).
''(We could be able to exchange Oni animation tracks with a semi-professional animating tool some time soon. Working on it. [[User:Geyser|geyser]])
====EnvWarehouse====
Scripted level logic
*this time totally rewritten, not just improved original
''(Lots of non-linearities, I hope... [[User:Geyser|geyser]])''
*again holstering enemies, this time I hope that in combination with Combat.bina file hack it will be more useful
''(There are pretty reliable way to script that. How about a few practical code samples : a mini-script with one smart AI or two? [[User:Geyser|geyser]])
*some boss fight surprises
''(I have a few ideas in store : some of them I've already talked about on {{OCF}}. Curious about yours. [[User:Geyser|geyser]])
*again alternate routes
''(Jetpacks, powersuits, and more generally slightly enhanced jumping could make new routes possible.. [[User:Geyser|geyser]])

''(I'd reveal the 15 hidden doors. Either by scripting, or in binary (have to find the quads first...). Fixing the pathfinding grids would be great, too. [[User:Geyser|geyser]])
*a bit rewritten story*, possibility of two alternate endings of this level, which can affect next level gameplay
*through the level you will play as Konoko and as Casey(depends on situations)
*something more???
*For Geyser: I would like to talk only with you about this. I want this mod to be entertaining so players can't know all details now. Plus your sharp critics. :)
''(PM/mail details, discuss more general ideas here. Honestly, the wiki isn't all that popular so far, and as for those who read it, a big '''SPOILER WARNING : DEVELOPER AREA''' should be dissuasive enough : if they want to enjoy the mod, they just won't read any further. [[User:Geyser|geyser]])

Overall, if this mod is successful (or ever made ^_^'), I will create another one of level two with alternate storylines (depends on ending of level 1). Long-time goal is to remake whole game :)

''(Hey, that's what [[ONK:ONK|ONK]] is all about. Welcome on board. [[User:Geyser|geyser]])

Written by Loser 26th July 2006
----

==Derived==
===Warehouse Mod Minus The Warehouse===
Basically the global component of the Warehouse Mod above : get it [http://geyser.oni2.net/ONK/warehouse/GlobalHacks/level0_Enhanced.rar HERE] (11 MB)

(both files in the archive should go in [[GameDataFolder]], backup the originals, yada yada)
====Change log====
Detailed change logs : [http://geyser.oni2.net/ONK/warehouse/GlobalHacks/dat.log DAT] [http://geyser.oni2.net/ONK/warehouse/GlobalHacks/raw.log RAW]
*Unlocked all of Konoko's combos
*"Pseudo-dashing" for Konoko, Strikers and Comguys (running TRAMS link to same resources as sprinting TRAMS)
**All characters are affected except Thugs, Tankers, Ninjas, Elites and Mutant Muro
**Player is also affected (i.e. Konoko pseudo-dashes instead of running)
**Konoko's sliding is enabled for pseudo-dashing to avoid frustration ^^
*Flashy particles for :
**Dashing and "pseudo-dashing"
**Spinning Sidekick (KONCOMcomb_k_k_k)
**Triple-Hit Haymaker (KONCOMcomb_p_p_p)
**Sledgehammer Heel (KONCOMcomb_p_p_k)
**Crescent Kick (KONCOMcomb_k_k_kfw)
**Twister Kicks (KONCOMlt_fw_kick/KONCOMrt_fw_kick)
**Striker Triple Kick (STRCOMcomb_k_k_k)
**Striker Triple Punch (STRCOMcomb_p_p_p)
**Comguy Triple Punch (COMCOMcomb_p_p_p)
**Comguy Double Kick (COMCOMcomb_k_k)
*"Radio Saber!" alternates at random with "Static Fist!"
*Muro's glows and trails are made framerate-friendlier (mercilessly trimmed)
And that's about it...

AE:BIP

2007-08-08T01:45:07Z

Your Mom: /* Downloading */

== The Binary Improvement Project ==

The main objective of the Binary Improvement Project (BIP) will be to make extremely script-er friendly versions of all the *.dat and *.raw files. We will fix up mistakes left by the original coders, add a "hurt" and a "death" trigger for each character, and improve the binaries altogether. Making it much easier to script for beginners and experts alike.

If you have a Hex Editor, an iron will, and want to help out, feel free to contribute your edited *.dat and *.raw files!

To read up on discussion on this topic, go [http://mukade.bungie.org/cgi-bin/mukade/ikonboard.cgi?s=6516029ae2bf986cdebc05c192858e22;act=ST;f=3;t=205 here]

==Project Points==
===Global improvements (level 0)===
*Unlocked combat moves for Konoko and female civilians
*Two new weapons : WMC Lite (a WMC you can run with and that everybody can collect and reload) and F3 - Framerate Friendly Fireworks
*Cool-looking particles for special moves of basic character classes : Konoko, Comguys, Strikers.
*run=dash, so AI automatically dash instead of running (for everyone but Elites, Ninjas, Tankers and Thugs)
The last point (dashing AI) has a few issues in its current state, so I propose we switch to Alloc's Trainer for a change.
===Level-specific improvements===
*Systematic names for AI and related events (hurt, death, dying, reload, etc), for more powerful scripting
*Improved AI (using complex AI melee patterns rather than basic ones)
*Wider range of spawnable characters (more random skins, harder enemy types, more enemy types where available)
*New enemy type (Comguy with Ninja skills) in levels 1, 12 and 19
*AI-endowed Konoko for all levels (Players will now use "ai_0" as their player character)
*More

== Downloading ==

WARNING: HUGE FILES

The ones currently available are the first generation.
They only contain functions for death and hurt. (And some other things which you must find out on your own :p)

{| border="1" cellpadding="5" cellspacing="0" align="center"
|+'''THE BINARY IMPROVEMENT PROJECT'''
|-
!Level
!Download File
|-
|level0_Final
|Available *
|-
|level1_Final
|Available
|-
|level2_Final
|Coming Soon
|-
|level3_Final
|Coming Soon
|-
|level4_Final
|Coming Soon
|-
|level6_Final
|Coming Soon
|-
|level8_Final
|Coming Soon
|-
|level9_Final
|Coming Soon
|-
|level10_Final
|Coming Soon
|-
|level11_Final
|Coming Soon
|-
|level12_Final
|Coming Soon
|-
|level13_Final
|Coming Soon
|-
|level14_Final
|Coming Soon
|-
|level18_Final
|Coming Soon
|-
|level19_Final
|Available [http://your_mom.oni2.net/Downloads/CompoundB.rar HERE!]
|}

*technically, level0_Final is not part of the project. Level0_final improves the overall game rather than a specific level, but it is awesome nonetheless. It allows AI to dash when unarmed and has improved particles.

'''Ok, File(s) Back Online (well, mine, Loser's are gone :S )'''

AE:BIP

2007-08-08T01:44:25Z

Your Mom: /* Downloading */

Oni (folder)/GameDataFolder/IGMD/compound

2007-07-14T19:55:51Z

Your Mom: /* Available mods */

==Level logic for Chapter 14:DAWN OF THE CHRYSALIS==
aka '''Syndicate Mountain Compound''' (Sturmanderung)
===Associated binaries===
*level19_Final.dat
*level19_Final.raw
===Original contents===
*[http://geyser.oni2.net/OSL/IGMD/compound/compound.bsl compound.bsl]
*[http://geyser.oni2.net/OSL/IGMD/compound/compound_cutscene.bsl compound_cutscene.bsl]
*[http://geyser.oni2.net/OSL/IGMD/compound/compound_main.bsl compound_main.bsl]
*[http://geyser.oni2.net/OSL/IGMD/compound/particle_scripts.bsl particle_scripts.bsl]

==="Overcommented" version (not online yet)===
*compound.bsl
*compound_cutscene.bsl
*compound_main.bsl
*particle_scripts.bsl
===Rewritten version (not online yet)===
*different filenames...

==Available mods==

*[http://your_mom.oni2.net/Downloads/My%20Other%20Scripts/mountainrallyv1.1.zip MR 1.1]
*[http://your_mom.oni2.net/Downloads/Scripts%20By%20Various%20Authors/Mirage.zip Mirage]

==Related issues==

Oni (folder)/GameDataFolder/IGMD/compound

2007-07-14T19:55:35Z

Your Mom: /* Available mods */

==Level logic for Chapter 14:DAWN OF THE CHRYSALIS==
aka '''Syndicate Mountain Compound''' (Sturmanderung)
===Associated binaries===
*level19_Final.dat
*level19_Final.raw
===Original contents===
*[http://geyser.oni2.net/OSL/IGMD/compound/compound.bsl compound.bsl]
*[http://geyser.oni2.net/OSL/IGMD/compound/compound_cutscene.bsl compound_cutscene.bsl]
*[http://geyser.oni2.net/OSL/IGMD/compound/compound_main.bsl compound_main.bsl]
*[http://geyser.oni2.net/OSL/IGMD/compound/particle_scripts.bsl particle_scripts.bsl]

==="Overcommented" version (not online yet)===
*compound.bsl
*compound_cutscene.bsl
*compound_main.bsl
*particle_scripts.bsl
===Rewritten version (not online yet)===
*different filenames...

==Available mods==

[http://your_mom.oni2.net/Downloads/My%20Other%20Scripts/mountainrallyv1.1.zip MR 1.1] 
[http://your_mom.oni2.net/Downloads/Scripts%20By%20Various%20Authors/Mirage.zip Mirage]

==Related issues==

Oni (folder)/GameDataFolder/IGMD/compound

2007-07-14T19:55:26Z

Your Mom: /* Available mods */

==Level logic for Chapter 14:DAWN OF THE CHRYSALIS==
aka '''Syndicate Mountain Compound''' (Sturmanderung)
===Associated binaries===
*level19_Final.dat
*level19_Final.raw
===Original contents===
*[http://geyser.oni2.net/OSL/IGMD/compound/compound.bsl compound.bsl]
*[http://geyser.oni2.net/OSL/IGMD/compound/compound_cutscene.bsl compound_cutscene.bsl]
*[http://geyser.oni2.net/OSL/IGMD/compound/compound_main.bsl compound_main.bsl]
*[http://geyser.oni2.net/OSL/IGMD/compound/particle_scripts.bsl particle_scripts.bsl]

==="Overcommented" version (not online yet)===
*compound.bsl
*compound_cutscene.bsl
*compound_main.bsl
*particle_scripts.bsl
===Rewritten version (not online yet)===
*different filenames...

==Available mods==

[http://your_mom.oni2.net/Downloads/My%20Other%20Scripts/mountainrallyv1.1.zip MR 1.1]
[http://your_mom.oni2.net/Downloads/Scripts%20By%20Various%20Authors/Mirage.zip Mirage]

==Related issues==

User:Your Mom

2007-02-15T03:11:56Z

Your Mom:

*Real Name: <Unknown>
*Birthday: February
*Job: <Unknown>
*Email: rcmpyourmom@hotmail.com

== Website ==
[http://your_mom.oni2.net/ Link]
After a year and three months, I have resumed work on the website. Hopefully, I can remeber enough finish the Analysis and Secrets, though those should really be, and are, here. If I can find my old TXT files, I'll upload em all...

== I'M NOT DEAD! ==

I haven't played Oni in a while, I forgot what scripts and HEX-edited things I had and ended up giving up trying to restore it (all me levels came out blank). I've forgotten most of the stuff, thank goodness for programming at school keeping me in tough with my FUNCs and VARs. Else i'd be totally lost into HTML and XML /CSS that I'd have no room left in my brain for um...actual coding? Scripting? whatever.

If you people ever check this, its not that I don't want to register on the new forums, I've tried several times, it just keeps giving me an error, something about timing out. Anyhow, don't expect anything from me anytime soon, but I'm feeling all nostalgic. I feel like opening up those *.BSL files and writing a new story script. I feel like running Un-Packer and making my own weapons. I can't do that anymore though. I have my obligations and deadlines to hold up both in life and the modding world (mod teams), as well as a community to please over at Star Wars Empire at War. I've never forgotten this game, Oni, and its lure - it dragged me into modding and into intrest in coding and programming. In a sense, this started my current career path. Ify ou ever manage to get those models exported, or if someone with 3D-Studio max would liek to model for me, I'd make a mod for that game, though its not the best engine, I'm wasting the space engine and the galactic map, but hey, I'd like to see the troops and heroes again. Maybe I can spark interst and make a squad-based FPS. Anyhow, good on this community for trying without mod tools. Makes it so only the most elite can produce high-quality mods. I haven't seen a n00b here yet ;)

Well, there's much I want to write, but hey, why right it if noone's going to read it? this is probably going to be buried under centuries of dust with noone to take a look at it.

I'll check back in a week or so, and that may be the last time. Not sure. Depending on what I feedback I get here.

Bye for now,

Your_Mom (What a fool I was choosing this name, I would much rather sign "D803" or "Droid #803" or even Unit-803 (Star wars thing)). Well, it goes to show how one changes.
----
:Hm, what kind of feedback are you expecting?
:I remember you, if that's what you're asking.
:3D stuff ''might'' be exportable... Soon(TM).
:But I tend to promise less rather than more.
:Good to know you're not dead, anyway.
:Weird how you can't register on the new {{OCF}}
::(looks like job for the Troubleshooter in Chief)
:Cheerios
::[[User:Geyser|geyser]] 19:13, 12 February 2007 (CET)

----
That (^) would have done.
Not gone and forgotten, might pick up modding this again. A great game, I want to go beat up some strikers again...
Well, anyhow, I need a refresher as to what's new in the way of the BIP, or if it died or something. Same with OTA.
I'll try registering again to see if it makes a difference...

Specifically, this is what it says:

An error was encountered
Error: Could not connect to smtp host "bungie.org" (60) (Operation timed out).

Thats two account names and two emails tried...no cigar. Apparently it creates the account, but it doesn't send me my confirmation email, therefore I can't login since I don't know my password... :(

-Y_M
----
:Harry says you should try and register again.
::[[User:Geyser|geyser]] 01:43, 15 February 2007 (CET)
:No can do for a thorough update on the projects...
:Too busy working on them ^^ Public overviews are the way.
:Basically, BIP and OTA are all part of [[ONK:ONK|ONK]] now.
:They're not dead by any means. There's a lot of hot new OBD stuff.
:However, there's no proper release apart from Loser's [[ONK:Warehouse|Warehouse Minus]] (beefed-up level0_Final)
:OUP still can't patch DAT stuff in a user-friendly (cross-version-compatible) way.
:But RAW stuff (BINA, TRAM tracks can very well be released as neat bundles).
:Loser has released a few such things, but nothing close to a "release" ^^
:(putting those together is probably more annoying than "experimenting")
:Loser has done a lot of things apart from that: moveable furniture, ''much'' smarter AI...
::but none of that has been relelased yet. Loser tries to cram it all into Warehouse Too
:::(unfortunately not in a modular and globally useful way, I'm afraid; we should talk)
:As for OTA, I hate to say that I didn't release anything since the Dev Mode came out.
::nothing but the pre-alpha of OTA2 that you had already seen.
:::I'm working on a completely new core, though. OTA3 or something.
::Looks really cool, but unfortunately it's mostly in my head, so you can't really enjoy it ^^
:::I'm distilling primary features (interface) one by one, and actual gameplay is secondary ATM.
::But it will be there. Will have to. I want OTA to totally rock by the end of the year.
:(it's already praised as the best Oni script mod "evah" by independent critics... congrats ^^ )
:EdT and you have really done a great job on that one... Thanks again, and welcome back...
::[[User:Geyser|geyser]] 01:43, 15 February 2007 (CET)

----
Affirmative, I'll try registering again...or...just sending that email to me :) EDIT: Worked :D

I'll just opt for a clean re-install of the game and hope it works again...
Modding in the other community has died down for now, its hit a dead phase. So, mght as well [ick up work again here, unless I forget about it again (I'm absent-minded of thing's I'm not immediately aware of need of doing). If you're still in need of a porter, there might be something I can do, giving its not too complex...I hope I remeber which values to change... So a combined thing, nice. OTA was fun with BIP-improved levels...in fact, I found it the easy way of testing the changes, rather than just play through the level...

Good to be back,
-Y_M

User:Your Mom

2007-02-15T02:44:37Z

Your Mom:

*Real Name: <Unknown>
*Birthday: February
*Job: <Unknown>
*Email: rcmpyourmom@hotmail.com

== Website ==
[http://your_mom.oni2.net/ Link]
After a year and three months, I have resumed work on the website. Hopefully, I can remeber enough finish the Analysis and Secrets, though those should really be, and are, here. If I can find my old TXT files, I'll upload em all...

== I'M NOT DEAD! ==

I haven't played Oni in a while, I forgot what scripts and HEX-edited things I had and ended up giving up trying to restore it (all me levels came out blank). I've forgotten most of the stuff, thank goodness for programming at school keeping me in tough with my FUNCs and VARs. Else i'd be totally lost into HTML and XML /CSS that I'd have no room left in my brain for um...actual coding? Scripting? whatever.

If you people ever check this, its not that I don't want to register on the new forums, I've tried several times, it just keeps giving me an error, something about timing out. Anyhow, don't expect anything from me anytime soon, but I'm feeling all nostalgic. I feel like opening up those *.BSL files and writing a new story script. I feel like running Un-Packer and making my own weapons. I can't do that anymore though. I have my obligations and deadlines to hold up both in life and the modding world (mod teams), as well as a community to please over at Star Wars Empire at War. I've never forgotten this game, Oni, and its lure - it dragged me into modding and into intrest in coding and programming. In a sense, this started my current career path. Ify ou ever manage to get those models exported, or if someone with 3D-Studio max would liek to model for me, I'd make a mod for that game, though its not the best engine, I'm wasting the space engine and the galactic map, but hey, I'd like to see the troops and heroes again. Maybe I can spark interst and make a squad-based FPS. Anyhow, good on this community for trying without mod tools. Makes it so only the most elite can produce high-quality mods. I haven't seen a n00b here yet ;)

Well, there's much I want to write, but hey, why right it if noone's going to read it? this is probably going to be buried under centuries of dust with noone to take a look at it.

I'll check back in a week or so, and that may be the last time. Not sure. Depending on what I feedback I get here.

Bye for now,

Your_Mom (What a fool I was choosing this name, I would much rather sign "D803" or "Droid #803" or even Unit-803 (Star wars thing)). Well, it goes to show how one changes.
----
:Hm, what kind of feedback are you expecting?
:I remember you, if that's what you're asking.
:3D stuff ''might'' be exportable... Soon(TM).
:But I tend to promise less rather than more.
:Good to know you're not dead, anyway.
:Weird how you can't register on the new {{OCF}}
::(looks like job for the Troubleshooter in Chief)
:Cheerios
::[[User:Geyser|geyser]] 19:13, 12 February 2007 (CET)

----
That (^) would have done.
Not gone and forgotten, might pick up modding this again. A great game, I want to go beat up some strikers again...
Well, anyhow, I need a refresher as to what's new in the way of the BIP, or if it died or something. Same with OTA.
I'll try registering again to see if it makes a difference...

Specifically, this is what it says:

An error was encountered
Error: Could not connect to smtp host "bungie.org" (60) (Operation timed out).

Thats two account names and two emails tried...no cigar. Apparently it creates the account, but it doesn't send me my confirmation email, therefore I can't login since I don't know my password... :(

-Y_M
----
:Harry says you should try and register again.
::[[User:Geyser|geyser]] 01:43, 15 February 2007 (CET)
:No can do for a thorough update on the projects...
:Too busy working on them ^^ Public overviews are the way.
:Basically, BIP and OTA are all part of [[ONK:ONK|ONK]] now.
:They're not dead by any means. There's a lot of hot new OBD stuff.
:However, there's no proper release apart from Loser's [[ONK:Warehouse|Warehouse Minus]] (beefed-up level0_Final)
:OUP still can't patch DAT stuff in a user-friendly (cross-version-compatible) way.
:But RAW stuff (BINA, TRAM tracks can very well be released as neat bundles).
:Loser has released a few such things, but nothing close to a "release" ^^
:(putting those together is probably more annoying than "experimenting")
:Loser has done a lot of things apart from that: moveable furniture, ''much'' smarter AI...
::but none of that has been relelased yet. Loser tries to cram it all into Warehouse Too
:::(unfortunately not in a modular and globally useful way, I'm afraid; we should talk)
:As for OTA, I hate to say that I didn't release anything since the Dev Mode came out.
::nothing but the pre-alpha of OTA2 that you had already seen.
:::I'm working on a completely new core, though. OTA3 or something.
::Looks really cool, but unfortunately it's mostly in my head, so you can't really enjoy it ^^
:::I'm distilling primary features (interface) one by one, and actual gameplay is secondary ATM.
::But it will be there. Will have to. I want OTA to totally rock by the end of the year.
:(it's already praised as the best Oni script mod "evah" by independent critics... congrats ^^ )
:EdT and you have really done a great job on that one... Thanks again, and welcome back...
::[[User:Geyser|geyser]] 01:43, 15 February 2007 (CET)

----
Affirmative, I'll try registering again...wait, tell Harry to delete the "Your_Mom" and "Droid" accounts...I don't have anymore email adresses and I can't register using an email adress I'v already used...

I'll just opt for a clean re-install of the game and hope it works again...
Modding in the other community has died down for now, its hit a dead phase. So, mght as well [ick up work again here, unless I forget about it again (I'm absent-minded of thing's I'm not immediately aware of need of doing). If you're still in need of a porter, there might be something I can do, giving its not too complex...I hope I remeber which values to change... So a combined thing, nice. OTA was fun with BIP-improved levels...in fact, I found it the easy way of testing the changes, rather than just play through the level...

Good to be back,
-Y_M

User:Your Mom

2007-02-15T01:33:18Z

Your Mom:

*Real Name: <Unknown>
*Birthday: February
*Job: <Unknown>
*Email: rcmpyourmom@hotmail.com

== Website ==
[http://your_mom.oni2.net/ Link]
After a year and three months, I have resumed work on the website. Hopefully, I can remeber enough finish the Analysis and Secrets, though those should really be, and are, here. If I can find my old TXT files, I'll upload em all...

== I'M NOT DEAD! ==

I haven't played Oni in a while, I forgot what scripts and HEX-edited things I had and ended up giving up trying to restore it (all me levels came out blank). I've forgotten most of the stuff, thank goodness for programming at school keeping me in tough with my FUNCs and VARs. Else i'd be totally lost into HTML and XML /CSS that I'd have no room left in my brain for um...actual coding? Scripting? whatever.

If you people ever check this, its not that I don't want to register on the new forums, I've tried several times, it just keeps giving me an error, something about timing out. Anyhow, don't expect anything from me anytime soon, but I'm feeling all nostalgic. I feel like opening up those *.BSL files and writing a new story script. I feel like running Un-Packer and making my own weapons. I can't do that anymore though. I have my obligations and deadlines to hold up both in life and the modding world (mod teams), as well as a community to please over at Star Wars Empire at War. I've never forgotten this game, Oni, and its lure - it dragged me into modding and into intrest in coding and programming. In a sense, this started my current career path. Ify ou ever manage to get those models exported, or if someone with 3D-Studio max would liek to model for me, I'd make a mod for that game, though its not the best engine, I'm wasting the space engine and the galactic map, but hey, I'd like to see the troops and heroes again. Maybe I can spark interst and make a squad-based FPS. Anyhow, good on this community for trying without mod tools. Makes it so only the most elite can produce high-quality mods. I haven't seen a n00b here yet ;)

Well, there's much I want to write, but hey, why right it if noone's going to read it? this is probably going to be buried under centuries of dust with noone to take a look at it.

I'll check back in a week or so, and that may be the last time. Not sure. Depending on what I feedback I get here.

Bye for now,

Your_Mom (What a fool I was choosing this name, I would much rather sign "D803" or "Droid #803" or even Unit-803 (Star wars thing)). Well, it goes to show how one changes.
----
:Hm, what kind of feedback are you expecting?
:I remember you, if that's what you're asking.
:3D stuff ''might'' be exportable... Soon(TM).
:But I tend to promise less rather than more.
:Good to know you're not dead, anyway.
:Weird how you can't register on the new {{OCF}}
::(looks like job for the Troubleshooter in Chief)
:Cheerios
::[[User:Geyser|geyser]] 19:13, 12 February 2007 (CET)

----
That (^) would have done.
Not gone and forgotten, might pick up modding this again. A great game, I want to go beat up some strikers again...
Well, anyhow, I need a refresher as to what's new in the way of the BIP, or if it died or something. Same with OTA.
I'll try registering again to see if it makes a difference...

Specifically, this is what it says:

An error was encountered
Error: Could not connect to smtp host "bungie.org" (60) (Operation timed out).

Thats two account names and two emails tried...no cigar. Apparently it creates the account, but it doesn't send me my confirmation email, therefore I can't login since I don't know my password... :(

-Y_M
----
:Harry says you should try and register again.
::[[User:Geyser|geyser]] 01:43, 15 February 2007 (CET)
:No can do for a thorough update on the projects...
:Too busy working on them ^^ Public overviews are the way.
:Basically, BIP and OTA are all part of [[ONK:ONK|ONK]] now.
:They're not dead by any means. There's a lot of hot new OBD stuff.
:However, there's no proper release apart from Loser's [[ONK:Warehouse|Warehouse Minus]] (beefed-up level0_Final)
:OUP still can't patch DAT stuff in a user-friendly (cross-version-compatible) way.
:But RAW stuff (BINA, TRAM tracks can very well be released as neat bundles).
:Loser has released a few such things, but nothing close to a "release" ^^
:(putting those together is probably more annoying than "experimenting")
:Loser has done a lot of things apart from that: moveable furniture, ''much'' smarter AI...
::but none of that has been relelased yet. Loser tries to cram it all into Warehouse Too
:::(unfortunately not in a modular and globally useful way, I'm afraid; we should talk)
:As for OTA, I hate to say that I didn't release anything since the Dev Mode came out.
::nothing but the pre-alpha of OTA2 that you had already seen.
:::I'm working on a completely new core, though. OTA3 or something.
::Looks really cool, but unfortunately it's mostly in my head, so you can't really enjoy it ^^
:::I'm distilling primary features (interface) one by one, and actual gameplay is secondary ATM.
::But it will be there. Will have to. I want OTA to totally rock by the end of the year.
:(it's already praised as the best Oni script mod "evah" by independent critics... congrats ^^ )
:EdT and you have really done a great job on that one... Thanks again, and welcome back...
::[[User:Geyser|geyser]] 01:43, 15 February 2007 (CET)

----
Affirmative, I'll try registering again.
I'll just opt for a clean re-install of the game and hope it works again...
Modding in the other community has died down for now, its hit a dead phase. So, mght as well [ick up work again here, unless I forget about it again (I'm absent-minded of thing's I'm not immediately aware of need of doing). If you're still in need of a porter, there might be something I can do, giving its not too complex...I hope I remeber which values to change... So a combined thing, nice. OTA was fun with BIP-improved levels...in fact, I found it the easy way of testing the changes, rather than just play through the level...

Good to be back,
-Y_M

User:Your Mom

2007-02-13T04:59:05Z

Your Mom:

User:Your Mom

2007-02-13T03:41:15Z

Your Mom:

*Real Name: <Unknown>
*Birthday: February
*Job: <Unknown>
*Email: rcmpyourmom@hotmail.com

== I'M NOT DEAD! ==

I haven't played Oni in a while, I forgot what scripts and HEX-edited things I had and ended up giving up trying to restore it (all me levels came out blank). I've forgotten most of the stuff, thank goodness for programming at school keeping me in tough with my FUNCs and VARs. Else i'd be totally lost into HTML and XML /CSS that I'd have no room left in my brain for um...actual coding? Scripting? whatever.

If you people ever check this, its not that I don't want to register on the new forums, I've tried several times, it just keeps giving me an error, something about timing out. Anyhow, don't expect anything from me anytime soon, but I'm feeling all nostalgic. I feel like opening up those *.BSL files and writing a new story script. I feel like running Un-Packer and making my own weapons. I can't do that anymore though. I have my obligations and deadlines to hold up both in life and the modding world (mod teams), as well as a community to please over at Star Wars Empire at War. I've never forgotten this game, Oni, and its lure - it dragged me into modding and into intrest in coding and programming. In a sense, this started my current career path. Ify ou ever manage to get those models exported, or if someone with 3D-Studio max would liek to model for me, I'd make a mod for that game, though its not the best engine, I'm wasting the space engine and the galactic map, but hey, I'd like to see the troops and heroes again. Maybe I can spark interst and make a squad-based FPS. Anyhow, good on this community for trying without mod tools. Makes it so only the most elite can produce high-quality mods. I haven't seen a n00b here yet ;)

Well, there's much I want to write, but hey, why right it if noone's going to read it? this is probably going to be buried under centuries of dust with noone to take a look at it.

I'll check back in a week or so, and that may be the last time. Not sure. Depending on what I feedback I get here.

Bye for now,

Your_Mom (What a fool I was choosing this name, I would much rather sign "D803" or "Droid #803" or even Unit-803 (Star wars thing)). Well, it goes to show how one changes.
----
:Hm, what kind of feedback are you expecting?
:I remember you, if that's what you're asking.
:3D stuff ''might'' be exportable... Soon(TM).
:But I tend to promise less rather than more.
:Good to know you're not dead, anyway.
:Weird how you can't register on the new {{OCF}}
::(looks like job for the Troubleshooter in Chief)
:Cheerios
::[[User:Geyser|geyser]] 19:13, 12 February 2007 (CET)

----
That (^) would have done.
Not gone and forgotten, might pick up modding this again. A great game, I want to go beat up some strikers again...
Well, anyhow, I need a refresher as to what's new in the way of the BIP, or if it died or something. Same with OTA.
I'll try registering again to see if it makes a difference...

Specifically, this is what it says:

An error was encountered
Error: Could not connect to smtp host "bungie.org" (60) (Operation timed out).

Thats two account names and two emails tried...no cigar. Apparently it creates the account, but it doesn't send me my confirmation email, therefore I can't login since I don't know my password... :(

-Y_M

User:Your Mom

2007-02-13T03:40:49Z

Your Mom:

User:Your Mom

2007-02-13T03:37:16Z

Your Mom:

User:Your Mom

2007-02-11T06:04:18Z

Your Mom:

STURMANDERUNG

2006-05-07T05:02:24Z

Your Mom:

== Meaning ==
STURMANDERUNG, when broken into Sturm-änderung means storm-change in german.
This name fits because "Changing the Storm" would be "Changing the Weather", which is what it was designed to do. Although the word "änderung" isn't a violent change as suggested by the name, it should merely have been an overlook by the storyboard writers. Perhaps they just stuck it into the translator.

----

== Project: STURMANDERUNG ==
Project "Sturmanderung" was the name of [[Muro]]'s "master plan". It was to reprogram the world's [[Atmospheric Conversion Centers]] to putrefy the air rather than purify it. The obvious reason he doesn't care himself is because his [[Daodan Chyrasalis]] would change his body to adapt to the new environment. Most likey, he planned to implant one into most of his men, or have them wear gas masks.
The reason he started this project is unknown. Perhaps he wishes to profit by selling the chrysalis, posing as a savior. Perhaps he plans to wipe out the world's population. Whatever the reason, it was his master plan.

=== Components ===
The project was based at a Mountain Compound. At the heart of it lay the massive Sturmanderung Supercomputer, which controlled the core logic. A sattleite dish was built into a nearby bunker, and could be raised to the surface when the time came to initate the project. Several sattleites in orbit were to be used to rebound the signal to the Atmospheric Conversion Centers.

=== Endgame ===
When Konoko infiltrated the facility, she reprogrammed the signal to overload the stations rather than reverse them, and activated them before the sattleites were aligned, allowing some of the Atmospheric Conversion Centers to survive. In a final attmept to stop his sister, Muro faced her himself, and was killed, foiling the Syndicate Leader's plans for the final time. Whether or not Konoko's choice was a good one is debated, as it "saved" the world, but at a horrible cost.
<Insert Quotes Here>

Your_Mom

STURMANDERUNG

2006-05-05T01:00:00Z

Your Mom:

"StormChange"

More to Come...

Your_Mom

Pre-beta content

2006-05-05T00:56:27Z

Your Mom: /* Pre-beta levels */

{|align=right border=1
|'''Almost all available shots of pre-beta content are here, compared to final content when applicable Most pictures are half-sized (click to enlarge)'''
|}
==Final levels==
There are a few snapshots from the 1999 trailer worth adding... soon...
===Syndicate Warehouse===
There are 15 hidden doors there. When revealed, they turn this very linear level into a completely non-linear structure (more like a real warehouse).
{|
|+4 extra doors can be seen on the left picture
|[http://geyser.oni2.net/genesis/screenshots/EnvWarehouse/warehouse_old.jpg http://geyser.oni2.net/genesis/screenshots/EnvWarehouse/_warehouse_old.jpg]
|[http://geyser.oni2.net/genesis/screenshots/EnvWarehouse/warehouse_new.jpg http://geyser.oni2.net/genesis/screenshots/EnvWarehouse/_warehouse_new.jpg]
|}
A whole lotta crates have been added, different door textures... and the forklift is higher now.

----
===Manufacturing Plant (Musashi Manufacturing)===
This one has evolved quite a lot :
{|
|+The room where the "engines of evil" are, and the foyer
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic26.htm http://geyser.oni2.net/genesis/screenshots/_oni_26.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic42.htm http://geyser.oni2.net/genesis/screenshots/_oni_42.jpg]
|-
|http://geyser.oni2.net/genesis/screenshots/manplant/ot2_manplant1.jpg
|http://geyser.oni2.net/genesis/screenshots/manplant/ot2_manplant2.jpg
|}
Note the door from the foyer (last pic) : there was a corridor running through the middle of the building.

{|
|+Halls and ramps are almost unrecognizable because of the brick walls and wooden floor
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic51.htm http://geyser.oni2.net/genesis/screenshots/_oni_51.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic52.htm http://geyser.oni2.net/genesis/screenshots/_oni_52.jpg]
|}

{|
|+Inner flyway and back of the building
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic18.htm http://geyser.oni2.net/genesis/screenshots/_oni_18.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic38.htm http://geyser.oni2.net/genesis/screenshots/_oni_38.jpg]
|-
|http://geyser.oni2.net/genesis/May_1999/screenshots/manplant1.jpg
|http://geyser.oni2.net/genesis/screenshots/manplant/ot2_manplantX.jpg
|}
Since there was a passage running through the middle of the building (see foyer, pic 3), the right of the inner flyway may have looked like pic 1 at that point.
 The corridor that runs under the flyway in pic 1 is rather wide and two floors tall. Where does it end?
 At the gallery where the alarm console is now (pic 4). With stairs leading to the ''upper half'' of that gallery.

{|
|+offices
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic37.htm http://geyser.oni2.net/genesis/screenshots/_oni_37.jpg]
|http://geyser.oni2.net/genesis/May_1999/screenshots/office2.jpg
|-
|http://geyser.oni2.net/genesis/May_1999/screenshots/office2bis.jpg
|http://geyser.oni2.net/genesis/May_1999/screenshots/office2ter.jpg
|-
|http://geyser.oni2.net/genesis/May_1999/screenshots/office1.jpg
|http://geyser.oni2.net/genesis/May_1999/screenshots/office1bis.jpg
|}
I think those were in the back of the building, on both floors, with doors and "windows" onto the "alarm console gallery" (also split in two floors).
 But, ''very'' early on... First 4 pics : lower floor, the empty dark wall on the first is where the stairs in pic 4 above are.
 Last pics : upper floor, to the left of pic 4 above. Note the stuff on the desk.

----

===Bio-Research Lab===
This one has kept the same basic layout, but there were a few changes

{|
|+General layout and view from the foyer
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic06.htm http://geyser.oni2.net/genesis/screenshots/_oni_06.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic36.htm http://geyser.oni2.net/genesis/screenshots/_oni_36.jpg]
|}
The interior is only done in one half of the lab, and it's the other one (the one on the right).
 Looks like the level was flipped horizontally at some point (and the surrounding buildings weren't there).
 In the second picture, there are buildings in the distance, but the level is still not final :
 pillars and foyer doors missing, extra ledges along the sides of the aisle...
 Wonder what she's shooting at...

{|
|+Foyer and SLD wing
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic50.htm http://geyser.oni2.net/genesis/screenshots/_oni_50.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic28.htm http://geyser.oni2.net/genesis/screenshots/_oni_28.jpg]
|-
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic27.htm http://geyser.oni2.net/genesis/screenshots/_oni_27.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic49.htm http://geyser.oni2.net/genesis/screenshots/_oni_49.jpg]
|}
The stairs in the foyer run the other way now. Like this \\ not like this //. So this is still the flipped version.
 There were ''stools'' for the scientists... Apart from that that wing is pretty much final.
 SLD-growing machines are more varied, though.

{|
|+Machines in the acid room
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic44.htm http://geyser.oni2.net/genesis/screenshots/_oni_44.jpg]
|http://geyser.oni2.net/genesis/screenshots/lab/_machine_new.jpg
|}
The final ones are much thinner, and the layout of the stairs and catwalks is different.

----

===Vansam Regional Airport===
{|
|+The airport's entrance
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic25.htm http://geyser.oni2.net/genesis/screenshots/_oni_25.jpg]
|}
This can be the "Arrivals" section (which is now completely empty).

----

===TCTF Regional Headquarters===
{|
|+Parking lot
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic39.htm http://geyser.oni2.net/genesis/screenshots/_oni_39.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic19.htm http://geyser.oni2.net/genesis/screenshots/_oni_19.jpg]
|}
A longer car. Different transition from the parking lot to the main building. A place for Konoko's bike.
Different stuff outside the parking's gates.

{|
|+Main entrance
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic40.htm http://geyser.oni2.net/genesis/screenshots/_oni_40.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic13.htm http://geyser.oni2.net/genesis/screenshots/_oni_13.jpg]
|}
The room is more than 2 times wider now. There are windows on the right and catwalks running across the far side.
The entrance door changed a lot, but the van didn't change much...

{|
|+The "atrium" rendered from an editor
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic24.htm http://geyser.oni2.net/genesis/screenshots/_oni_24.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic46.htm http://geyser.oni2.net/genesis/screenshots/_oni_46.jpg]
|}
Another pic [http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic16.htm here]. The elevator was ''between'' the two sets of ramps. Solid floors had a tiling pattern, and ramps were transparent.

{|
|+Same place, other version, ingame quality
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic03.htm http://geyser.oni2.net/genesis/screenshots/_oni_03.jpg]
|[http://geyser.oni2.net/genesis/screenshots/tctf/lg_thumb4.jpg http://geyser.oni2.net/genesis/screenshots/tctf/_lg_thumb4.jpg]
|}
The ramps had really nice railings (I wish they'd kept them), overall the room was much lighter (there's a light wall on the far side).
Same "V" structures at the ceiling as above : they're gone now. The layout of the rooms on either side is different, too.

{|
|+Damocles
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic15.htm http://geyser.oni2.net/genesis/screenshots/_oni_15.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic43.htm http://geyser.oni2.net/genesis/screenshots/_oni_43.jpg]
|}
The model didn't change at all, but now it's placed at the center (floor 2/3) of a really tall room rather than in that rather small one.
 As for the terminals, there are primitives with similar looks, around Damocles and elsewhere.

----

===Regional State Building===
{|
|+The foyer
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic01.htm http://geyser.oni2.net/genesis/screenshots/_oni_01.jpg]
|http://geyser.oni2.net/pics/screenshots/iron_demon/demon_fight.jpg
|}
Slightly different textures, smaller windows. It also looks like there used to be doors between the two parts of the building on the ground floor. The only connections now are on the top floor and in the basement.

----

===TCTF Science Prison===
{|
|+The scanner
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic17.htm http://geyser.oni2.net/genesis/screenshots/_oni_17.jpg]
|}
New wall textures. Looks like the scanner's textures are actually higher-res than what we have now.

----
===Syndicate Mountain Compound===
Old versus new :
{|
|+"This is the heart of the Sturmanderung Megacomputer"
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic14.htm http://geyser.oni2.net/genesis/screenshots/_oni_14.jpg]
|[http://geyser.oni2.net/genesis/screenshots/compound/compound_new1.jpg http://geyser.oni2.net/genesis/screenshots/compound/_compound_new1.jpg]
|-
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic45.htm http://geyser.oni2.net/genesis/screenshots/_oni_45.jpg]
|[http://geyser.oni2.net/genesis/screenshots/compound/compound_new2.jpg http://geyser.oni2.net/genesis/screenshots/compound/_compound_new2.jpg]
|-
|http://geyser.oni2.net/genesis/screenshots/compound/ot2_compound1.jpg
|[http://geyser.oni2.net/genesis/screenshots/compound/compound_new3.jpg http://geyser.oni2.net/genesis/screenshots/compound/_compound_new3.jpg]
|-
|http://geyser.oni2.net/genesis/screenshots/compound/ot2_compound2.jpg
|[http://geyser.oni2.net/genesis/screenshots/compound/compound_new4.jpg http://geyser.oni2.net/genesis/screenshots/compound/_compound_new4.jpg]
|}
The basic layout of the room is the same, but :
*it was much more crowded with "computers"
*there were catwalks (and rooms) missing
*the existing catwalks were aligned differently
*the lowest level is close to final on picture 4; on picture 2, it's clearly lacking a lot of connections

----

==Pre-beta levels==
Just for the hell of it, here are the possible names of those missing levels :
*05. The Airport Part Deux (deux is 2 in French)
*07. Obsolete
*16. BGI HQ
*30. The Arena of Pain
*31. Crossing Zone
*32. Pit
*33. Crossing Zone Too
*34. Capture
*35. Territories
*36. Test_Stuff
*55. AlexTestSite
*66. Experimental_II
*68. MARTY'S SOUND CORRIDOR
*71. FiringRange
*77. One Room
*88. One Room 2
*99. Test Barn II

The E3 1998 trailer takes place in a Syndicate Warehouse that has nothing to do with the final one.

Pictures (trailer snapshots) coming soon...

{|
|+The HQ of the anecdotical [[BGI]] corporation?
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic08.htm http://geyser.oni2.net/genesis/screenshots/_oni_08.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic07.htm http://geyser.oni2.net/genesis/screenshots/_oni_07.jpg]
|}
Note the oddly twisted catwalk in both pictures (dynamic deformation? heat distorsion?).
 Also note that this is not the same side of a same room : probably both sides of that room.

{|
|+A deathmatch arena
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic23.htm http://geyser.oni2.net/genesis/screenshots/_oni_23.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic31.htm http://geyser.oni2.net/genesis/screenshots/_oni_31.jpg]
|-
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic32.htm http://geyser.oni2.net/genesis/screenshots/_oni_32.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic35.htm http://geyser.oni2.net/genesis/screenshots/_oni_35.jpg]
|-
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic41.htm http://geyser.oni2.net/genesis/screenshots/_oni_41.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic09.htm http://geyser.oni2.net/genesis/screenshots/_oni_09.jpg]
|-
|http://geyser.oni2.net/genesis/screenshots/arena/ot2_arena2.jpg
|http://geyser.oni2.net/genesis/screenshots/arena/ot2_arena3.jpg
|}
Although the last 3 shots look different, it's the same layout.
 Either "The Arena of Pain" at two stages of development, or "One Room" and "One Room 2".

{|
|+A giant playground
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic33.htm http://geyser.oni2.net/genesis/screenshots/_oni_33.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic34.htm http://geyser.oni2.net/genesis/screenshots/_oni_34.jpg]
|-
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic04.htm http://geyser.oni2.net/genesis/screenshots/_oni_04.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic10.htm http://geyser.oni2.net/genesis/screenshots/_oni_10.jpg]
|-
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross1.jpg
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross1bis.jpg
|-
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross2.jpg
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross2bis.jpg
|-
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross3.jpg
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross3bis.jpg
|-
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross3ter.jpg
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross5.jpg
|-
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross4.jpg
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross4bis.jpg
|-
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross4ter.jpg
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross4quater.jpg
|-
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross10.jpg
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross10bis.jpg
|-
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross6.jpg
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross6bis.jpg
|-
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross7.jpg
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross7bis.jpg
|-
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross7ter.jpg
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross7quater.jpg
|-
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross8.jpg
|http://geyser.oni2.net/genesis/May_1999/screenshots/cross9.jpg
|}
Judging from the architecture (lots of massive crosses covering a few floors), I think it's Crossing Zone and Crossing Zone Too.

{|
|+Completely random
|http://geyser.oni2.net/genesis/May_1999/screenshots/enigma1.jpg
|http://geyser.oni2.net/genesis/May_1999/screenshots/enigma1bis.jpg
|-
|colspan=2|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic11.htm http://geyser.oni2.net/genesis/screenshots/_oni_11.jpg]
|}
The first ones beat me. Isn't the second one a Marathon level?

Aren't the first ones Atmostpheric Conversion Center Interior? <Your_Mom>

{|
|+Even more random
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic20.htm http://geyser.oni2.net/genesis/screenshots/_oni_20.jpg]
|[http://www6.fh-eberswalde.de/user/dkriesch/onistuff/subfold/oldpics/pic05.htm http://geyser.oni2.net/genesis/screenshots/_oni_05.jpg]
|}
The first one doesn't look like anything in the final game. The last one, well, it could be anything.
 Judjing by the floor texture, probably Crossing Zone too.

AE:BIP

2005-12-15T03:27:24Z

Your Mom: /* Downloading */

== The Binary Improvement Project ==

The main objective of the Binary Improvement Project (BIP) will be to make extremely script-er friendly versions of all the *.dat and *.raw files. We will fix up mistakes left by the original coders, add a "hurt" and a "death" trigger for each character, and improve the binaries altogether. Making it much easier to script for beginners and experts alike.

If you have a Hex Editor, an iron will, and want to help out, feel free to contribute your edited *.dat and *.raw files!

To read up on discussion on this topic, go [http://mukade.bungie.org/cgi-bin/mukade/ikonboard.cgi?s=6516029ae2bf986cdebc05c192858e22;act=ST;f=3;t=205 here]

==Project Points==
*Improved AI (Using Alternate AI Mele logic/improving mele logic)
*Easier to Script (AI names/functions)
*Wider Range of Character Classes (More random skins, harder enemy types, more enemy types where available)
*AI endowed Konoko for all levels (Players will now use "ai_0" as their player character)
*Trigger Events (hurt, death, dying, reload, ect)
*Better Ai Names (yes, no more annoying names. Will all be sorted likewise : AI_000_Konoko, AI_001_Thug, ect)
*More Coming (Yes, more!)

== Downloading ==

WARNING: HUGE FILES

The ones currently available are the first generation.
They only contain functions for death and hurt. (And some other things which you must find out on your own :p)

{| border="1" cellpadding="5" cellspacing="0" align="center"
|+'''THE BINARY IMPROVEMENT PROJECT'''
|-
!Level
!Download File
|-
|level0_Final
|Available *
|-
|level1_Final
|Available
|-
|level2_Final
|Coming Soon
|-
|level3_Final
|Coming Soon
|-
|level4_Final
|Coming Soon
|-
|level6_Final
|Coming Soon
|-
|level8_Final
|Coming Soon
|-
|level9_Final
|Coming Soon
|-
|level10_Final
|Coming Soon
|-
|level11_Final
|Coming Soon
|-
|level12_Final
|Coming Soon
|-
|level13_Final
|Coming Soon
|-
|level14_Final
|Coming Soon
|-
|level18_Final
|Coming Soon
|-
|level19_Final
|Available
|}

*technically, level0_Final is not part of the project. Level0_final improves the overall game rather than a specific level, but it is awesome nonetheless. It allows AI to dash when unarmed and has improved particles.

'''Sorry, but the BIP's download section has been taken down temporarily for legal reasons.'''

AE:BIP

2005-12-10T17:59:53Z

Your Mom: /* Downloading */

== The Binary Improvement Project ==

The main objective of the Binary Improvement Project (BIP) will be to make extremely script-er friendly versions of all the *.dat and *.raw files. We will fix up mistakes left by the original coders, add a "hurt" and a "death" trigger for each character, and improve the binaries altogether. Making it much easier to script for beginners and experts alike.

If you have a Hex Editor, an iron will, and want to help out, feel free to contribute your edited *.dat and *.raw files!

To read up on discussion on this topic, go [http://mukade.bungie.org/cgi-bin/mukade/ikonboard.cgi?s=6516029ae2bf986cdebc05c192858e22;act=ST;f=3;t=205 here]

==Project Points==
*Improved AI (Using Alternate AI Mele logic/improving mele logic)
*Easier to Script (AI names/functions)
*Wider Range of Character Classes (More random skins, harder enemy types, more enemy types where available)
*AI endowed Konoko for all levels (Players will now use "ai_0" as their player character)
*Trigger Events (hurt, death, dying, reload, ect)
*Better Ai Names (yes, no more annoying names. Will all be sorted likewise : AI_000_Konoko, AI_001_Thug, ect)
*More Coming (Yes, more!)

== Downloading ==

WARNING: HUGE FILES

The ones currently available are the forst generation.
They only contain funtions for death and hurt. (And some other things which you must find out on your own :p)

{| border="1" cellpadding="5" cellspacing="0" align="center"
|+'''THE BINARY IMPROVEMENT PROJECT'''
|-
!Level
!Download File
|-
|level0_Final
|[http://loser.oni2.net/Geyser_Level0.rar Available Here!]*
|-
|level1_Final
|[http://loser.oni2.net/Geyser_Level1.rar Available Here!]
|-
|level2_Final
|Coming Soon
|-
|level3_Final
|Coming Soon
|-
|level4_Final
|Coming Soon
|-
|level6_Final
|Coming Soon
|-
|level8_Final
|Coming Soon
|-
|level9_Final
|Coming Soon
|-
|level10_Final
|Coming Soon
|-
|level11_Final
|Coming Soon
|-
|level12_Final
|Coming Soon
|-
|level13_Final
|Coming Soon
|-
|level14_Final
|Coming Soon
|-
|level18_Final
|Coming Soon
|-
|level19_Final
|[http://www.your_mom.oni2.net/Downloads/CompoundB.rar Available Here!]
|}

*technically, level0_Final is not part of the project. Level0_final improves the overall game rather than a specific level, but it is awesome nonetheless. It allows AI to dash when unarmed and has improved particles.

AE:BIP

2005-12-10T17:58:26Z

Your Mom: /* Project Points */

== The Binary Improvement Project ==

The main objective of the Binary Improvement Project (BIP) will be to make extremely script-er friendly versions of all the *.dat and *.raw files. We will fix up mistakes left by the original coders, add a "hurt" and a "death" trigger for each character, and improve the binaries altogether. Making it much easier to script for beginners and experts alike.

If you have a Hex Editor, an iron will, and want to help out, feel free to contribute your edited *.dat and *.raw files!

To read up on discussion on this topic, go [http://mukade.bungie.org/cgi-bin/mukade/ikonboard.cgi?s=6516029ae2bf986cdebc05c192858e22;act=ST;f=3;t=205 here]

==Project Points==
*Improved AI (Using Alternate AI Mele logic/improving mele logic)
*Easier to Script (AI names/functions)
*Wider Range of Character Classes (More random skins, harder enemy types, more enemy types where available)
*AI endowed Konoko for all levels (Players will now use "ai_0" as their player character)
*Trigger Events (hurt, death, dying, reload, ect)
*Better Ai Names (yes, no more annoying names. Will all be sorted likewise : AI_000_Konoko, AI_001_Thug, ect)
*More Coming (Yes, more!)

== Downloading ==

WARNING: HUGE FILES

{| border="1" cellpadding="5" cellspacing="0" align="center"
|+'''THE BINARY IMPROVEMENT PROJECT'''
|-
!Level
!Download File
|-
|level0_Final
|[http://loser.oni2.net/Geyser_Level0.rar Available Here!]*
|-
|level1_Final
|[http://loser.oni2.net/Geyser_Level1.rar Available Here!]
|-
|level2_Final
|Coming Soon
|-
|level3_Final
|Coming Soon
|-
|level4_Final
|Coming Soon
|-
|level6_Final
|Coming Soon
|-
|level8_Final
|Coming Soon
|-
|level9_Final
|Coming Soon
|-
|level10_Final
|Coming Soon
|-
|level11_Final
|Coming Soon
|-
|level12_Final
|Coming Soon
|-
|level13_Final
|Coming Soon
|-
|level14_Final
|Coming Soon
|-
|level18_Final
|Coming Soon
|-
|level19_Final
|[http://www.your_mom.oni2.net/Downloads/CompoundB.rar Available Here!]
|}

*technically, level0_Final is not part of the project. Level0_final improves the overall game rather than a specific level, but it is awesome nonetheless. It allows AI to dash when unarmed and has improved particles.

AE:BIP

2005-12-08T01:58:06Z

Your Mom:

AE:BIP

2005-12-08T01:55:18Z

Your Mom: /* Downloading */

AE:BIP

2005-12-08T01:54:43Z

Your Mom: /* Downloading */

AE:BIP

2005-12-04T23:13:57Z

Your Mom: /* The Binary Improvement Project */

AE:BIP

2005-12-04T23:11:54Z

Your Mom: /* The Binary Improvement Project */

== The Binary Improvement Project ==

The main objective of the Binary Improvement Project (BIP) will be to make extremely scripter friendly versions of all the *.dat and *.raw files. We will fix up mistakes left by the original coders, add a "hurt" and a "death" trigger for each character, and improve the binaries altogether. Making it much easier to script for beginners and experts alike.

If you have a Hex Editor, an Iron will, and want to help out, feel free to contribute your edited *.dat and *.raw files!

To read up on disscussion on this topic, go [http://mukade.bungie.org/cgi-bin/mukade/ikonboard.cgi?s=6516029ae2bf986cdebc05c192858e22;act=ST;f=3;t=205 here]

{| border="1" cellpadding="5" cellspacing="0" align="center"
|+'''THE BINARY IMPROVEMENT PROJECT'''
|-
!Level
!Download File
|-
|level0_final
|[http://loser.oni2.net/Geyser_Level0.rar Level 0]*
|-
|level1_final
|[http://loser.oni2.net/Geyser_Level1.rar Level 1]
|-
|level2_final
|Coming Soon
|-
|level3_final
|Coming Soon
|-
|level4_final
|Coming Soon
|-
|level6_final
|Coming Soon
|-
|level8_final
|Coming Soon
|-
|level9_final
|Coming Soon
|-
|level10_final
|Coming Soon
|-
|level11_final
|Coming Soon
|-
|level12_final
|Coming Soon
|-
|level13_final
|Coming Soon
|-
|level14_final
|Coming Soon
|-
|level18_final
|Coming Soon
|-
|level19_final
|[http://www.your_mom.oni2.net/Downloads/CompoundB.rar Level 14]
|}

AE:BIP

2005-12-04T23:06:08Z

Your Mom:

OBD:Oni Binary Data

2005-12-04T22:59:33Z

Your Mom:

Muuuuch more stuff will come here soon.

[[OBD:OUP|OniUnPacker (OUP)]]

[http://www.fh-eberswalde.de/user/dkriesch/onistuff/oni.htm SSGs Oni-Site] (Good starting point for information about Oni's data-files)

[[OBD:BIP|The Binary Improvement Project]]

AE talk:OTA

2005-12-03T20:35:05Z

Your Mom: /* CRASH REPORTS */

AE talk:OTA

2005-12-03T20:29:52Z

Your Mom: /* CRASH REPORTS */

Oni (folder)/GameDataFolder/IGMD/global

2005-12-03T20:28:12Z

Your Mom: /* Why call it <tt>pre</tt>? */

==Oni global script folder==
"global" is a "secret subfolder" of [[OSL:IGMD|IGMD]] : a regular installation of Oni doesn't have it at all.

But you can create it and use it and it's actually very rewarding. It's a very special folder.

==What's so special about it?==
The global folder is visible from every one of Oni's levels. Rather, the scripts (files with extension BSL) in the global folder are always processed at the same time as the level logic of a particular level, when that particular level is loaded.

==How do I use it?==
Is there really a short way to describe it? Oh well...
-----------
Let's say you want Oni to do the exact same thing every time you load a save point. Like, you've just learned about how the [[OSL:Oni Scripting Language/functions/built-in/dmsg|<tt>dmsg</tt>]] command works, and you want the message "Thank you for playing Oni!" to be displayed after a level loads. Then the trivial solution is to go in every level's folder, open the file where <tt>func void main(void)</tt> is declared and modify it as follows :
func void main(void) {
dmsg "Thank you for playing Oni!"
# REST OF THE MAIN FUNCTION'S BODY, UNCHANGED
}
OK. You've done that for all 14 levels. But now, let's say you've learned about how to add colors to debug messages, and you want the whole message to be red, except for the word Oni which shall be blue.

What then? Load the whole level again and replace "Thank you for playing Oni!" with "[r.Thank you for playing ][b.Oni][r.!]"? 14 times?

No. You use the global folder

==<tt>func pre</tt>==
Go to the global folder and create a file called <tt>pre.bsl</tt>. Open it and give it the following content :
func pre {
dmsg "[r.Thank you for playing ][b.Oni][r.!]"
}
Then go and open the 14 files where you had <tt>dmsg "Thank you for playing Oni!"</tt>, and replace that line with <tt>pre</tt>, getting :
func void main(void) {
pre
# REST OF THE MAIN FUNCTION'S BODY, UNCHANGED
}
This is an inline call to the <tt>pre</tt> function we have just set up in the global folder. The function <tt>pre</tt> is "globally recognized".

===Why call it <tt>pre</tt>?===
Because everything in <tt>func main</tt> is level-specific settings and/or logic, so if you want something to happen exactly the same way every time you load a level, the only place to add that something is at the very start of <tt>func main</tt>, that is, ''before'' all the level-specific content. Which is why it's called "pre".

Should still work if you name it anything else though. <tt>pre</tt> just makes the most sense.

===Why make it inline? (WARNING : EXPERT STUFF)===
Because in that case, it's as if the content of <tt>func pre</tt> got pasted at the start of <tt>func main</tt> which is perfectly OK for some purposes (like the <tt>dmsg "[r.Thank you for playing ][b.Oni][r.!]"</tt> call in the example above). Three things to consider :
#You can always <tt>fork</tt> what you want to be <tt>fork</tt>ed inside <tt>func pre</tt>. And it will be exactly the same as if you placed the <tt>fork</tt>ed call directly inside <tt>func main</tt>.
#If you put <tt>fork pre</tt> instead of <tt>pre</tt> in <tt>func main</tt>, you can no longer consider that you're "just adding stuff to the beginning of <tt>func main</tt>". You can make an inline call into a forked call, but not the other way round.
#In some cases, you may want to be sure some part of <tt>func pre</tt> is executed ''rigorously before'' <tt>func main</tt>. And that's something you can not guarantee with a <tt>fork</tt>ed call.
Sure you can't put anything you want in an inline-called <tt>func pre</tt>, like a <tt>sleep</tt> statement, or a call to <tt>chr_wait_animtype</tt>.
It's up to you to bear in mind that what you're looking at is in fact just a part of every level's <tt>func main</tt>.

Oni (folder)/GameDataFolder/IGMD/global

2005-12-03T20:27:59Z

Your Mom: /* Why call it <tt>pre</tt>? */

==Oni global script folder==
"global" is a "secret subfolder" of [[OSL:IGMD|IGMD]] : a regular installation of Oni doesn't have it at all.

But you can create it and use it and it's actually very rewarding. It's a very special folder.

==What's so special about it?==
The global folder is visible from every one of Oni's levels. Rather, the scripts (files with extension BSL) in the global folder are always processed at the same time as the level logic of a particular level, when that particular level is loaded.

==How do I use it?==
Is there really a short way to describe it? Oh well...
-----------
Let's say you want Oni to do the exact same thing every time you load a save point. Like, you've just learned about how the [[OSL:Oni Scripting Language/functions/built-in/dmsg|<tt>dmsg</tt>]] command works, and you want the message "Thank you for playing Oni!" to be displayed after a level loads. Then the trivial solution is to go in every level's folder, open the file where <tt>func void main(void)</tt> is declared and modify it as follows :
func void main(void) {
dmsg "Thank you for playing Oni!"
# REST OF THE MAIN FUNCTION'S BODY, UNCHANGED
}
OK. You've done that for all 14 levels. But now, let's say you've learned about how to add colors to debug messages, and you want the whole message to be red, except for the word Oni which shall be blue.

What then? Load the whole level again and replace "Thank you for playing Oni!" with "[r.Thank you for playing ][b.Oni][r.!]"? 14 times?

No. You use the global folder

==<tt>func pre</tt>==
Go to the global folder and create a file called <tt>pre.bsl</tt>. Open it and give it the following content :
func pre {
dmsg "[r.Thank you for playing ][b.Oni][r.!]"
}
Then go and open the 14 files where you had <tt>dmsg "Thank you for playing Oni!"</tt>, and replace that line with <tt>pre</tt>, getting :
func void main(void) {
pre
# REST OF THE MAIN FUNCTION'S BODY, UNCHANGED
}
This is an inline call to the <tt>pre</tt> function we have just set up in the global folder. The function <tt>pre</tt> is "globally recognized".

===Why call it <tt>pre</tt>?===
Because everything in <tt>func main</tt> is level-specific settings and/or logic, so if you want something to happen exactly the same way every time you load a level, the only place to add that something is at the very start of <tt>func main</tt>, that is, ''before'' all the level-specific content. Which is why it's called "pre".

Should still work if you name it anything else though. <tt>pre</tt> just makes athe most sense.

===Why make it inline? (WARNING : EXPERT STUFF)===
Because in that case, it's as if the content of <tt>func pre</tt> got pasted at the start of <tt>func main</tt> which is perfectly OK for some purposes (like the <tt>dmsg "[r.Thank you for playing ][b.Oni][r.!]"</tt> call in the example above). Three things to consider :
#You can always <tt>fork</tt> what you want to be <tt>fork</tt>ed inside <tt>func pre</tt>. And it will be exactly the same as if you placed the <tt>fork</tt>ed call directly inside <tt>func main</tt>.
#If you put <tt>fork pre</tt> instead of <tt>pre</tt> in <tt>func main</tt>, you can no longer consider that you're "just adding stuff to the beginning of <tt>func main</tt>". You can make an inline call into a forked call, but not the other way round.
#In some cases, you may want to be sure some part of <tt>func pre</tt> is executed ''rigorously before'' <tt>func main</tt>. And that's something you can not guarantee with a <tt>fork</tt>ed call.
Sure you can't put anything you want in an inline-called <tt>func pre</tt>, like a <tt>sleep</tt> statement, or a call to <tt>chr_wait_animtype</tt>.
It's up to you to bear in mind that what you're looking at is in fact just a part of every level's <tt>func main</tt>.

BSL:Tutorial/Scratch

2005-11-20T19:04:49Z

Your Mom: /* Part 9: Variables and Save Points */

This page is a short tutorial on how to get started on simple scripts for those who have had no experience with scripting before.
It will teach you, step by step, how to write a simple script. By the end of this tutorial, you will be able to move on to more advanced scripts.

----

== Part 1 : Knowing your formats ==

The game will accept 2 types of syntax for scripts, and they are based on different styles of writing. Choose the one that suits you best.

The types are :

Shell-Style:
This is compiled much like some System-Shells. It is written in a "one-function-call-a-line" format, and is the easiest to begin with if you have had no coding experience, as the code is neatly displayed line after line. The downside of this it, that once you get into more complex scripts or scripts with many function calls, the file becomes very hard to read and very large. Also, an great tool, passing information through a command, cannot be done using Shell-Style.

Example: [[Shell-Style]]

C-Style:
This is compiled much like the popular coding style C. The syntax can be placed into multiple-function lines and functions are divided by a ''';''' . In advanced scripts, this style will allow you to condense your script and the parts will be easier to read/debug. It also allows you to utilize some of the more advanced features easily. The problem with this is, that starting off, it is harder to write if you have had no previous experience with coding.

Example: [[C-Style]]

Hybrid Style:
This is a combination between C-Style and Shell-Stlye. It keeps the easy-to-read format of Shell-Style, yet allows you to use the more advanced techniques of C-Style.

For the purpose of this article, we will use Shell-Style syntax for simplicity.

----

== Part 2: Starting Off ==

Now, I suggest reading the original script files to get a basic idea for how scripts are laid out. This will allow us to jump-start a bit.

Open up your IMGD and look for the following folder: EnvWarehouse.
Open it up, and we'll take a look at how it it laid out. There should be several files in here. Open using NOTEPAD, the one titled '''warehouse_main.bsl'''. It should look like this:

<tt>
func void main(void) 
{ 
env_show 2010 0 
gl_fog_blue=.15 
gl_fog_red=.15 
gl_fog_green=.15 
gl_fog_start=.99 
gs_farclipplane_set 5000 
obj_create 20 20 
level_start 
 
}</tt>

This is an example of a '''main''' file. It contains the information of how the level starts.

Ignore the contents of the script for now, and notice that the contents of the function <tt>main</tt> are enclosed by a set of brackets ('''{''' and '''}''').

All functions must be enclosed in this set of brackets or it will not be executed.

Close the file, and rename the folder "EnvWarehouse" "EnvWarehouse_original". Then, create a folder called "EnvWarehouse" and create a script file inside and name it "Tutorial". We will be using this file to show various examples of scripts and finally, write a small script of your own.

----

== Part 3: Basic Commands ==

This is just a small section explaining the commands that will be used in this tutorial. For a complete list of commands, see [http://www.fh-eberswalde.de/user/dkriesch/onistuff/commands.htm Ssg's Site] for more information.

ai2_spawn (name) - creates and starts an AI from a character object 
chr_teleport (name) (flag) - teleports a character to a flag 
chr_givepowerup (name) (powerup) (amount) - gives a character a powerup 
.
.
.

----

== Part 4: First Script ==

This section will teach you how to write a very basic script (fighting script). It will start you off in the Final Training Room, where you practiced firing weapons in the original game. With this script, the room will appear very empty.

Let's open up the "Tutorial.bsl" file and start writing the script.

First, declare it the "main" portion of the script by typing "<tt>func void main(void)</tt> at the very beginning of the file. This tells the game which function it is. The "main" function is the function that the game looks at first to determine what is to be executed.

Below that line, type '''{'''. This tells the game that the function has started.

Add a space, and then type <tt>chr_teleport 0 7010</tt>. This function teleports Konoko (her id is always 0) to the flag 7010. It is located in the final training room.

Finish the function "main" by typing '''}''' on the next line.

It should look like this:

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
}</tt>

Save the file, load up Oni, and click "New Game". You should be standing in the center of the final combat training room.

You are now on your way!

----

== Part 5: Adding NPCs (AI) ==

Before we begin, notice that there are two types of AI. AI created from character objects, and AI created from memory. AI created from character objects are created by the function call <tt>ai2_spawn (name)</tt>, where (name) is the name of the AI. AI created from memory are created by the function call <tt>chr_create (ai_number) start,</tt>. These AI do not have combat logic, and thus will not attack you physically but can still use weapons.

Now, we are going to add 2 enemy AI to our script that we wrote in the last section. Open it up, and lets add some enemies for Konoko to fight.

To recap, it should look like this :

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
}</tt>

After the function call <tt>chr_teleport 0 7010</tt>, add the following 2 commands on separate lines: <tt>ai2_spawn Top_Striker</tt> and <tt>ai2_spawn Top_Comguy</tt>. These two commands tell the game to create 2 characters: Top_Striker, and Top_Comguy.

Since that these characters do not spawn in the room, they must be teleported there. Using the <tt>chr_teleport</tt> command used earlier to teleport yourself, modify it to teleport the 2 AI using their names instead of "0". Teleport them to the flags "7008" and "7009" respectively. Refer to the example above or the list of function calls above to write this in.

It should now look like this :

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
ai2_spawn Top_Striker 
ai2_spawn Top_Comguy 
chr_teleport Top_Striker 7008 
chr_teleport Top_Comguy 7009 
}</tt>

This script will now teleport you into the final training room and face you off against 2 Strikers.

This fight too easy? In the next section, we will learn how to spice up the fight, and let you develop your own script.

----

== Part 6: Customization==

Here, you will be able to split off and customize your script.
Each subsection will represent a way to customize the above script.

===Weapons and Powerups===
These are the easiest things to add into a battle.

Weapons can be spawned on the ground or given to characters.

====Giving Characters Weapons====

Giving characters weapons is very easy. Simply use the command <tt>chr_giveweapon</tt> to give a character a weapon.

[[OSL:Inventory|Here]] are the list of the weapon codes. For the purpose of this example, we will use <tt>w3_phr</tt>, the plasma rifle. This command will give the two strikers plasma rifles.

Add the commands <tt>chr_giveweapon Top_Striker w3_phr</tt> and <tt>chr_giveweapon Top_Comguy w3_phr</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute.

====Spawning Weapons on the ground====

Spawning weapons is simple. Use the command <tt>weapon_spawn</tt> to spawn a weapon.

Add the commands <tt>weapon_spawn w3_phr 7008</tt> and <tt>weapon_spawn w3_phr 7009</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will spawn 2 plasma rifles, one under each striker's feet. AI will automatically pick up weapons with ammo or empty weapons they have ammo for.

====Giving Characters Powerups====

Giving characters powerups is much like giving characters weapons. Use the command <tt>chr_givepowerup</tt> to give a character a powerup.

The powerups you can give a character are :
* shield : Gives a force shield
* invis : Gives a phase cloak
* ammo : Gives a ballistic ammo
* cell : Gives an energy cell.

For the purpose of this example, we will give the characters invisibilities.

Add the commands <tt>chr_givepowerup Top_Striker invis -1</tt> and <tt>chr_givepowerup Top_Comguy invis -1</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will make the strikers permanently invisible. To make then visible after 30 seconds, erase "-1".

====Spawning Powerups on the Ground====

Spawning powerups are simple. Use the command <tt>powerup_spawn</tt> to spawn a powerup.

Add the commands <tt>powerup_spawn invis 7008</tt> and <tt>powerup_spawn invis 7009</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will spawn 2 phase cloaks beneath the striker's feet. Since AI will not pick up powerups, this is for you only.

===Extra Characters===

Addubg extra characters to the script is easy. Just follow the steps for adding the first AI and follow the procedure, look for AI names [[OSL: AI names|Here]].

====Adding Enemies====

Look at the chart for what teams the AI are on. Most of the time, adding enemies simply involve spawning and teleporting the AI. As long as the team in "Syndicate", it will be an enemy. If you want to add an emeny from an allied team, use the <tt>chr_changeteam</tt> command to changet their team to "Syndicate" like this:

<tt>chr_changeteam griffin Syndicate</tt>

====Adding Allies====

Look at the chart for what teams the AI are on. As long as the team is "TCTF" or "Konoko", it will be an ally for you in this script. If you want to add an ally from the enemy team, use the <tt>chr_changeteam</tt> command to changet their team to "TCTF" or "Konoko" like this:

<tt>chr_changeteam WH_Striker_D TCTF</tt>

===Overpower===

Use the <tt>chr_set_health</tt> command to set a character's health. Note that each character has a base health that may not be the same. For example, konoko's base health is 200, while a brown striker's is only 50. Keep this in mind when setting character's health. Setting it over their base health will send them into overpower - like using a hypo at full health. The health will drain at 1 every second even for AI. This example sets konoko's health to 400 - overpower.

<tt>chr_set_health 0 400</tt>

This following example shows everything listed above added.

<tt>func void main(void) 
{ 
 
chr_teleport 0 7010 
powerup_spawn hypo 7010 
 
ai2_spawn Top_Striker 
ai2_spawn Top_Comguy 
 
chr_teleport Top_Striker 7008 
chr_teleport Top_Comguy 7009 
 
chr_givepowerup Top_Striker invis -1 
chr_givepowerup Top_Comguy invis -1 
powerup_spawn invis 7007 
powerup_spawn invis 7009 
 
chr_giveweapon Top_Striker w7_scc 
chr_giveweapon Top_Comguy w3_phr 
chr_givepowerup Top_Striker ammo 15 
chr_givepowerup Top_Comguy cell 30 
 
weapon_spawn w2_sap 7045 
powerup_spawn ammo 7008 
 
ai2_spawn OutroTCTF01 
chr_teleport OutroTCTF01 7007 
 
ai2_spawn WH_Thug_A 
chr_changeteam WH_Thug_A TCTF 
chr_teleport WH_Thug_A 7007 
 
ai2_spawn griffin 
chr_changeteam griffin Syndicate 
chr_teleport griffin 7008 
chr_set_health griffin 3900 
}</tt>

----

== Part 7: Delay ==

<tt>sleep</tt> 
<tt>chr_wait_health</tt>

To wait for some time before executing a command, use <tt>sleep</tt>. To wait for approx 5 seconds before spawning an extra drone, go like this:

<tt>sleep 300 
ai2_spawn dum_train_block 
chr_teleport dum_train_block 7010 
</tt>

To wait for a striker to die and then spawn some drones, go like this:

<tt>chr_wait_health Top_Striker 0 
ai2_spawn dum_train_block 
chr_teleport dum_train_block 7010 </tt>

== Part 8: Forking and Separate Functions==

This is the part where we start moving commands out of "main". Create a new function called "logic" like this : type "func logic" two lines below the '''}''' of "main". Type '''{''' nad copy out everything inside "main" into "logic". Type <tt>fork logic</tt> in main. It should look like this :

<tt>func void main(void) 
{ 
fork logic 
} 
 
func logic 
{ 
... 
}</tt>

... being whatever you had in "main" before. Add <tt>chr_wait_health griffin 0</tt> at the end of "logic", then type <tt>fork logic2</tt>. Create the function "logic2". In "logic2" you can write whatever you want that you have learned before. For the prupose of this example, '''...''' will represent whatever you had, '''..''' will represent whatever you want, and typed text will represent thing that must be included.

<tt>func void main(void) 
{ 
fork logic 
} 
 
func logic 
{ 
... 
chr_wait_health griffin 0 
fork logic2 
} 
 
func logic2 { 
.. 
}</tt>

===Extra: Multiple Forking===

More than one function can be forked in the same function. Look at ths example :

<tt>func void main(void) 
{ 
fork logicA 
fork logicB 
} 

func logicA { 
.. 
} 

func logicB { 
.. }</tt>

Both "logicA" and "logicB" are executed at the same time. If <tt>chr_wait_health griffin 0</tt> were to be removed, likewise, both "logic" and "logic2" are executed at the same time.

== Part 9: Variables and Save Points ==

Every wondered why there is no folder for basic training? The truth is, it is actually part of the Warehouse level and is managed by save points.

This is the beginning of the "level_start" which is forked from "main" in the original level scripts.

<tt>func void level_start(string ai_name) 
{ 
 
 
if (save_point eq 0) 
{ 
... 
} 
 
if (save_point eq 1) 
{ 
... 
} 
 
}</tt>

Using forking, you can link save points to functions. Like so :

<tt>func void main(void) 
{ 
 
if (save_point eq 0) 
{ 
fork logic 
} 
 
if (save_point eq 1) 
{ 
fork logic2 
} 
 
}</tt>

When save point 0 is loaded (TCTF Training), the function "logic" is executed. If save point 1 is loaded (Syndicate Warehouse), "logic2" is executed. Note that in Warehouse, the save point number in the script is one higher than in the level load list, because "TCTF Training" is SP0.

- Your_Mom

BSL:Tutorial/Scratch

2005-11-20T18:27:39Z

Your Mom: /* Part 1 : Knowing your formats */

This page is a short tutorial on how to get started on simple scripts for those who have had no experience with scripting before.
It will teach you, step by step, how to write a simple script. By the end of this tutorial, you will be able to move on to more advanced scripts.

----

== Part 1 : Knowing your formats ==

The game will accept 2 types of syntax for scripts, and they are based on different styles of writing. Choose the one that suits you best.

The types are :

Shell-Style:
This is compiled much like some System-Shells. It is written in a "one-function-call-a-line" format, and is the easiest to begin with if you have had no coding experience, as the code is neatly displayed line after line. The downside of this it, that once you get into more complex scripts or scripts with many function calls, the file becomes very hard to read and very large. Also, an great tool, passing information through a command, cannot be done using Shell-Style.

Example: [[Shell-Style]]

C-Style:
This is compiled much like the popular coding style C. The syntax can be placed into multiple-function lines and functions are divided by a ''';''' . In advanced scripts, this style will allow you to condense your script and the parts will be easier to read/debug. It also allows you to utilize some of the more advanced features easily. The problem with this is, that starting off, it is harder to write if you have had no previous experience with coding.

Example: [[C-Style]]

Hybrid Style:
This is a combination between C-Style and Shell-Stlye. It keeps the easy-to-read format of Shell-Style, yet allows you to use the more advanced techniques of C-Style.

For the purpose of this article, we will use Shell-Style syntax for simplicity.

----

== Part 2: Starting Off ==

Now, I suggest reading the original script files to get a basic idea for how scripts are laid out. This will allow us to jump-start a bit.

Open up your IMGD and look for the following folder: EnvWarehouse.
Open it up, and we'll take a look at how it it laid out. There should be several files in here. Open using NOTEPAD, the one titled '''warehouse_main.bsl'''. It should look like this:

<tt>
func void main(void) 
{ 
env_show 2010 0 
gl_fog_blue=.15 
gl_fog_red=.15 
gl_fog_green=.15 
gl_fog_start=.99 
gs_farclipplane_set 5000 
obj_create 20 20 
level_start 
 
}</tt>

This is an example of a '''main''' file. It contains the information of how the level starts.

Ignore the contents of the script for now, and notice that the contents of the function <tt>main</tt> are enclosed by a set of brackets ('''{''' and '''}''').

All functions must be enclosed in this set of brackets or it will not be executed.

Close the file, and rename the folder "EnvWarehouse" "EnvWarehouse_original". Then, create a folder called "EnvWarehouse" and create a script file inside and name it "Tutorial". We will be using this file to show various examples of scripts and finally, write a small script of your own.

----

== Part 3: Basic Commands ==

This is just a small section explaining the commands that will be used in this tutorial. For a complete list of commands, see [http://www.fh-eberswalde.de/user/dkriesch/onistuff/commands.htm Ssg's Site] for more information.

ai2_spawn (name) - creates and starts an AI from a character object 
chr_teleport (name) (flag) - teleports a character to a flag 
chr_givepowerup (name) (powerup) (amount) - gives a character a powerup 
.
.
.

----

== Part 4: First Script ==

This section will teach you how to write a very basic script (fighting script). It will start you off in the Final Training Room, where you practiced firing weapons in the original game. With this script, the room will appear very empty.

Let's open up the "Tutorial.bsl" file and start writing the script.

First, declare it the "main" portion of the script by typing "<tt>func void main(void)</tt> at the very beginning of the file. This tells the game which function it is. The "main" function is the function that the game looks at first to determine what is to be executed.

Below that line, type '''{'''. This tells the game that the function has started.

Add a space, and then type <tt>chr_teleport 0 7010</tt>. This function teleports Konoko (her id is always 0) to the flag 7010. It is located in the final training room.

Finish the function "main" by typing '''}''' on the next line.

It should look like this:

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
}</tt>

Save the file, load up Oni, and click "New Game". You should be standing in the center of the final combat training room.

You are now on your way!

----

== Part 5: Adding NPCs (AI) ==

Before we begin, notice that there are two types of AI. AI created from character objects, and AI created from memory. AI created from character objects are created by the function call <tt>ai2_spawn (name)</tt>, where (name) is the name of the AI. AI created from memory are created by the function call <tt>chr_create (ai_number) start,</tt>. These AI do not have combat logic, and thus will not attack you physically but can still use weapons.

Now, we are going to add 2 enemy AI to our script that we wrote in the last section. Open it up, and lets add some enemies for Konoko to fight.

To recap, it should look like this :

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
}</tt>

After the function call <tt>chr_teleport 0 7010</tt>, add the following 2 commands on separate lines: <tt>ai2_spawn Top_Striker</tt> and <tt>ai2_spawn Top_Comguy</tt>. These two commands tell the game to create 2 characters: Top_Striker, and Top_Comguy.

Since that these characters do not spawn in the room, they must be teleported there. Using the <tt>chr_teleport</tt> command used earlier to teleport yourself, modify it to teleport the 2 AI using their names instead of "0". Teleport them to the flags "7008" and "7009" respectively. Refer to the example above or the list of function calls above to write this in.

It should now look like this :

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
ai2_spawn Top_Striker 
ai2_spawn Top_Comguy 
chr_teleport Top_Striker 7008 
chr_teleport Top_Comguy 7009 
}</tt>

This script will now teleport you into the final training room and face you off against 2 Strikers.

This fight too easy? In the next section, we will learn how to spice up the fight, and let you develop your own script.

----

== Part 6: Customization==

Here, you will be able to split off and customize your script.
Each subsection will represent a way to customize the above script.

===Weapons and Powerups===
These are the easiest things to add into a battle.

Weapons can be spawned on the ground or given to characters.

====Giving Characters Weapons====

Giving characters weapons is very easy. Simply use the command <tt>chr_giveweapon</tt> to give a character a weapon.

[[OSL:Inventory|Here]] are the list of the weapon codes. For the purpose of this example, we will use <tt>w3_phr</tt>, the plasma rifle. This command will give the two strikers plasma rifles.

Add the commands <tt>chr_giveweapon Top_Striker w3_phr</tt> and <tt>chr_giveweapon Top_Comguy w3_phr</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute.

====Spawning Weapons on the ground====

Spawning weapons is simple. Use the command <tt>weapon_spawn</tt> to spawn a weapon.

Add the commands <tt>weapon_spawn w3_phr 7008</tt> and <tt>weapon_spawn w3_phr 7009</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will spawn 2 plasma rifles, one under each striker's feet. AI will automatically pick up weapons with ammo or empty weapons they have ammo for.

====Giving Characters Powerups====

Giving characters powerups is much like giving characters weapons. Use the command <tt>chr_givepowerup</tt> to give a character a powerup.

The powerups you can give a character are :
* shield : Gives a force shield
* invis : Gives a phase cloak
* ammo : Gives a ballistic ammo
* cell : Gives an energy cell.

For the purpose of this example, we will give the characters invisibilities.

Add the commands <tt>chr_givepowerup Top_Striker invis -1</tt> and <tt>chr_givepowerup Top_Comguy invis -1</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will make the strikers permanently invisible. To make then visible after 30 seconds, erase "-1".

====Spawning Powerups on the Ground====

Spawning powerups are simple. Use the command <tt>powerup_spawn</tt> to spawn a powerup.

Add the commands <tt>powerup_spawn invis 7008</tt> and <tt>powerup_spawn invis 7009</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will spawn 2 phase cloaks beneath the striker's feet. Since AI will not pick up powerups, this is for you only.

===Extra Characters===

Addubg extra characters to the script is easy. Just follow the steps for adding the first AI and follow the procedure, look for AI names [[OSL: AI names|Here]].

====Adding Enemies====

Look at the chart for what teams the AI are on. Most of the time, adding enemies simply involve spawning and teleporting the AI. As long as the team in "Syndicate", it will be an enemy. If you want to add an emeny from an allied team, use the <tt>chr_changeteam</tt> command to changet their team to "Syndicate" like this:

<tt>chr_changeteam griffin Syndicate</tt>

====Adding Allies====

Look at the chart for what teams the AI are on. As long as the team is "TCTF" or "Konoko", it will be an ally for you in this script. If you want to add an ally from the enemy team, use the <tt>chr_changeteam</tt> command to changet their team to "TCTF" or "Konoko" like this:

<tt>chr_changeteam WH_Striker_D TCTF</tt>

===Overpower===

Use the <tt>chr_set_health</tt> command to set a character's health. Note that each character has a base health that may not be the same. For example, konoko's base health is 200, while a brown striker's is only 50. Keep this in mind when setting character's health. Setting it over their base health will send them into overpower - like using a hypo at full health. The health will drain at 1 every second even for AI. This example sets konoko's health to 400 - overpower.

<tt>chr_set_health 0 400</tt>

This following example shows everything listed above added.

<tt>func void main(void) 
{ 
 
chr_teleport 0 7010 
powerup_spawn hypo 7010 
 
ai2_spawn Top_Striker 
ai2_spawn Top_Comguy 
 
chr_teleport Top_Striker 7008 
chr_teleport Top_Comguy 7009 
 
chr_givepowerup Top_Striker invis -1 
chr_givepowerup Top_Comguy invis -1 
powerup_spawn invis 7007 
powerup_spawn invis 7009 
 
chr_giveweapon Top_Striker w7_scc 
chr_giveweapon Top_Comguy w3_phr 
chr_givepowerup Top_Striker ammo 15 
chr_givepowerup Top_Comguy cell 30 
 
weapon_spawn w2_sap 7045 
powerup_spawn ammo 7008 
 
ai2_spawn OutroTCTF01 
chr_teleport OutroTCTF01 7007 
 
ai2_spawn WH_Thug_A 
chr_changeteam WH_Thug_A TCTF 
chr_teleport WH_Thug_A 7007 
 
ai2_spawn griffin 
chr_changeteam griffin Syndicate 
chr_teleport griffin 7008 
chr_set_health griffin 3900 
}</tt>

----

== Part 7: Delay ==

<tt>sleep</tt> 
<tt>chr_wait_health</tt>

To wait for some time before executing a command, use <tt>sleep</tt>. To wait for approx 5 seconds before spawning an extra drone, go like this:

<tt>sleep 300 
ai2_spawn dum_train_block 
chr_teleport dum_train_block 7010 
</tt>

To wait for a striker to die and then spawn some drones, go like this:

<tt>chr_wait_health Top_Striker 0 
ai2_spawn dum_train_block 
chr_teleport dum_train_block 7010 </tt>

== Part 8: Forking and Separate Functions==

This is the part where we start moving commands out of "main". Create a new function called "logic" like this : type "func logic" two lines below the '''}''' of "main". Type '''{''' nad copy out everything inside "main" into "logic". Type <tt>fork logic</tt> in main. It should look like this :

<tt>func void main(void) 
{ 
fork logic 
} 
 
func logic 
{ 
... 
}</tt>

... being whatever you had in "main" before. Add <tt>chr_wait_health griffin 0</tt> at the end of "logic", then type <tt>fork logic2</tt>. Create the function "logic2". In "logic2" you can write whatever you want that you have learned before. For the prupose of this example, '''...''' will represent whatever you had, '''..''' will represent whatever you want, and typed text will represent thing that must be included.

<tt>func void main(void) 
{ 
fork logic 
} 
 
func logic 
{ 
... 
chr_wait_health griffin 0 
fork logic2 
} 
 
func logic2 { 
.. 
}</tt>

===Extra: Multiple Forking===

More than one function can be forked in the same function. Look at ths example :

<tt>func void main(void) 
{ 
fork logicA 
fork logicB 
} 

func logicA { 
.. 
} 

func logicB { 
.. }</tt>

Both "logicA" and "logicB" are executed at the same time. If <tt>chr_wait_health griffin 0</tt> were to be removed, likewise, both "logic" and "logic2" are executed at the same time.

== Part 9: Variables and Save Points ==

Every wondered why there is no folder for basic training? The truth is, it is actually part of the Warehouse level and is managed by save points.

This is the beginning of the "level_start" which is forked from "main" in the original level scripts.

<tt>func void level_start(string ai_name) 
{ 
 
my_save_point = save_point; 
 
if (my_save_point eq 0) 
{ 
... 
} 
 
if (my_save_point eq 1) 
{ 
... 
} 
 
if (my_save_point eq 2) 
{ 
... 
} 
 
if (my_save_point eq 3) 
{ 
... 
} 
 
if (my_save_point eq 4) 
{ 
... 
} 
 
if (my_save_point eq 5) 
{ 
... 
} 
}</tt>

- Your_Mom

BSL:Tutorial/Scratch

2005-11-20T18:24:24Z

Your Mom: /* Part 8: Forking and Separate Functions */

This page is a short tutorial on how to get started on simple scripts for those who have had no experience with scripting before.
It will teach you, step by step, how to write a simple script. By the end of this tutorial, you will be able to move on to more advanced scripts.

----

== Part 1 : Knowing your formats ==

The game will accept 2 types of syntax for scripts, and they are based on different styles of writing. Choose the one that suits you best.

The types are :

Shell-Style:
This is compiled much like some System-Shells. It is written in a "one-function-call-a-line" format, and is the easiest to begin with if you have had no coding experience, as the code is neatly displayed line after line. The downside of this it, that once you get into more complex scripts or scripts with many function calls, the file becomes very hard to read and very large.

Example: [[Shell-Style]]

C-Style:
This is compiled much like the popular coding style C. The syntax can be placed into multiple-function lines and functions are divided by a ''';''' . In advanced scripts, this style will allow you to condense your script and the parts will be easier to read/debug. It also allows you to utilize some of the more advanced features easily. The problem with this is, that starting off, it is harder to write if you have had no previous experience with coding.

Example: [[C-Style]]

For the purpose of this article, we will use Shell-Style syntax for simplicity.

----

== Part 2: Starting Off ==

Now, I suggest reading the original script files to get a basic idea for how scripts are laid out. This will allow us to jump-start a bit.

Open up your IMGD and look for the following folder: EnvWarehouse.
Open it up, and we'll take a look at how it it laid out. There should be several files in here. Open using NOTEPAD, the one titled '''warehouse_main.bsl'''. It should look like this:

<tt>
func void main(void) 
{ 
env_show 2010 0 
gl_fog_blue=.15 
gl_fog_red=.15 
gl_fog_green=.15 
gl_fog_start=.99 
gs_farclipplane_set 5000 
obj_create 20 20 
level_start 
 
}</tt>

This is an example of a '''main''' file. It contains the information of how the level starts.

Ignore the contents of the script for now, and notice that the contents of the function <tt>main</tt> are enclosed by a set of brackets ('''{''' and '''}''').

All functions must be enclosed in this set of brackets or it will not be executed.

Close the file, and rename the folder "EnvWarehouse" "EnvWarehouse_original". Then, create a folder called "EnvWarehouse" and create a script file inside and name it "Tutorial". We will be using this file to show various examples of scripts and finally, write a small script of your own.

----

== Part 3: Basic Commands ==

This is just a small section explaining the commands that will be used in this tutorial. For a complete list of commands, see [http://www.fh-eberswalde.de/user/dkriesch/onistuff/commands.htm Ssg's Site] for more information.

ai2_spawn (name) - creates and starts an AI from a character object 
chr_teleport (name) (flag) - teleports a character to a flag 
chr_givepowerup (name) (powerup) (amount) - gives a character a powerup 
.
.
.

----

== Part 4: First Script ==

This section will teach you how to write a very basic script (fighting script). It will start you off in the Final Training Room, where you practiced firing weapons in the original game. With this script, the room will appear very empty.

Let's open up the "Tutorial.bsl" file and start writing the script.

First, declare it the "main" portion of the script by typing "<tt>func void main(void)</tt> at the very beginning of the file. This tells the game which function it is. The "main" function is the function that the game looks at first to determine what is to be executed.

Below that line, type '''{'''. This tells the game that the function has started.

Add a space, and then type <tt>chr_teleport 0 7010</tt>. This function teleports Konoko (her id is always 0) to the flag 7010. It is located in the final training room.

Finish the function "main" by typing '''}''' on the next line.

It should look like this:

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
}</tt>

Save the file, load up Oni, and click "New Game". You should be standing in the center of the final combat training room.

You are now on your way!

----

== Part 5: Adding NPCs (AI) ==

Before we begin, notice that there are two types of AI. AI created from character objects, and AI created from memory. AI created from character objects are created by the function call <tt>ai2_spawn (name)</tt>, where (name) is the name of the AI. AI created from memory are created by the function call <tt>chr_create (ai_number) start,</tt>. These AI do not have combat logic, and thus will not attack you physically but can still use weapons.

Now, we are going to add 2 enemy AI to our script that we wrote in the last section. Open it up, and lets add some enemies for Konoko to fight.

To recap, it should look like this :

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
}</tt>

After the function call <tt>chr_teleport 0 7010</tt>, add the following 2 commands on separate lines: <tt>ai2_spawn Top_Striker</tt> and <tt>ai2_spawn Top_Comguy</tt>. These two commands tell the game to create 2 characters: Top_Striker, and Top_Comguy.

Since that these characters do not spawn in the room, they must be teleported there. Using the <tt>chr_teleport</tt> command used earlier to teleport yourself, modify it to teleport the 2 AI using their names instead of "0". Teleport them to the flags "7008" and "7009" respectively. Refer to the example above or the list of function calls above to write this in.

It should now look like this :

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
ai2_spawn Top_Striker 
ai2_spawn Top_Comguy 
chr_teleport Top_Striker 7008 
chr_teleport Top_Comguy 7009 
}</tt>

This script will now teleport you into the final training room and face you off against 2 Strikers.

This fight too easy? In the next section, we will learn how to spice up the fight, and let you develop your own script.

----

== Part 6: Customization==

Here, you will be able to split off and customize your script.
Each subsection will represent a way to customize the above script.

===Weapons and Powerups===
These are the easiest things to add into a battle.

Weapons can be spawned on the ground or given to characters.

====Giving Characters Weapons====

Giving characters weapons is very easy. Simply use the command <tt>chr_giveweapon</tt> to give a character a weapon.

[[OSL:Inventory|Here]] are the list of the weapon codes. For the purpose of this example, we will use <tt>w3_phr</tt>, the plasma rifle. This command will give the two strikers plasma rifles.

Add the commands <tt>chr_giveweapon Top_Striker w3_phr</tt> and <tt>chr_giveweapon Top_Comguy w3_phr</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute.

====Spawning Weapons on the ground====

Spawning weapons is simple. Use the command <tt>weapon_spawn</tt> to spawn a weapon.

Add the commands <tt>weapon_spawn w3_phr 7008</tt> and <tt>weapon_spawn w3_phr 7009</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will spawn 2 plasma rifles, one under each striker's feet. AI will automatically pick up weapons with ammo or empty weapons they have ammo for.

====Giving Characters Powerups====

Giving characters powerups is much like giving characters weapons. Use the command <tt>chr_givepowerup</tt> to give a character a powerup.

The powerups you can give a character are :
* shield : Gives a force shield
* invis : Gives a phase cloak
* ammo : Gives a ballistic ammo
* cell : Gives an energy cell.

For the purpose of this example, we will give the characters invisibilities.

Add the commands <tt>chr_givepowerup Top_Striker invis -1</tt> and <tt>chr_givepowerup Top_Comguy invis -1</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will make the strikers permanently invisible. To make then visible after 30 seconds, erase "-1".

====Spawning Powerups on the Ground====

Spawning powerups are simple. Use the command <tt>powerup_spawn</tt> to spawn a powerup.

Add the commands <tt>powerup_spawn invis 7008</tt> and <tt>powerup_spawn invis 7009</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will spawn 2 phase cloaks beneath the striker's feet. Since AI will not pick up powerups, this is for you only.

===Extra Characters===

Addubg extra characters to the script is easy. Just follow the steps for adding the first AI and follow the procedure, look for AI names [[OSL: AI names|Here]].

====Adding Enemies====

Look at the chart for what teams the AI are on. Most of the time, adding enemies simply involve spawning and teleporting the AI. As long as the team in "Syndicate", it will be an enemy. If you want to add an emeny from an allied team, use the <tt>chr_changeteam</tt> command to changet their team to "Syndicate" like this:

<tt>chr_changeteam griffin Syndicate</tt>

====Adding Allies====

Look at the chart for what teams the AI are on. As long as the team is "TCTF" or "Konoko", it will be an ally for you in this script. If you want to add an ally from the enemy team, use the <tt>chr_changeteam</tt> command to changet their team to "TCTF" or "Konoko" like this:

<tt>chr_changeteam WH_Striker_D TCTF</tt>

===Overpower===

Use the <tt>chr_set_health</tt> command to set a character's health. Note that each character has a base health that may not be the same. For example, konoko's base health is 200, while a brown striker's is only 50. Keep this in mind when setting character's health. Setting it over their base health will send them into overpower - like using a hypo at full health. The health will drain at 1 every second even for AI. This example sets konoko's health to 400 - overpower.

<tt>chr_set_health 0 400</tt>

This following example shows everything listed above added.

<tt>func void main(void) 
{ 
 
chr_teleport 0 7010 
powerup_spawn hypo 7010 
 
ai2_spawn Top_Striker 
ai2_spawn Top_Comguy 
 
chr_teleport Top_Striker 7008 
chr_teleport Top_Comguy 7009 
 
chr_givepowerup Top_Striker invis -1 
chr_givepowerup Top_Comguy invis -1 
powerup_spawn invis 7007 
powerup_spawn invis 7009 
 
chr_giveweapon Top_Striker w7_scc 
chr_giveweapon Top_Comguy w3_phr 
chr_givepowerup Top_Striker ammo 15 
chr_givepowerup Top_Comguy cell 30 
 
weapon_spawn w2_sap 7045 
powerup_spawn ammo 7008 
 
ai2_spawn OutroTCTF01 
chr_teleport OutroTCTF01 7007 
 
ai2_spawn WH_Thug_A 
chr_changeteam WH_Thug_A TCTF 
chr_teleport WH_Thug_A 7007 
 
ai2_spawn griffin 
chr_changeteam griffin Syndicate 
chr_teleport griffin 7008 
chr_set_health griffin 3900 
}</tt>

----

== Part 7: Delay ==

<tt>sleep</tt> 
<tt>chr_wait_health</tt>

To wait for some time before executing a command, use <tt>sleep</tt>. To wait for approx 5 seconds before spawning an extra drone, go like this:

<tt>sleep 300 
ai2_spawn dum_train_block 
chr_teleport dum_train_block 7010 
</tt>

To wait for a striker to die and then spawn some drones, go like this:

<tt>chr_wait_health Top_Striker 0 
ai2_spawn dum_train_block 
chr_teleport dum_train_block 7010 </tt>

== Part 8: Forking and Separate Functions==

This is the part where we start moving commands out of "main". Create a new function called "logic" like this : type "func logic" two lines below the '''}''' of "main". Type '''{''' nad copy out everything inside "main" into "logic". Type <tt>fork logic</tt> in main. It should look like this :

<tt>func void main(void) 
{ 
fork logic 
} 
 
func logic 
{ 
... 
}</tt>

... being whatever you had in "main" before. Add <tt>chr_wait_health griffin 0</tt> at the end of "logic", then type <tt>fork logic2</tt>. Create the function "logic2". In "logic2" you can write whatever you want that you have learned before. For the prupose of this example, '''...''' will represent whatever you had, '''..''' will represent whatever you want, and typed text will represent thing that must be included.

<tt>func void main(void) 
{ 
fork logic 
} 
 
func logic 
{ 
... 
chr_wait_health griffin 0 
fork logic2 
} 
 
func logic2 { 
.. 
}</tt>

===Extra: Multiple Forking===

More than one function can be forked in the same function. Look at ths example :

<tt>func void main(void) 
{ 
fork logicA 
fork logicB 
} 

func logicA { 
.. 
} 

func logicB { 
.. }</tt>

Both "logicA" and "logicB" are executed at the same time. If <tt>chr_wait_health griffin 0</tt> were to be removed, likewise, both "logic" and "logic2" are executed at the same time.

== Part 9: Variables and Save Points ==

Every wondered why there is no folder for basic training? The truth is, it is actually part of the Warehouse level and is managed by save points.

This is the beginning of the "level_start" which is forked from "main" in the original level scripts.

<tt>func void level_start(string ai_name) 
{ 
 
my_save_point = save_point; 
 
if (my_save_point eq 0) 
{ 
... 
} 
 
if (my_save_point eq 1) 
{ 
... 
} 
 
if (my_save_point eq 2) 
{ 
... 
} 
 
if (my_save_point eq 3) 
{ 
... 
} 
 
if (my_save_point eq 4) 
{ 
... 
} 
 
if (my_save_point eq 5) 
{ 
... 
} 
}</tt>

- Your_Mom

BSL:Tutorial/Scratch

2005-11-20T18:23:37Z

Your Mom: /* Part 7: Delay */

This page is a short tutorial on how to get started on simple scripts for those who have had no experience with scripting before.
It will teach you, step by step, how to write a simple script. By the end of this tutorial, you will be able to move on to more advanced scripts.

----

== Part 1 : Knowing your formats ==

The game will accept 2 types of syntax for scripts, and they are based on different styles of writing. Choose the one that suits you best.

The types are :

Shell-Style:
This is compiled much like some System-Shells. It is written in a "one-function-call-a-line" format, and is the easiest to begin with if you have had no coding experience, as the code is neatly displayed line after line. The downside of this it, that once you get into more complex scripts or scripts with many function calls, the file becomes very hard to read and very large.

Example: [[Shell-Style]]

C-Style:
This is compiled much like the popular coding style C. The syntax can be placed into multiple-function lines and functions are divided by a ''';''' . In advanced scripts, this style will allow you to condense your script and the parts will be easier to read/debug. It also allows you to utilize some of the more advanced features easily. The problem with this is, that starting off, it is harder to write if you have had no previous experience with coding.

Example: [[C-Style]]

For the purpose of this article, we will use Shell-Style syntax for simplicity.

----

== Part 2: Starting Off ==

Now, I suggest reading the original script files to get a basic idea for how scripts are laid out. This will allow us to jump-start a bit.

Open up your IMGD and look for the following folder: EnvWarehouse.
Open it up, and we'll take a look at how it it laid out. There should be several files in here. Open using NOTEPAD, the one titled '''warehouse_main.bsl'''. It should look like this:

<tt>
func void main(void) 
{ 
env_show 2010 0 
gl_fog_blue=.15 
gl_fog_red=.15 
gl_fog_green=.15 
gl_fog_start=.99 
gs_farclipplane_set 5000 
obj_create 20 20 
level_start 
 
}</tt>

This is an example of a '''main''' file. It contains the information of how the level starts.

Ignore the contents of the script for now, and notice that the contents of the function <tt>main</tt> are enclosed by a set of brackets ('''{''' and '''}''').

All functions must be enclosed in this set of brackets or it will not be executed.

Close the file, and rename the folder "EnvWarehouse" "EnvWarehouse_original". Then, create a folder called "EnvWarehouse" and create a script file inside and name it "Tutorial". We will be using this file to show various examples of scripts and finally, write a small script of your own.

----

== Part 3: Basic Commands ==

This is just a small section explaining the commands that will be used in this tutorial. For a complete list of commands, see [http://www.fh-eberswalde.de/user/dkriesch/onistuff/commands.htm Ssg's Site] for more information.

ai2_spawn (name) - creates and starts an AI from a character object 
chr_teleport (name) (flag) - teleports a character to a flag 
chr_givepowerup (name) (powerup) (amount) - gives a character a powerup 
.
.
.

----

== Part 4: First Script ==

This section will teach you how to write a very basic script (fighting script). It will start you off in the Final Training Room, where you practiced firing weapons in the original game. With this script, the room will appear very empty.

Let's open up the "Tutorial.bsl" file and start writing the script.

First, declare it the "main" portion of the script by typing "<tt>func void main(void)</tt> at the very beginning of the file. This tells the game which function it is. The "main" function is the function that the game looks at first to determine what is to be executed.

Below that line, type '''{'''. This tells the game that the function has started.

Add a space, and then type <tt>chr_teleport 0 7010</tt>. This function teleports Konoko (her id is always 0) to the flag 7010. It is located in the final training room.

Finish the function "main" by typing '''}''' on the next line.

It should look like this:

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
}</tt>

Save the file, load up Oni, and click "New Game". You should be standing in the center of the final combat training room.

You are now on your way!

----

== Part 5: Adding NPCs (AI) ==

Before we begin, notice that there are two types of AI. AI created from character objects, and AI created from memory. AI created from character objects are created by the function call <tt>ai2_spawn (name)</tt>, where (name) is the name of the AI. AI created from memory are created by the function call <tt>chr_create (ai_number) start,</tt>. These AI do not have combat logic, and thus will not attack you physically but can still use weapons.

Now, we are going to add 2 enemy AI to our script that we wrote in the last section. Open it up, and lets add some enemies for Konoko to fight.

To recap, it should look like this :

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
}</tt>

After the function call <tt>chr_teleport 0 7010</tt>, add the following 2 commands on separate lines: <tt>ai2_spawn Top_Striker</tt> and <tt>ai2_spawn Top_Comguy</tt>. These two commands tell the game to create 2 characters: Top_Striker, and Top_Comguy.

Since that these characters do not spawn in the room, they must be teleported there. Using the <tt>chr_teleport</tt> command used earlier to teleport yourself, modify it to teleport the 2 AI using their names instead of "0". Teleport them to the flags "7008" and "7009" respectively. Refer to the example above or the list of function calls above to write this in.

It should now look like this :

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
ai2_spawn Top_Striker 
ai2_spawn Top_Comguy 
chr_teleport Top_Striker 7008 
chr_teleport Top_Comguy 7009 
}</tt>

This script will now teleport you into the final training room and face you off against 2 Strikers.

This fight too easy? In the next section, we will learn how to spice up the fight, and let you develop your own script.

----

== Part 6: Customization==

Here, you will be able to split off and customize your script.
Each subsection will represent a way to customize the above script.

===Weapons and Powerups===
These are the easiest things to add into a battle.

Weapons can be spawned on the ground or given to characters.

====Giving Characters Weapons====

Giving characters weapons is very easy. Simply use the command <tt>chr_giveweapon</tt> to give a character a weapon.

[[OSL:Inventory|Here]] are the list of the weapon codes. For the purpose of this example, we will use <tt>w3_phr</tt>, the plasma rifle. This command will give the two strikers plasma rifles.

Add the commands <tt>chr_giveweapon Top_Striker w3_phr</tt> and <tt>chr_giveweapon Top_Comguy w3_phr</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute.

====Spawning Weapons on the ground====

Spawning weapons is simple. Use the command <tt>weapon_spawn</tt> to spawn a weapon.

Add the commands <tt>weapon_spawn w3_phr 7008</tt> and <tt>weapon_spawn w3_phr 7009</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will spawn 2 plasma rifles, one under each striker's feet. AI will automatically pick up weapons with ammo or empty weapons they have ammo for.

====Giving Characters Powerups====

Giving characters powerups is much like giving characters weapons. Use the command <tt>chr_givepowerup</tt> to give a character a powerup.

The powerups you can give a character are :
* shield : Gives a force shield
* invis : Gives a phase cloak
* ammo : Gives a ballistic ammo
* cell : Gives an energy cell.

For the purpose of this example, we will give the characters invisibilities.

Add the commands <tt>chr_givepowerup Top_Striker invis -1</tt> and <tt>chr_givepowerup Top_Comguy invis -1</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will make the strikers permanently invisible. To make then visible after 30 seconds, erase "-1".

====Spawning Powerups on the Ground====

Spawning powerups are simple. Use the command <tt>powerup_spawn</tt> to spawn a powerup.

Add the commands <tt>powerup_spawn invis 7008</tt> and <tt>powerup_spawn invis 7009</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will spawn 2 phase cloaks beneath the striker's feet. Since AI will not pick up powerups, this is for you only.

===Extra Characters===

Addubg extra characters to the script is easy. Just follow the steps for adding the first AI and follow the procedure, look for AI names [[OSL: AI names|Here]].

====Adding Enemies====

Look at the chart for what teams the AI are on. Most of the time, adding enemies simply involve spawning and teleporting the AI. As long as the team in "Syndicate", it will be an enemy. If you want to add an emeny from an allied team, use the <tt>chr_changeteam</tt> command to changet their team to "Syndicate" like this:

<tt>chr_changeteam griffin Syndicate</tt>

====Adding Allies====

Look at the chart for what teams the AI are on. As long as the team is "TCTF" or "Konoko", it will be an ally for you in this script. If you want to add an ally from the enemy team, use the <tt>chr_changeteam</tt> command to changet their team to "TCTF" or "Konoko" like this:

<tt>chr_changeteam WH_Striker_D TCTF</tt>

===Overpower===

Use the <tt>chr_set_health</tt> command to set a character's health. Note that each character has a base health that may not be the same. For example, konoko's base health is 200, while a brown striker's is only 50. Keep this in mind when setting character's health. Setting it over their base health will send them into overpower - like using a hypo at full health. The health will drain at 1 every second even for AI. This example sets konoko's health to 400 - overpower.

<tt>chr_set_health 0 400</tt>

This following example shows everything listed above added.

<tt>func void main(void) 
{ 
 
chr_teleport 0 7010 
powerup_spawn hypo 7010 
 
ai2_spawn Top_Striker 
ai2_spawn Top_Comguy 
 
chr_teleport Top_Striker 7008 
chr_teleport Top_Comguy 7009 
 
chr_givepowerup Top_Striker invis -1 
chr_givepowerup Top_Comguy invis -1 
powerup_spawn invis 7007 
powerup_spawn invis 7009 
 
chr_giveweapon Top_Striker w7_scc 
chr_giveweapon Top_Comguy w3_phr 
chr_givepowerup Top_Striker ammo 15 
chr_givepowerup Top_Comguy cell 30 
 
weapon_spawn w2_sap 7045 
powerup_spawn ammo 7008 
 
ai2_spawn OutroTCTF01 
chr_teleport OutroTCTF01 7007 
 
ai2_spawn WH_Thug_A 
chr_changeteam WH_Thug_A TCTF 
chr_teleport WH_Thug_A 7007 
 
ai2_spawn griffin 
chr_changeteam griffin Syndicate 
chr_teleport griffin 7008 
chr_set_health griffin 3900 
}</tt>

----

== Part 7: Delay ==

<tt>sleep</tt> 
<tt>chr_wait_health</tt>

To wait for some time before executing a command, use <tt>sleep</tt>. To wait for approx 5 seconds before spawning an extra drone, go like this:

<tt>sleep 300 
ai2_spawn dum_train_block 
chr_teleport dum_train_block 7010 
</tt>

To wait for a striker to die and then spawn some drones, go like this:

<tt>chr_wait_health Top_Striker 0 
ai2_spawn dum_train_block 
chr_teleport dum_train_block 7010 </tt>

== Part 8: Forking and Separate Functions==

This is the part where we start moving commands out of "main". Create a new function called "logic" like this : type "func logic" two lines below the '''}''' of "main". Type '''{''' nad copy out everything inside "main" into "logic". Type <tt>fork logic</tt> in main. It should look like this :

<tt>func void main(void) 
{ 
fork logic 
} 
 
func logic 
{ 
... 
}</tt>

... being whatever you had in "main" before. Add <tt>chr_wait_health griffin 0</tt> at the end of "logic", then type <tt>fork logic2</tt>. Create the function "logic2". In "logic2" you can write whatever you want that you have learned before. For the prupose of this example, '''...''' will represent whatever you had, '''..''' will represent whatever you want, and typed text will represent thing that must be included.

<tt>func void main(void) 
{ 
fork logic 
} 
 
func logic 
{ 
... 
chr_wait_health griffin 0 
fork logic2 
} 
 
func logic2 { 
.. 
} 

===Extra: Multiple Forking===

More than one function can be forked in the same function. Look at ths example :

<tt>func void main(void) 
{ 
fork logicA 
fork logicB 
} 

func logicA { 
.. 
} 

func logicB { 
.. }</tt>

Both "logicA" and "logicB" are executed at the same time. If <tt>chr_wait_health griffin 0</tt> were to be removed, likewise, both "logic" and "logic2" are executed at the same time.

== Part 9: Variables and Save Points ==

Every wondered why there is no folder for basic training? The truth is, it is actually part of the Warehouse level and is managed by save points.

This is the beginning of the "level_start" which is forked from "main" in the original level scripts.

<tt>func void level_start(string ai_name) 
{ 
 
my_save_point = save_point; 
 
if (my_save_point eq 0) 
{ 
... 
} 
 
if (my_save_point eq 1) 
{ 
... 
} 
 
if (my_save_point eq 2) 
{ 
... 
} 
 
if (my_save_point eq 3) 
{ 
... 
} 
 
if (my_save_point eq 4) 
{ 
... 
} 
 
if (my_save_point eq 5) 
{ 
... 
} 
}</tt>

- Your_Mom

Oni (folder)/GameDataFolder/IGMD/compound

2005-11-19T18:06:10Z

Your Mom: /* Available mods */

==Level logic for Chapter 14:DAWN OF THE CHRYSALIS==
aka '''Syndicate Mountain Compound''' (Sturmanderung)
===Associated binaries===
*level19_Final.dat
*level19_Final.raw
===Original contents===
*[http://geyser.oni2.net/OSL/IGMD/compound/compound.bsl compound.bsl]
*[http://geyser.oni2.net/OSL/IGMD/compound/compound_cutscene.bsl compound_cutscene.bsl]
*[http://geyser.oni2.net/OSL/IGMD/compound/compound_main.bsl compound_main.bsl]
*[http://geyser.oni2.net/OSL/IGMD/compound/particle_scripts.bsl particle_scripts.bsl]

==="Overcommented" version (not online yet)===
*compound.bsl
*compound_cutscene.bsl
*compound_main.bsl
*particle_scripts.bsl
===Rewritten version (not online yet)===
*different filenames...

==Available mods==

[http://your_mom.oni2.net/Downloads/My%20Other%20Scripts/mountainrallyv1.1.zip MR 1.1]

==Related issues==

Oni (folder)/GameDataFolder/IGMD/roof

2005-11-19T18:05:02Z

Your Mom: /* Available mods */

==Level logic for Chapter 10:CAT AND MOUSE==
aka '''Rooftops'''
===Associated binaries===
*level12_Final.dat
*level12_Final.raw
===Original contents===
*[http://geyser.oni2.net/OSL/IGMD/roof/particle_scripts.bsl particle_scripts.bsl]
*[http://geyser.oni2.net/OSL/IGMD/roof/roof.bsl roof.bsl]
*[http://geyser.oni2.net/OSL/IGMD/roof/roof_cutscene.bsl roof_cutscene.bsl]
*[http://geyser.oni2.net/OSL/IGMD/roof/roof_main.bsl roof_main.bsl]

==="Overcommented" version (not online yet)===
*particle_scripts.bsl
*roof.bsl
*roof_cutscene.bsl
*roof_main.bsl
===Rewritten version (not online yet)===
*different filenames...

==Available mods==

[http://your_mom.oni2.net/Downloads/My%20Other%20Scripts/Mukade's%20Wonderful%20Battle%20Arena.zip MWBA]

==Related issues==

Oni (folder)/GameDataFolder/IGMD/state

2005-11-19T18:03:41Z

Your Mom: /* Available mods */

==Level logic for Chapter 9:TRUTH AND CONSEQUENCES==
aka '''Regional State Building'''
===Associated binaries===
*level11_Final.dat
*level11_Final.raw

===Original contents===
*[http://geyser.oni2.net/OSL/IGMD/state/state_cutscene.bsl state_cutscene.bsl]
*[http://geyser.oni2.net/OSL/IGMD/state/state_level_logic.bsl state_level_logic.bsl]
*[http://geyser.oni2.net/OSL/IGMD/state/state_main.bsl state_main.bsl]

==="Overcommented" version (not online yet)===
*state_cutscene.bsl
*state_level_logic.bsl
*state_main.bsl
===Rewritten version (not online yet)===
*different filenames...

==Available mods==

[http://your_mom.oni2.net/Downloads/Scripts%20By%20Various%20Authors/ddstate.zip DDstate]

==Related issues==

BSL:Tutorial/Scratch

2005-11-18T03:36:11Z

Your Mom: /* Overpower */

This page is a short tutorial on how to get started on simple scripts for those who have had no experience with scripting before.
It will teach you, step by step, how to write a simple script. By the end of this tutorial, you will be able to move on to more advanced scripts.

----

== Part 1 : Knowing your formats ==

The game will accept 2 types of syntax for scripts, and they are based on different styles of writing. Choose the one that suits you best.

The types are :

Shell-Style:
This is compiled much like some System-Shells. It is written in a "one-function-call-a-line" format, and is the easiest to begin with if you have had no coding experience, as the code is neatly displayed line after line. The downside of this it, that once you get into more complex scripts or scripts with many function calls, the file becomes very hard to read and very large.

Example: [[Shell-Style]]

C-Style:
This is compiled much like the popular coding style C. The syntax can be placed into multiple-function lines and functions are divided by a ''';''' . In advanced scripts, this style will allow you to condense your script and the parts will be easier to read/debug. It also allows you to utilize some of the more advanced features easily. The problem with this is, that starting off, it is harder to write if you have had no previous experience with coding.

Example: [[C-Style]]

For the purpose of this article, we will use Shell-Style syntax for simplicity.

----

== Part 2: Starting Off ==

Now, I suggest reading the original script files to get a basic idea for how scripts are laid out. This will allow us to jump-start a bit.

Open up your IMGD and look for the following folder: EnvWarehouse.
Open it up, and we'll take a look at how it it laid out. There should be several files in here. Open using NOTEPAD, the one titled '''warehouse_main.bsl'''. It should look like this:

<tt>
func void main(void) 
{ 
env_show 2010 0 
gl_fog_blue=.15 
gl_fog_red=.15 
gl_fog_green=.15 
gl_fog_start=.99 
gs_farclipplane_set 5000 
obj_create 20 20 
level_start 
 
}</tt>

This is an example of a '''main''' file. It contains the information of how the level starts.

Ignore the contents of the script for now, and notice that the contents of the function <tt>main</tt> are enclosed by a set of brackets ('''{''' and '''}''').

All functions must be enclosed in this set of brackets or it will not be executed.

Close the file, and rename the folder "EnvWarehouse" "EnvWarehouse_original". Then, create a folder called "EnvWarehouse" and create a script file inside and name it "Tutorial". We will be using this file to show various examples of scripts and finally, write a small script of your own.

----

== Part 3: Basic Commands ==

This is just a small section explaining the commands that will be used in this tutorial. For a complete list of commands, see [http://www.fh-eberswalde.de/user/dkriesch/onistuff/commands.htm Ssg's Site] for more information.

ai2_spawn (name) - creates and starts an AI from a character object 
chr_teleport (name) (flag) - teleports a character to a flag 
chr_givepowerup (name) (powerup) (amount) - gives a character a powerup 
.
.
.

----

== Part 4: First Script ==

This section will teach you how to write a very basic script (fighting script). It will start you off in the Final Training Room, where you practiced firing weapons in the original game. With this script, the room will appear very empty.

Let's open up the "Tutorial.bsl" file and start writing the script.

First, declare it the "main" portion of the script by typing "<tt>func void main(void)</tt> at the very beginning of the file. This tells the game which function it is. The "main" function is the function that the game looks at first to determine what is to be executed.

Below that line, type '''{'''. This tells the game that the function has started.

Add a space, and then type <tt>chr_teleport 0 7010</tt>. This function teleports Konoko (her id is always 0) to the flag 7010. It is located in the final training room.

Finish the function "main" by typing '''}''' on the next line.

It should look like this:

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
}</tt>

Save the file, load up Oni, and click "New Game". You should be standing in the center of the final combat training room.

You are now on your way!

----

== Part 5: Adding NPCs (AI) ==

Before we begin, notice that there are two types of AI. AI created from character objects, and AI created from memory. AI created from character objects are created by the function call <tt>ai2_spawn (name)</tt>, where (name) is the name of the AI. AI created from memory are created by the function call <tt>chr_create (ai_number) start,</tt>. These AI do not have combat logic, and thus will not attack you physically but can still use weapons.

Now, we are going to add 2 enemy AI to our script that we wrote in the last section. Open it up, and lets add some enemies for Konoko to fight.

To recap, it should look like this :

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
}</tt>

After the function call <tt>chr_teleport 0 7010</tt>, add the following 2 commands on separate lines: <tt>ai2_spawn Top_Striker</tt> and <tt>ai2_spawn Top_Comguy</tt>. These two commands tell the game to create 2 characters: Top_Striker, and Top_Comguy.

Since that these characters do not spawn in the room, they must be teleported there. Using the <tt>chr_teleport</tt> command used earlier to teleport yourself, modify it to teleport the 2 AI using their names instead of "0". Teleport them to the flags "7008" and "7009" respectively. Refer to the example above or the list of function calls above to write this in.

It should now look like this :

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
ai2_spawn Top_Striker 
ai2_spawn Top_Comguy 
chr_teleport Top_Striker 7008 
chr_teleport Top_Comguy 7009 
}</tt>

This script will now teleport you into the final training room and face you off against 2 Strikers.

This fight too easy? In the next section, we will learn how to spice up the fight, and let you develop your own script.

----

== Part 6: Customization==

Here, you will be able to split off and customize your script.
Each subsection will represent a way to customize the above script.

===Weapons and Powerups===
These are the easiest things to add into a battle.

Weapons can be spawned on the ground or given to characters.

====Giving Characters Weapons====

Giving characters weapons is very easy. Simply use the command <tt>chr_giveweapon</tt> to give a character a weapon.

[[OSL:Inventory|Here]] are the list of the weapon codes. For the purpose of this example, we will use <tt>w3_phr</tt>, the plasma rifle. This command will give the two strikers plasma rifles.

Add the commands <tt>chr_giveweapon Top_Striker w3_phr</tt> and <tt>chr_giveweapon Top_Comguy w3_phr</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute.

====Spawning Weapons on the ground====

Spawning weapons is simple. Use the command <tt>weapon_spawn</tt> to spawn a weapon.

Add the commands <tt>weapon_spawn w3_phr 7008</tt> and <tt>weapon_spawn w3_phr 7009</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will spawn 2 plasma rifles, one under each striker's feet. AI will automatically pick up weapons with ammo or empty weapons they have ammo for.

====Giving Characters Powerups====

Giving characters powerups is much like giving characters weapons. Use the command <tt>chr_givepowerup</tt> to give a character a powerup.

The powerups you can give a character are :
* shield : Gives a force shield
* invis : Gives a phase cloak
* ammo : Gives a ballistic ammo
* cell : Gives an energy cell.

For the purpose of this example, we will give the characters invisibilities.

Add the commands <tt>chr_givepowerup Top_Striker invis -1</tt> and <tt>chr_givepowerup Top_Comguy invis -1</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will make the strikers permanently invisible. To make then visible after 30 seconds, erase "-1".

====Spawning Powerups on the Ground====

Spawning powerups are simple. Use the command <tt>powerup_spawn</tt> to spawn a powerup.

Add the commands <tt>powerup_spawn invis 7008</tt> and <tt>powerup_spawn invis 7009</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will spawn 2 phase cloaks beneath the striker's feet. Since AI will not pick up powerups, this is for you only.

===Extra Characters===

Addubg extra characters to the script is easy. Just follow the steps for adding the first AI and follow the procedure, look for AI names [[OSL: AI names|Here]].

====Adding Enemies====

Look at the chart for what teams the AI are on. Most of the time, adding enemies simply involve spawning and teleporting the AI. As long as the team in "Syndicate", it will be an enemy. If you want to add an emeny from an allied team, use the <tt>chr_changeteam</tt> command to changet their team to "Syndicate" like this:

<tt>chr_changeteam griffin Syndicate</tt>

====Adding Allies====

Look at the chart for what teams the AI are on. As long as the team is "TCTF" or "Konoko", it will be an ally for you in this script. If you want to add an ally from the enemy team, use the <tt>chr_changeteam</tt> command to changet their team to "TCTF" or "Konoko" like this:

<tt>chr_changeteam WH_Striker_D TCTF</tt>

===Overpower===

Use the <tt>chr_set_health</tt> command to set a character's health. Note that each character has a base health that may not be the same. For example, konoko's base health is 200, while a brown striker's is only 50. Keep this in mind when setting character's health. Setting it over their base health will send them into overpower - like using a hypo at full health. The health will drain at 1 every second even for AI. This example sets konoko's health to 400 - overpower.

<tt>chr_set_health 0 400</tt>

This following example shows everything listed above added.

<tt>func void main(void) 
{ 
 
chr_teleport 0 7010 
powerup_spawn hypo 7010 
 
ai2_spawn Top_Striker 
ai2_spawn Top_Comguy 
 
chr_teleport Top_Striker 7008 
chr_teleport Top_Comguy 7009 
 
chr_givepowerup Top_Striker invis -1 
chr_givepowerup Top_Comguy invis -1 
powerup_spawn invis 7007 
powerup_spawn invis 7009 
 
chr_giveweapon Top_Striker w7_scc 
chr_giveweapon Top_Comguy w3_phr 
chr_givepowerup Top_Striker ammo 15 
chr_givepowerup Top_Comguy cell 30 
 
weapon_spawn w2_sap 7045 
powerup_spawn ammo 7008 
 
ai2_spawn OutroTCTF01 
chr_teleport OutroTCTF01 7007 
 
ai2_spawn WH_Thug_A 
chr_changeteam WH_Thug_A TCTF 
chr_teleport WH_Thug_A 7007 
 
ai2_spawn griffin 
chr_changeteam griffin Syndicate 
chr_teleport griffin 7008 
chr_set_health griffin 3900 
}</tt>

----

== Part 7: Delay ==

<tt>sleep</tt> 
<tt>chr_wait_health</tt>

To wait for some time before executing a command, use <tt>sleep</tt>. To wait for approx 5 seconds before spawning an extra drone, go like this:

<tt>sleep 300 
ai2_spawn dum_train_block 
chr_teleport dum_train_block 7010 
</tt>

To wait for a striker to die and then spawn some drones, go like this:

<tt>chr_wait_health Top_Striker 0 
ai2_spawn dum_train_block 
chr_teleport dum_train_block 7010 </tt>

- Your_Mom

Oni (folder)/GameDataFolder/IGMD/power

2005-11-18T03:19:04Z

Your Mom: /* Available mods */

==Level logic for Chapter 7:A FRIEND IN NEED==
aka '''Atmospheric Conversion Center (exterior)'''
===Associated binaries===
*level9_Final.dat
*level9_Final.raw
===Original contents===
*[http://geyser.oni2.net/OSL/IGMD/power/particle_scripts.bsl particle_scripts.bsl]
*[http://geyser.oni2.net/OSL/IGMD/power/power_cutscene.bsl power_cutscene.bsl]
*[http://geyser.oni2.net/OSL/IGMD/power/power_main.bsl power_main.bsl]
*[http://geyser.oni2.net/OSL/IGMD/power/power_objectives.bsl power_objectives.bsl]
*[http://geyser.oni2.net/OSL/IGMD/power/power_spawn.bsl power_spawn.bsl]

==="Overcommented" version (not online yet)===
*particle_scripts.bsl
*power_cutscene.bsl
*power_main.bsl
*power_objectives.bsl
*power_spawn.bsl
===Rewritten version (not online yet)===
*different filenames...

==Available mods==

[http://your_mom.oni2.net/Downloads/My%20Other%20Scripts/Power%20New%20Ending.zip Save Point Six]

==Related issues==

BSL:Inventory management

2005-11-17T03:07:20Z

Your Mom: /* Weapon Codes */

== Weapon Codes ==

Campbell Equalizer - w1_tap 
SMG Black Adder - w2_sap 
Plasma Rifle - w3_phr 
Phase Stream Projector - w4_psm 
Superball Gun - w5_sbg 
Van De Graff Pistol - w6_vdg 
Scram Cannon - v7_scc 
Mercury Bow - w8_mbo 
Screaming Cannon - w9_scr 
 
Mukade's Fireworks Ring - w10_sni 
Wave Motion Cannon - w11_ba1 
 
'''Other Unused Weapons''' 
w0_sec 
w12_ba2 
w13_muro 
w14_muro

BSL:Inventory management

2005-11-17T03:06:52Z

Your Mom:

== Weapon Codes ==

TCTF Autopistol - w1_tap 
SMG Black Adder - w2_sap 
Plasma Rifle - w3_phr 
Phase Stream Projector - w4_psm 
Superball Gun - w5_sbg 
Van De Graff Pistol - w6_vdg 
Scram Cannon - v7_scc 
Mercury Bow - w8_mbo 
Screaming Cannon - w9_scr 
 
Mukade's Fireworks Ring - w10_sni 
Wave Motion Cannon - w11_ba1 
 
'''Other Unused Weapons''' 
w0_sec 
w12_ba2 
w13_muro 
w14_muro

BSL:Tutorial/Scratch

2005-11-17T01:52:00Z

Your Mom: /* Overpower */

This page is a short tutorial on how to get started on simple scripts for those who have had no experience with scripting before.
It will teach you, step by step, how to write a simple script. By the end of this tutorial, you will be able to move on to more advanced scripts.

----

== Part 1 : Knowing your formats ==

The game will accept 2 types of syntax for scripts, and they are based on different styles of writing. Choose the one that suits you best.

The types are :

Shell-Style:
This is compiled much like some System-Shells. It is written in a "one-function-call-a-line" format, and is the easiest to begin with if you have had no coding experience, as the code is neatly displayed line after line. The downside of this it, that once you get into more complex scripts or scripts with many function calls, the file becomes very hard to read and very large.

Example: [[Shell-Style]]

C-Style:
This is compiled much like the popular coding style C. The syntax can be placed into multiple-function lines and functions are divided by a ''';''' . In advanced scripts, this style will allow you to condense your script and the parts will be easier to read/debug. It also allows you to utilize some of the more advanced features easily. The problem with this is, that starting off, it is harder to write if you have had no previous experience with coding.

Example: [[C-Style]]

For the purpose of this article, we will use Shell-Style syntax for simplicity.

----

== Part 2: Starting Off ==

Now, I suggest reading the original script files to get a basic idea for how scripts are laid out. This will allow us to jump-start a bit.

Open up your IMGD and look for the following folder: EnvWarehouse.
Open it up, and we'll take a look at how it it laid out. There should be several files in here. Open using NOTEPAD, the one titled '''warehouse_main.bsl'''. It should look like this:

<tt>
func void main(void) 
{ 
env_show 2010 0 
gl_fog_blue=.15 
gl_fog_red=.15 
gl_fog_green=.15 
gl_fog_start=.99 
gs_farclipplane_set 5000 
obj_create 20 20 
level_start 
 
}</tt>

This is an example of a '''main''' file. It contains the information of how the level starts.

Ignore the contents of the script for now, and notice that the contents of the function <tt>main</tt> are enclosed by a set of brackets ('''{''' and '''}''').

All functions must be enclosed in this set of brackets or it will not be executed.

Close the file, and rename the folder "EnvWarehouse" "EnvWarehouse_original". Then, create a folder called "EnvWarehouse" and create a script file inside and name it "Tutorial". We will be using this file to show various examples of scripts and finally, write a small script of your own.

----

== Part 3: Basic Commands ==

This is just a small section explaining the commands that will be used in this tutorial. For a complete list of commands, see [http://www.fh-eberswalde.de/user/dkriesch/onistuff/commands.htm Ssg's Site] for more information.

ai2_spawn (name) - creates and starts an AI from a character object 
chr_teleport (name) (flag) - teleports a character to a flag 
chr_givepowerup (name) (powerup) (amount) - gives a character a powerup 
.
.
.

----

== Part 4: First Script ==

This section will teach you how to write a very basic script (fighting script). It will start you off in the Final Training Room, where you practiced firing weapons in the original game. With this script, the room will appear very empty.

Let's open up the "Tutorial.bsl" file and start writing the script.

First, declare it the "main" portion of the script by typing "<tt>func void main(void)</tt> at the very beginning of the file. This tells the game which function it is. The "main" function is the function that the game looks at first to determine what is to be executed.

Below that line, type '''{'''. This tells the game that the function has started.

Add a space, and then type <tt>chr_teleport 0 7010</tt>. This function teleports Konoko (her id is always 0) to the flag 7010. It is located in the final training room.

Finish the function "main" by typing '''}''' on the next line.

It should look like this:

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
}</tt>

Save the file, load up Oni, and click "New Game". You should be standing in the center of the final combat training room.

You are now on your way!

----

== Part 5: Adding NPCs (AI) ==

Before we begin, notice that there are two types of AI. AI created from character objects, and AI created from memory. AI created from character objects are created by the function call <tt>ai2_spawn (name)</tt>, where (name) is the name of the AI. AI created from memory are created by the function call <tt>chr_create (ai_number) start,</tt>. These AI do not have combat logic, and thus will not attack you physically but can still use weapons.

Now, we are going to add 2 enemy AI to our script that we wrote in the last section. Open it up, and lets add some enemies for Konoko to fight.

To recap, it should look like this :

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
}</tt>

After the function call <tt>chr_teleport 0 7010</tt>, add the following 2 commands on separate lines: <tt>ai2_spawn Top_Striker</tt> and <tt>ai2_spawn Top_Comguy</tt>. These two commands tell the game to create 2 characters: Top_Striker, and Top_Comguy.

Since that these characters do not spawn in the room, they must be teleported there. Using the <tt>chr_teleport</tt> command used earlier to teleport yourself, modify it to teleport the 2 AI using their names instead of "0". Teleport them to the flags "7008" and "7009" respectively. Refer to the example above or the list of function calls above to write this in.

It should now look like this :

<tt>func void main(void) 
{ 
chr_teleport 0 7010 
ai2_spawn Top_Striker 
ai2_spawn Top_Comguy 
chr_teleport Top_Striker 7008 
chr_teleport Top_Comguy 7009 
}</tt>

This script will now teleport you into the final training room and face you off against 2 Strikers.

This fight too easy? In the next section, we will learn how to spice up the fight, and let you develop your own script.

----

== Part 6: Customization==

Here, you will be able to split off and customize your script.
Each subsection will represent a way to customize the above script.

===Weapons and Powerups===
These are the easiest things to add into a battle.

Weapons can be spawned on the ground or given to characters.

====Giving Characters Weapons====

Giving characters weapons is very easy. Simply use the command <tt>chr_giveweapon</tt> to give a character a weapon.

[[OSL: Weapon Codes|Here]] are the list of the weapon codes. For the purpose of this example, we will use <tt>w3_phr</tt>, the plasma rifle. This command will give the two strikers plasma rifles.

Add the commands <tt>chr_giveweapon Top_Striker w3_phr</tt> and <tt>chr_giveweapon Top_Comguy w3_phr</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute.

====Spawning Weapons on the ground====

Spawning weapons is simple. Use the command <tt>weapon_spawn</tt> to spawn a weapon.

Add the commands <tt>weapon_spawn w3_phr 7008</tt> and <tt>weapon_spawn w3_phr 7009</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will spawn 2 plasma rifles, one under each striker's feet. AI will automatically pick up weapons with ammo or empty weapons they have ammo for.

====Giving Characters Powerups====

Giving characters powerups is much like giving characters weapons. Use the command <tt>chr_givepowerup</tt> to give a character a powerup.

The powerups you can give a character are :
* shield : Gives a force shield
* invis : Gives a phase cloak
* ammo : Gives a ballistic ammo
* cell : Gives an energy cell.

For the purpose of this example, we will give the characters invisibilities.

Add the commands <tt>chr_givepowerup Top_Striker invis -1</tt> and <tt>chr_givepowerup Top_Comguy invis -1</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will make the strikers permanently invisible. To make then visible after 30 seconds, erase "-1".

====Spawning Powerups on the Ground====

Spawning powerups are simple. Use the command <tt>powerup_spawn</tt> to spawn a powerup.

Add the commands <tt>powerup_spawn invis 7008</tt> and <tt>powerup_spawn invis 7009</tt> on separate lines beneath what you have already. Be sure to add it ''BEFORE'' the '''}''' or it will not execute. This command will spawn 2 phase cloaks beneath the striker's feet. Since AI will not pick up powerups, this is for you only.

===Extra Characters===

Addubg extra characters to the script is easy. Just follow the steps for adding the first AI and follow the procedure, look for AI names [[OSL: AI names|Here]].

====Adding Enemies====

Look at the chart for what teams the AI are on. Most of the time, adding enemies simply involve spawning and teleporting the AI. As long as the team in "Syndicate", it will be an enemy. If you want to add an emeny from an allied team, use the <tt>chr_changeteam</tt> command to changet their team to "Syndicate" like this:

<tt>chr_changeteam griffin Syndicate</tt>

====Adding Allies====

Look at the chart for what teams the AI are on. As long as the team is "TCTF" or "Konoko", it will be an ally for you in this script. If you want to add an ally from the enemy team, use the <tt>chr_changeteam</tt> command to changet their team to "TCTF" or "Konoko" like this:

<tt>chr_changeteam WH_Striker_D TCTF</tt>

===Overpower===

Use the <tt>chr_set_health</tt> command to set a character's health. Note that each character has a base health that may not be the same. For example, konoko's base health is 200, while a brown striker's is only 50. Keep this in mind when setting character's health. Setting it over their base health will send them into overpower - like using a hypo at full health. The health will drain at 1 every second even for AI. This example sets konoko's health to 400 - overpower.

<tt>chr_set_health 0 400</tt>

This following example shows everything listed above added.

<tt>func void main(void) 
{ 
 
chr_teleport 0 7010 
powerup_spawn hypo 7010 
 
ai2_spawn Top_Striker 
ai2_spawn Top_Comguy 
 
chr_teleport Top_Striker 7008 
chr_teleport Top_Comguy 7009 
 
chr_givepowerup Top_Striker invis -1 
chr_givepowerup Top_Comguy invis -1 
powerup_spawn invis 7007 
powerup_spawn invis 7009 
 
chr_giveweapon Top_Striker w7_scc 
chr_giveweapon Top_Comguy w3_phr 
chr_givepowerup Top_Striker ammo 15 
chr_givepowerup Top_Comguy cell 30 
 
weapon_spawn w2_sap 7045 
powerup_spawn ammo 7008 
 
ai2_spawn OutroTCTF01 
chr_teleport OutroTCTF01 7007 
 
ai2_spawn WH_Thug_A 
chr_changeteam WH_Thug_A TCTF 
chr_teleport WH_Thug_A 7007 
 >
ai2_spawn griffin 
chr_changeteam griffin Syndicate 
chr_teleport griffin 7008 
chr_set_health griffin 3900 
}</tt>

- Your_Mom