User Screenshots!

Rate This File!

File Notes

The result of this endeavour is that most of the flaws of RPG_Beta6 are now taken care of;
The base is now smaller and more efficient, more tunels below it and the Keep now has
a new nuclear shelter. A new Airfield has been added to the mix, as well as the Lost Island
and the Control room makes a return. With Me[Ks]'s colossal , RPG_Beta6.2 will also feature
a high amount of scripted events. RPG_Beta6 started this trend with an elevator, in 6_2
we're stretching this even further. Switch Activated "Lockdown" Mode for the Air Base,
Ability to toggle the "Red Alert" mode, Even the ability to activate Halo itself!
Also new, is the ability to switch BSPs. Not like you've seen before, No. Host controled
and sync'ing! This means the host can decide "Alright, now it's night". And everyone
will be switched to night.


Also, the prowler is no longer landed in a valley. It's now up in the air, with a lifepod
in it's belly thus allowing you to make Ship RPs.


With all this and the numerous BSP changes, added to some new vehicles, RPG_Beta6.2
is intended to be much less streamlined than RPG_Beta6 was. You now have tons of new
plot possibilities and even the ability to make cross-maps RPs with Sanctuary_Final.




Suggested player: 1-16
Supported Gametypes: Slayer, CTF, KoTH, Oddball, Race


Vehicles: Pelican, Warthog, Trans Hog, Sparrowhawk, Lifepod, Firebomb-Longsword, Jets

Credits:

OpsY:BSP, Concept, Population, Some Tagging,
*Me_Ks Explodes*: All Scripting job, Tagging, Music, Insane debugging, Bungie programmers begaring and MUCH, MUCH more
Terrel: Hi-Res Biped
017: Sparrowhawk, Firebomb LS
Dhark Atlan: Some Ideas, Bunker Model
Kcaj: Concepts, Ideas
Gibbo: Original RPG_Beta concept
Matooba: Warthogs
MRp and RPC Clans: Beta Testing services


Script Essentials:

Here is the list of commands you can use to tweak the scripts. These are sometimes
more advanced commands that will give you options such as manually setting the delay
involved in Lockdown, trigger it manually and others akin. Mastering those will give
your server an edge over others.


By Me [KS]

*explodes*

Hello people. This is a rundown of all of the commands you can mess with in RPG_Beta6.2 as hosts or admins in order to customize some aspects of how the scripted features work.

I've layed out a pretty thorough explanation of each, but here are some things that you should know ahead of time:

- First, whenever there are brackes [ ] in a command in this list, that indicates a value that you are supposed to add in. If there aren't any brackets, that means there's nothing to change and changing anything may cause DIRE consequences. Well no not really, but you could mess something up. Unless you know what you're doing, don't mess with any value in these commands that isn't specified to be changed.

- Second, ALL of these are meant to work ONLY on server side. This means that if you are not hosting, you can't abuse the game with these commands, so don't get your hopes up. In fact, just to be safe, never use these if you are not hosting, as you may mess up something on your end. For the most part though, these won't do anything in that case.

Note: This does NOT apply if you are a server admin. While you are not yourself hosting, you are sending commands to the server through the Rcon command or through the chat text if you're using some server app, so you are properly using the commands.

- Third, ALL of these commands require devmode on in order to work. This is very important if you are running this map on a dedicated server, as any dedicated server without a server app running can't activate devmode. In order for admins to use these commands on your dedi server, you will need one of many dedi server apps that enable devmode.

For players hosting the map, all you need is any app for Halo CE that can turn devmode on while online, e.g. Alldev.

1. device_set_position alarm_control_1 1

- This will toggle Red Alert on or off. Using this command activates one of the control panels that players normally have to use to activate this.

2. device_set_position lock_control 1

- This will activate Lockdown mode. Using this command activates the control panel that players normally have to use to activate this.

3. device_set_position boom_control 1

- This will initiate Halo's activation. Using this command activates the control panel that players normally have to use to activate this. (copy-pasting is great)

4. set setting [#]

- This will change the environment of the map based on the value of '#'. This setting can ONLY be set on the server and won't do anything if used on client side (clients are any players who are not hosting, as in players who joined a game).

Valid # Values Are:
0 - Day (default)
1 - Rain
2 - Night

Examples:

set setting 0 - Day
set setting 1 - Rain
etc.

Note: Any other values for # will NOT do anything. Also, you will find that during the switch to Rain From Day there is a brief change to Night. This is normal and was needed in order for the switch to work properly.

5. set lock_timer (* 30 (* 60 [# of minutes]))
OR
set lock_timer (* 30 [# of seconds])

- This will change the amount of time that the doors stay closed while Lockdown is activated. It won't affect the time remaining for a current lockdown, only future ones. The default is 3 minutes.

Note: As you can see, you can use either of the commands above depending on whether you want to specify the time in minutes or seconds. You can't use decimal values, e.g. 1.5, 2.5, etc, being why I gave you both options. If you're feeling really OCD and want to specify time in fractions of a second, then you can do this instead:

set lock_timer [# of ticks]

1 tick is 1/30th of a second, so 30 ticks is 1 second. You'll have to do the math yourself, unlike the commands above =).

Examples:

set lock_timer (* 30 (* 60 3)) - 3 minutes
set lock_timer (* 30 3) - 3 seconds
set lock_timer 3 - 3 ticks, or 1/10th of a second
set lock_timer 0 - absolutely nothing

6. set boom_timer (* 30 (* 60 [# of minutes]))
OR
set boom_timer (* 30 [# of seconds])

- This will change the minimum delay between firings of Halo. It won't affect the time remaining for the current delay if it was recently fired, only future ones. The default is 5 minutes.

Note: As you can see, you can use either of the commands above depending on whether you want to specify the time in minutes or seconds. You can't use decimal values, e.g. 1.5, 2.5, etc, being why I gave you both options. If you're feeling really OCD and want to specify time in fractions of a second, then you can do this instead:

set boom_timer [# of ticks]

1 tick is 1/30th of a second, so 30 ticks is 1 second. You'll have to do the math yourself, unlike the commands above =).

Examples:

set boom_timer (* 30 (* 60 3)) - 3 minutes
set boom_timer (* 30 3) - 3 seconds
set boom_timer 3 - 3 ticks, or 1/10th of a second
set boom_timer 0 - absolutely nothing
(copy-paste eh?)