Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Ares and Super Weapons
#1
Hello all!

"Begun, the Clone War has."
– Yoda

I just committed a new branch, ft-superweapons, and you might want to take a look at it. It groups many features from the tracker, but the most notable one should be:
It is now possible to create multiple super weapons of the same action.

You can create up to two superweapons of the same action. And they will both use the global Rules settings. The AI will not use them right now and there are several known crashes. This entire paragraph is a joke. Ignore it. Big Grin 2

If you are an Ares tester, have a look at that branch and at least skim the manual. There are too many new tags to name them here. Be aware of the changes. Not all tags from 0.1 exist any more. Further down below is a migration guide. Essentially, just find and replace actions needed.

The most important thing: There is still time for feedback. Nothing is set in stone and there are several improvements yet to come. Post here what you like or don't like. I can't imagine we'll ignore your comments Tongue.

The unmodded super weapons should work as always. If you encounter crashes of inconsistencies of any kind, file a bug report or post here, respectively.

Happy modding!

[Image: t_SW_YuriStorm.png]
[Image: t_SW_FullBaseIronCurtain.png]

Some features:
  • No cryptic AI Targeting Mode values.
    Ares uses names like LightningStorm, ParaDrop or GeneticMutator instead of meaningless numbers which change if you reorder the SuperWeaponType list.

  • New targeting modes.
    Offensive shoots like the Lightning Storm, but doesn't wait if a storm is active. Stealth targets cloaked units only.

  • Land and Water firing support.
    You define what the SW can fired upon. If you want the Sonar Pulse to fire on land cells too, you can do that quite easily.

  • (Mostly) unlimited ranges.
    Except for the nuke explosion, every ranged super weapons support unlimited range. And you can define circular and rectangular areas.

  • Auto-Firing with targeting mode instead of firing to edges.
    Why should your super weapons auto fire on the edges? Wouldn't that be stupid? Why should one want to do that?

  • Messages support.
    Whenever your super weapon is launched, you can print messages like the Lightning Storm does.

  • Customizable icon overlay texts.
    Whatever text should be on the SW cameo, you can set it with Ares. Launch instead of Ready? Offline instead of On Hold?

  • Deferred explosion on every projectile.
    Only the nuke could have an animation, deferring the actual hit. Now, every warhead can have that.

  • Paradrop plane count and contents fully customizable.
    Every side and every country can have multiple planes with arbitrary units dropping out of them.

  • Ranged or full-map Sonar Pulse.
    Just like the Sonar Pulse from Red Alert. You click the cameo and every cloaked unit on the map emerges. Of course, you can still have the ranged one.

  • Lightning Rods.
    Basic support for Lightning Rods to attract deadly clouds and even reduce the damage caused by lightning – unless you tell your Lightning Storm SW to ignore them.

  • Dominator Deferment.
    The Psychic Dominator always strikes out of nowhere. Now it can be deferred like the Lightning Storm.

  • Animation visibility.
    You define whether the super weapon animation is visible to your team mates or the enemy. For example, the Chronoshift source animation is now visible to your allies by default, too.

  • Disallow units to be Chronoshifted.
    The Chronosphere ignored Warpable=no. With a new tag you can tell it to ignore units that are too large or too powerful to be chronoshifted.

  • Buildings can be Chronoshifted.
    Deployed vehicles can be chronshifted just like units. But all other buildings can be chronoshifted, too. (Default is off, naturally.)

  • Many Hardcoded Values Customizable.
    Lightning Storm debris, Genetic Mutator damage, Psychic Dominator permanent mind control ring anim and many more.

  • Some Customizable Values Hardcoded.
    PreClick, PostClick and PreDependent are obsolete now, replaced by SW.PostDependent.

Not yet working (list not complete):
  • AI doesn't use the Chronosphere correctly.
  • AI doesn't use the Iron Curtain correctly.
  • Several SWs still need some work.
  • Still some new SWs are missing.
  • SW.RequiresTarget needs some improvements.
  • Generic Warhead could be more versatile.
  • Unit Delivery doesn't support deferment.

Migration Guide
Just replace the following tags:
Code:
SW.Deliver --> Deliver.Types
SW.DeliverBuildups --> Deliver.Buildups
SonarPulse.Range --> SW.Range
GenericWarhead.Warhead --> SW.Warhead
GenericWarhead.Damage --> SW.Damage
Reply
#2
Epic.

Warpable=no is more about blocking the unit from being erased away, I'm not sure it should apply here.
Reply
#3
Thanks! The meaning of Warpable= hasn't changed. But you can order the Chronosphere to respect it (by default, it doesn't). There's also Chronoshift.Allow=no, for per-unit customization without touching Warpable=.
Reply
#4
didn't Warpable=y/n tell if the infantry in question was chronoshifted by the chronosphere, rather than killed? Since, IIRC, the chronosphere kills infantry by default.
Reply
#5
That's Teleporter=yes.
Reply
#6
(15.09.2010, 08:30:22)DCoder Wrote: Epic.
What more can I say? Awesome work!
[Image: jsfml.png]
Reply
#7
Woah. Keep up the great work!
Reply
#8
(15.09.2010, 15:26:14)AlexB Wrote: That's Teleporter=yes.

Oh yeah, that's right... thanks.

Anyways, I will definitely be testing this sometime. I want to help get this project moving again... this place has been so dead lately, it's depressing.

EDIT: Okay, something's not right here. I went ahead and tried to make a modified version of the regular original Lightning Storm superweapon (without cloning it!), and I used the following code:

Code:
[LightningStormSpecial]
UIName=Name:Storm
Name=Lightning Storm
IsPowered=true
RechargeVoice=00-I156
ChargingVoice=
ImpatientVoice=
SuspendVoice=
RechargeTime=10
Type=LightningStorm
Action=LightningStorm
SidebarImage=BOLTICON
ShowTimer=yes
DisableableFromShell=yes
AIDefendAgainst=yes
SW.Range=60
Lightning.Duration=-1
Lightning.HitDelay=0
Lightning.ScatterDelay=120
Lightning.PrintText=Name:Storm
LineMultiplier=2
Light.Enabled=no
Text.Hold=SWT:OnHold
Text.Ready=SWT:Launch
Text.Preparing=SWT:Preparing

And I observed absolutely no difference whatsoever in the LS's behavior. I read the manual pretty carefully and I made sure to get the ares.dll and manual from the ft-superweapons branch.

So what the heck is going on?
Reply
#9
Wow, That's awesome!
Good job!
Reply
#10
Launch Base is downloading a 1kb file for some reason, doesn't happen with other branches, any idea on what's going on?
[Image: MRMIdAS2k.jpg]
MRMIdAS: No longer allowed to criticise Westwood on PPM
Reply
#11
It's a 404 error page. This is something for Renegade to fix.

Lightning Storm issue: I'm working on that. Might be related to the svn problem. Can you check the file version? It should not be r817.
Reply
#12
I downloaded the ares.dll from the r821 page, but the Ares.dll version is 817.

EDIT: And for the record, I generally download my files straight off of svn.renegadeprojects.net or use TortoiseSVN, instead of getting the files from Launch Base.
Reply
#13
I got the SVN version and mine says it's 817 too.
[Image: MRMIdAS2k.jpg]
MRMIdAS: No longer allowed to criticise Westwood on PPM
Reply
#14
I uploaded r824. This one should work.
Reply
#15
Unit delivery works fine.

original Psychic reveal now reveals in a square for some reason, see pic.


Attached Files Thumbnail(s)
   
[Image: MRMIdAS2k.jpg]
MRMIdAS: No longer allowed to criticise Westwood on PPM
Reply




Users browsing this thread: 1 Guest(s)