some of you may know the siege 2004 mod. i won't explain how it works but i'll post a link later on.
there was a problem with the mod, you could only use UT2004 weapons. i have edited the script s you can only use BW weapons, but you still start with assaultrifle and shieldgun.
There will sure be some buggz, but I haven’t found them yet.

and no... i'm not good in scripting, it was only replacing some things in the script.
[br]File: [url=../../files/public/1165342559_172_FT0_taskforces.zip]1165342559_172_FT0_taskforces.zip[/url] replace the original file with this one in you ...\\UT2004\\Siege 2004\\System. directory.

siege download site
[br]File: [url=../../files/public/1165343228_172_FT21165_default.zip]1165343228_172_FT21165_default.zip[/url] and also replace this in \\UT2004\\Siege 2004\\System.

i bet this is something RS can play with, improve and add to BW.

Hey, this is pretty cool! I loved that mod but I don't like the original weapons. Thanks, MMM!

You should see if Bjossi would move this to the BW Mods section, though.

i'm not sure, because this needs work that the guys from Rune Storm need to do to make it work will. because this in not scripted to work properly with BW. so i think it will be better if it will stay here.

I think it probably would be best in the BW Mods section for now, as currently its not supported by RS, but it does let you use ballistic weapons. Also it'd be easier to find.

Thats just my opinion though.

We may need a “work in progressâ€Â

I love Seige, but making it work with BW. . .It could work, but it would definetly require at least ther permission, and probably the assistance of the Seige team.

Oh, yeah, someone probably oughta ask them... We might end up getting some advertisment for BW out of this.

there is only one developer of siege, and he did quit with it a long time ago. now he works in the defence alliance mod team.

Its a must its need to be moved ASAP.

Well I'm sure Sieges creator would be happy to see someone updateing his work,but then again some people are strange with that sorta thing

maybe if they help with siege they may be able to help the RS team with BW as well?

Siege?? info please

Link to main page up there,

It basically turns UT2004 a war strategy without adding (many) new interfaces and still keeps with the first person perspective.

Its actually pretty fun, despite there being a lack for actual bot support. Unlike regular warstrategies you don't 'create' your units, but you can get equipment and load up on armaments and even pick up a class or two (the classes don't do anything other than add a unique weapon to your armament, afaik).

make sure you add in the readme that it is a modification of the mod created by them, or they may get unhappy.

sounds pretty fun im about to try it, ive never heard of siege but it sounds cool from what X is saying. Yeah permission should be aquired before you get to far with this.

Now that's a cool thing indeed, nice work MMM. But I agree that you should ask for permission, modifying other's work without asking, even with the best intentions, is generally regarded as bad manners.

And now to a more detailed explanation of Siege for ShadowBlade:
It's basically a cross between normal UT2004 and a RTS game, played on CTF-Maps. The Flag gets replaced by a power core with an insame amount of health and every player spawns with only an Assault Rifle, a Shield Gun and a Construction device. With the Construction tool it is possible to create and upgrade buildings, like power generators to produce resources, armories to buy weapons in exchange for those resources and automated defense systems. It is also possible to buy special class-ability-items, like a commander's flag that gives every player within a certain radius a higher damage ratio, or a tool that regenerates health. The ultimate goal is of course to destroy the enemy power core, but since it has so much health, the best way to do that is the ultimate weapon, the Siege Nuke (which is basically a Redeemer, but with a great looking mushroom-explosion effect). It is constructed like a building and very vulnerable, but when upgraded to level 3 it is capable to destroy a power core with one hit. If you decide to eqip it the building is destroyed and you carry the nuke around like a usual Redeemer, unfortunately it is also as vulnerable as the Redeemer there fore a sucicidal attack is recommended (which of course bears the risk that the nemy kills you, grabs the weapon from your dead hands and nukes you instead).
One of the best things of Siege are the innovative special weapons. Take the Bomber for instance: It drops higly damaging projectiles right beneath your feet, so you'd better be in the air if don't want to kill yourself. In the air? Yes, the weapon also gives the player an unlimited amount of mid-air jumps. But the coolest weapons were removed since Siege 2003, but they are still available via cheats:
"summon taskforces.TFNKPickup" gives you the old nuke device, the nuclear grenade launcher. It can fire only three shots, no matter if you use fire or altfire. Fire is a timed grenade. The five-seconds-timer activates when the grenade touches the ground. The grenade also makes a loud beeping noise, so the enemy team can find and destroy it before the timer runs out. If they don't make it in time, well... It is a nuke, what do you think? Altfire is really interesting, in this mode the grenade explodes upon tounching the ground and contaminates a huge area with highly damaging radiation, turning whole parts of the map into a no-go-area for 30 seconds or so.
"summon taskforces.TFWBPickup" gives you the WarpBlade. Primary fire is a deadly energy blade that kills everything at close range. Alt-fire allows you to fly for a short time, but you will be more vulnerable during that time.
"summon taskforces.TFSCPickup" gives you the Siege Cannon. Primary fire shoots a really slow energy projectile without collision, so you can shoot through walls and meshes. Altfire detonates the projectile. It is so slow, you can basically shoot at the enemy base, run there and wait for the projectile to arrive, then detonate it when it has reached the right spot.

I recommend everyone who hasn't tired it out yet to give it a go, it is indeed a really cool mod.

important newz: BUGZ!!!
my modified version doesn't work well, some emitters and sounds don't work.

Really? Hmm... I'll have to check that out, I don't remember any, but I was probably too excited running around with BW weapons to notice.

does sounds pretty cool.. thanks Doc

does anyone know how to fix it
i think i'm going crazy !!!

welcom to programing

come on, im not a coder.
the only thing that i can is editing other codes.
i can't create a single one by my self.

it is always:

'something' extends 'something'

Defaultproperties
{
'something'
}

or something like changing names.

This is what i edited in the script:

From

defaultproperties
{
ArmoryWeapon(0)="XWeapons.Shieldgun"
ArmoryWeapon(1)="XWeapons.Assaultrifle"
ArmoryWeapon(2)="XWeapons.biorifle"
ArmoryWeapon(3)="XWeapons.shockrifle"
ArmoryWeapon(4)="XWeapons.linkgun"
ArmoryWeapon(5)="XWeapons.minigun"
ArmoryWeapon(6)="XWeapons.flakcannon"
ArmoryWeapon(7)="XWeapons.rocketlauncher"
ArmoryWeapon(8)="XWeapons.sniperrifle"
ArmoryWeapon(9)="Onslaught.ONSMinelayer"
ArmoryWeapon(10)="Onslaught.ONSGrenadeLauncher"
ArmoryWeapon(11)="UTClassic.ClassicSniperrifle"
ArmoryWeapon(12)="OnslaughtFull.ONSPainter"
ArmoryWeapon(13)="Taskforces.TFPainter"
ArmoryWeapon(14)="Taskforces.TFRedeemer"
ArmoryWOption(0)="30 Shieldgun"
ArmoryWOption(1)="30 Assaultrifle"
ArmoryWOption(2)="50 Biorifle"
ArmoryWOption(3)="50 Schockrifle"
ArmoryWOption(4)="50 Linkgun"
ArmoryWOption(5)="50 Minigun"
ArmoryWOption(6)="50 Flakcannon"
ArmoryWOption(7)="50 Rocketlauncher"
ArmoryWOption(8)="50 Lightninggun"
ArmoryWOption(9)="50 Minelayer"
ArmoryWOption(10)="50 Grenadelauncher"
ArmoryWOption(11)="50 SniperRifle"
ArmoryWOption(12)="300 TargetPainter"
ArmoryWOption(13)="400 IonPainter"
ArmoryWOption(14)="500 Redeemer"

To

defaultproperties
{
ArmoryWeapon(0)="ballistic.M806Pistol"
ArmoryWeapon(1)="ballistic.A42SkrithPistol"
ArmoryWeapon(2)="ballistic.XK2SubMachinegun"
ArmoryWeapon(3)="ballistic.MRT6Shotgun"
ArmoryWeapon(4)="ballistic.M763Shotgun"
ArmoryWeapon(5)="ballistic.M290Shotgun"
ArmoryWeapon(6)="ballistic.A73SkrithRifle"
ArmoryWeapon(7)="ballistic.M50AssaultRifle"
ArmoryWeapon(8)="ballistic.M353Machinegun"
ArmoryWeapon(9)="ballistic.M925Machinegun"
ArmoryWeapon(10)="ballistic.R78Rifle"
ArmoryWeapon(11)="ballistic.M75Railgun"
ArmoryWeapon(12)="ballistic.G5Bazooka"
ArmoryWeapon(13)="ballistic.NRP57Grenade"
ArmoryWeapon(14)="ballistic.FP7Grenade"
ArmoryWeapon(15)="ballistic.FP9Explosive"
ArmoryWeapon(16)="ballistic.BX5Mine"
ArmoryWOption(0)="30 M906 Pistol"
ArmoryWOption(1)="30 A42 Skith Pistol"
ArmoryWOption(2)="30 XK2 Submachinegun"
ArmoryWOption(3)="30 MRT6 Shotgun"
ArmoryWOption(4)="50 M763 Shotgun"
ArmoryWOption(5)="80 M290 Double Barrel Shotgun"
ArmoryWOption(6)="50 A73 SkrithRifle"
ArmoryWOption(7)="50 M50 AssaultRifle"
ArmoryWOption(8)="50 M353 Machinegun"
ArmoryWOption(9)="70 M925 Machinegun"
ArmoryWOption(10)="50 R78 Sniper Rifle"
ArmoryWOption(11)="50 M75 Railgun"
ArmoryWOption(12)="200 G5 RPG"
ArmoryWOption(13)="50 NRP57 Grenade"
ArmoryWOption(14)="50 FP7 Incendiary Grenade"
ArmoryWOption(15)="50 FP9 Explosive"
ArmoryWOption(16)="50 BX5 Mine"

Judging by what the problem is, that doesn't sound related to the changes you made...

Something you might want to look for is perhaps maybe you accidently put something extra in the code or deleted something. I'll check it out sometime if I get some time.

no, it's a problem with putting the .UC files back to a .U file.
the strange thing is, if you extract a .U file to .UC files and then back, things can get messed up.

Many things can cause corruption when compiling code, but I think it's not possible to know the exact reason when that happens each time.

is there a way to change the defaultproperties in the .U file without extracting it to .UC files first?

yes.. right click on the class in the actor browser, and click Default Properties

Imo, the best way to modify Siege would be to make the defaultproperties section ini-based, so they aren't hard-coded. That way every custom weapon can easily be implemented and everyone can implement his personal favourites. Of course this requires the original source code, because reverse-engineering messes things up, as you already said. I really recommend to mail the original creator of Siege. Ask politely and tell him precisely what you want to change, I guess he should agree then.

thanks Doc Shock, i'll try it.