The War of Terrador: RIP

[Dragonchampion]

The Zederian ships

[Dragonchampion]

And the last 1

[Flameslash]

I say make them their own Factions with other Ships. Terrador Space Forces versus Zererian Navy.

[Dragonchampion]

That would make the game too complicated. Stick to KISS. Don't 4get, these will all be ships you can get from leveling up a fighter ONLY, making leveling the fighters up more important.

[huntermeca31]

I have play with your era and thing for balance(very cool the new unit ):

Repair satellite should be 7-4 or 6-5
T-09b destroyer should be 6-6 or 7-6
Raven was not very powerfull for a Level2. His power should be 8-3
Sniper was too powerfull. 14-2 or 10-3 should be better.

Continue this good era ( One of my favorite)

[Dragonchampion]

I compromised for the Destroyer; I put it to 12-5. Anyways, I would like to get rid of the poison effect of the Sniper line, but I can't think of any other anti-infantry effect. Any Ideas, guys?

[mnewton1]

How about an abilities called lodged. were the bullet gets lodged in the body and slows the unit until it is healed in a village of but a medic. But unlike slow it will continue until healed. what do you think? Better name needed though

[Dragonchampion]

I was thinking more like instant kill, as snipers sometimes get headshots. This wouldn't work against mechanical units, though.

Then again, maybe Bleeding? That way, the sniper could "wing" an enemy, and they would die of blood loss unless healed.

[mnewton1]

The bleeding idea would work fine. Also maybe your sniper should have a head shot were he only has 20% chance to hit but if it hits it is an instance kill.

[thespaceinvader]

Future snipers would probably have weapon which stand a good chance of doing catastrophic damage to vehicles as well - even today there are such rifles. They're too big to be easily man-portable in battle, but they do exist and they do a LOT of damage... A low CTH extremely high damage (or insta-kill) attack would be an interesting one, but I'd also give him a standard accuracy attack too, to give strategic options.

[Dragonchampion]

I never thought of that! I'm going to go investigate WML now to see if the instant kill is possible. I never even thought to add a second attack for those who don't want to use the instant-kill one!

[thespaceinvader]

If it's not directly (which it might well be), simply use an amount of damage that very few units will survive (100 would probably be enough, 1000 would be plenty...)

[Glass Pearl Player]

The instakill can be done in WML. The following code (which should work) creates a fake weapon special and a corresponding event. On attack, the special has a 1 in 5 chance for an instakill, AND he gets the corresponding experience. You might want to change this for balancing reasons. Hope this is helpful.

Spoiler:

Code: Select all

#define WEAPON_SPECIAL_HEADSHOT
   [head_shot]
      id=head_shot
      name= _ "head shot"
      name_inactive = _ "head shot"
      description = _ "Head Shot:
On attack, this unit has a one in five chance per hit to kill a non-mechanical target instantly."
      description_inactive = _  "Head Shot:
On attack, this unit has a one in five chance per hit to kill a non-mechanical target instantly."
   [/head_shot]
#enddef

#define EVENT_HEADSHOT
    [event]
        name=attacker_hits
        first_time_only=no
        [filter_attack]
             special=head_shot
        [/filter_attack]
        [filter_second]
            [not]
                race=mechanical
            [/not]
        [/filter_second]
        {RANDOM 0,0,0,0,1}
        [if]
            [variable]
                name=random
                equals=1
            [/variable]
            [then]
                #no need to actually subtract any value from second_unit.hitpoints. second_unit will be killed anyway.
                [unstore_unit]
                    variable=second_unit
                    text=$second_unit.hitpoints
                    {COLOR_HARM}
                [/unstore_unit]
                [kill]
                    x,y=$second_unit.x,$second_unit.y
                    animate=yes
                    fire_event=yes
                [/kill]
                # Balance question: should a unit delivering a headshot gain the kill experience or not? If not, remove this if tag and the unstore tag.
                [if]
                    [variable]
                        name=$second_unit.level
                        equals=0
                    [/variable]
                    # Gosh dang it to heck! Wasted a headshot on a level 0 unit.
                    [then]
                        {VARIABLE_OP unit.experience add 4}
                    [/then]
                    # subtract target level from experience, then add 8 times level to exp. 
                    [else]
                        {VARIABLE extra_exp $second_unit.level}
                        {VARIABLE_OP extra_exp multiply 7} # adding 8, taking away 1 we would get anyway.
                        {VARIABLE_OP unit.experience add $extra_exp}
                        {CLEAR_VARIABLE extra_exp}
                    [/else]
                [/if]
                [unstore_unit]
                    variable=unit
                [/unstore_unit]
            [/then]
        [/if]
    [/event]
#enddef

Note to developers: This WML code could be considerably shortened if

• WML had "subtract" in addition to "add"
• units had a "give experience on kill" and "give experience on combat" value to query.

One could then save 18 lines of code by replacing the if-tag with

Code: Select all

{VARIABLE_OP unit.experience add $second_unit.gives_exp_on_kill}
{VARIABLE_OP unit.experience subtract $second_unit.gives_exp_on_fight}

Or am I missing something obvious?

EDIT: However, can the AI handle such an ability? Can it be told to avoid these units? Giving it simply an insane damage value as previously suggested may be not so cool, but easier to work with. Maybe give it a unique damage type that infantry units do not resist (or have insanely negative resistance), but mechanical units resist extremely well.

[Dragonchampion]

So I just copy and paste the code above that is in the spoiler in my Abilities Section for it to work?

[Exasperation]

I would think it would be simpler to do something like this, and let the normal combat code handle the kill and exp:

Code: Select all

#define EVENT_HEADSHOT
    [event]
        name=attacker_hits
        first_time_only=no
        [filter_attack]
             special=head_shot
        [/filter_attack]
        [filter_second]
            [not]
                race=mechanical
            [/not]
        [/filter_second]
        {RANDOM 0,0,0,0,1}
        [if]
            [variable]
                name=random
                equals=1
            [/variable]
            [then]
				{VARIABLE second_unit.variables.damage_taken $second_unit.hitpoints}
				{VARIABLE second_unit.hitpoints 0}
                [unstore_unit]
                    variable=second_unit
                    text=$second_unit.variables.damage_taken
                    {COLOR_HARM}
                [/unstore_unit]
			[/then]
		[/if]
	[/event]
#enddef