Scripting updates

zwzsg · Post by **zwzsg** » 03 Sep 2005, 13:19

In OTA there was HitByWeapon(x,z), but sadly the arguments were normalised to 400, so it could be used to get only the angle, not the radius.

So yes, a OnHit(piecename,xz,y,heading,pitch) function would be nice.

Also, would it be possible for script variable not be be limited to 32bits signed integers? I'd like to be able to use long floats, and character strings. With all the accompagning string function. It would open lots of possibilies, things like: if(get UNIT_TYPE(unit_id)=="ARMCOM")

Guessmyname · Post by **Guessmyname** » 03 Sep 2005, 13:30

I'm working on a set of test-units for this. These do of course assume that we will use the syntax mentioned...

Gnomre · Post by **Gnomre** » 03 Sep 2005, 13:31

A note: In spring, you'd just need to set "CanMove" to 0 in the FBI to strip away movement abilities from a unit. You wouldn't need to mess with TED classes or anything :)

Guessmyname · Post by **Guessmyname** » 03 Sep 2005, 14:04

Oh good...

"Component" Tower (upgrade thingy)

GrOuNd_ZeRo · Post by **GrOuNd_ZeRo** » 03 Sep 2005, 21:10

Particle support would be nice, so if infantry get hit they bleed for example, or if a tank get hit there are sparks flying, that'd be cool.

Min3mat · Post by **Min3mat** » 03 Sep 2005, 21:46

rocket tower looks like it was rinsed from earth 2150 don't be breaking copyright yahear! ;P

Post by **Fnordia** » 03 Sep 2005, 23:46

Setting values of arbitrary fbi-tags might be something for the future, but not now. It would be powerful, but it is not simple to implement. It would among other things require a rewrite of most of the parsing since we don't just save the propertynames as strings and use their values, there's a lot of parsing done at loadtime. It would also require new script compilers. A better idea for now would probably be to expose some of the more useful values to change through the existing get/set interface.

In general, I don't think we will do any changes which would require updating the syntax of the language and require a new compiler at this time, it will have to wait until it's decided if we should switch to a new scripting language and if so which one for the updated unit format.

Supporting some of the ta:k stuff could be done though I guess, at least if I can find some documentation on what is changed. :)

PauloMorfeo · Post by **PauloMorfeo** » 07 Sep 2005, 09:20

I'm not sure if this is part of scripting or of the model...

http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2149
The possibility for buildings to be built either in land, under water and water surface.

That way, we would only need one metal extractor for land and for under water. Only one radar for land and for water surface. Only one hovercraft plant. Et Cetera.

Maybe they could be made to cost extra if built in water and have, for example, sunking animations if on water.

Torrasque · Post by **Torrasque** » 07 Sep 2005, 13:42

PauloMorfeo wrote:I'm not sure if this is part of scripting or of the model...

http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2149
The possibility for buildings to be built either in land, under water and water surface.

That way, we would only need one metal extractor for land and for under water. Only one radar for land and for water surface. Only one hovercraft plant. Et Cetera.

Maybe they could be made to cost extra if built in water and have, for example, sunking animations if on water.

I had the same idea, building having the same buildpics, and when you place them, the engine will determine wich one to place.

But..how knowing if you want an unterwater metal convertisser, or one on the top of water?

zwzsg · Post by **zwzsg** » 07 Sep 2005, 14:15

In TA the same building can be made buildeable underwater and on land. Land and floating wasn't possible however. Oh and in Spring too, I made building buildeable both underwater and on land without any problem. So don't ask for something that's already supported.

Torrasque · Post by **Torrasque** » 07 Sep 2005, 16:05

zwzsg wrote:In TA the same building can be made buildeable underwater and on land. Land and floating wasn't possible however. Oh and in Spring too, I made building buildeable both underwater and on land without any problem. So don't ask for something that's already supported.

Sorry for not being an unit maker.
And thus, even if it's supported, I ask about being used...good or bad idea?

PauloMorfeo · Post by **PauloMorfeo** » 08 Sep 2005, 15:48

Torrasque wrote:...
But..how knowing if you want an unterwater metal convertisser, or one on the top of water?

That wouldn't hapen. (at least not acording to what i said.)
For example, the metal extractor is always on the floor.
The metal maker, would have to check if it was on water or on land. On water it is on top of the water, too, but has that sunking animation, so the check.

zwzsg wrote:...
So don't ask for something that's already supported.

No? Why not? I most certainly do not know every single feature already existant and, so, i do not know if it is already there or not. Then i wouldn't ask for anothing at all.

PauloMorfeo · Post by **PauloMorfeo** » 08 Sep 2005, 15:48

I think that the units could have description for the diferent orders menus.
For example, there could be these 5 as a basic standard:
- Orders
- Factories
- Resources
- Defensive Structures
- General Structures
When shifting with the arrows, we would start at the orders menu and circle through them.

So we could add orders to the orders menus but have them organized.
We would also be able to create other menus like the menu "Alien Technology", "Research", "Spells" to suit our needs.

If something unclear, ask me to explain further.

Warlord Zsinj · Post by **Warlord Zsinj** » 08 Sep 2005, 16:24

I don't think zwzsg was trying to be rude; he isn't a native English speaker, and technically that was a direct translation of what (I think) he wants to say. I'm sure it'd be pretty hard to learn all the nuances of what to say and what not to say once you've learnt the basics of the language...

FLOZi · Post by **FLOZi** » 08 Sep 2005, 23:05

Information about a target unit, be it height or TEDClass, that way you can use a particular weapon against a particular type of unit more effectively. Also a way to prioritise what targets to attack first.

FLOZi · Post by **FLOZi** » 11 Sep 2005, 04:47

*bump*

Can't believe it but noone seems to have mentioned it, basic trig functions!

GrOuNd_ZeRo · Post by **GrOuNd_ZeRo** » 11 Sep 2005, 17:29

PauloMorfeo, you inspired me.

Maybe if you try to build a mex on water, spring will determine what you are trying and build an UW mex instead.

Perhaps the same can be done if you attempt to build a radar tower, it will build a floating one instead, the only problem here will be that there will have to be a seperate unit for every possibility I.E. wind gen for land, sea...

it might get confusing...

Another thing that is worth considdering is this:

This is more like PauloMorfeo's suggestion, when you build a windgen on water, the script knows the unit is being build on water and pontoons normally being hidden on the ground, will be drawn on water, so we only need an extra model inside the windgen model.

in this way we could easilly remove many unnecesary units such as the floating defenders and such.

as for mexes, we could do the same, the only problem I see is the build picture which will be a regular mex instead of the UW one.

Guessmyname · Post by **Guessmyname** » 11 Sep 2005, 22:25

The ability for units to know when and what they are transporting: OnTransporting(unitname), and to tell what they are being transported by: OnGetTransport(unitname). Very useful for WD when APCs need to have a gunner or infantry bloke loaded to fire its mounted machine gun, or where units can run out of ammo and have to load them selves into an ammo-dispencing unit / building to get more ammo.

Also, the ability to change how much energy / metal the unit is using / making, maybe something like this: energy = +10 or something

Post by **Tim Blokdijk** » 11 Sep 2005, 22:59

Suggestion:
Allow scripting (not hard coded) that can help a unit to think for itself.
Like planes returning to a air repair pad.
Unit's to collect ammo.
A stealth unit to avoid los detection.
A zombie unit to randomly walk over the map destroying whatever it finds.
A construction unit capable to construct a fully functional base on it's own.

Maybe code can be used from the AI subsystem?

Guessmyname · Post by **Guessmyname** » 11 Sep 2005, 23:14

Patrolling planes automatically reurn to air-repair pads when damaged anyway

Spring RTS Engine

Scripting updates