Scripting Engine Suggestions

[Aquarius]

Would it be possible to enable Pascal/Delphi string functions like LeftStr, RightStr and Trim??? Right now I can't use it in scripts.

[EnEsCe]

People may now request functions that would require the Soldat client to be changed.
(ie: spawn scenery at X,Y)

So start thinking! And don't suggest CreatePolygon or CreateScenery or CreateSound.

[Kavukamari]

is GetServerStat(IP: string; Port: integer; Stat:string); possible?

[EnEsCe]

Heh, no way. Server's don't communicate with each other

[Kavukamari]

function CopySound(SoundFile: string); (forces player to download a sound to be played)
function PlaySound(SoundFile: string); (plays a sound on Soldat)
function LoopSound(SoundFile: string; Time: integer); (Same as play sound, but loops sound for Time seconds, 0 = forever (until player leaves))
(at least it's not CreateSound('Waterfall.midi')

(aww, no GetServerStat, well, I tried)

[EnEsCe]

No. No sound related sh!t.

EDIT: New wordfilter sucks ass.

[spkka]

ah nice enesce. Did you thought about setplayerdeaths by the way?

[freestyler]

People may now request functions that would require the Soldat client to be changed.
(ie: spawn scenery at X,Y)

GetCursorXY(ID: byte; X, Y: single);
MoveCursor(ID: byte; newX, newY: single);
yay, shakin' crosshair

GetPlayerColor(ID: byte; Hair, Shirt, Pants, Flames: longint);
SetPlayerColor(ID: byte; Hair, Shirt, Pants, Flames: longint);

[Aquarius]

SpawnParticles( [ParticleImages], ParticlesNum, ParticlesTime, X, Y, MinVelocity, MaxVelocity, MinAngle, MaxAngle )

Spawns a number of random particles (the exact look of the spawned particles may differ a bit for each client)

[ParticleImages] -- Array holding all particle image names from Sparks-gfx folder which MAY be rendered, for example if ['lilblood.bmp', 'blood.bmp'] - each particle will use blood or lilblood image (randomized on client side).

ParticlesNum - Total number of particles which will be spawned.

ParticlesTime - How long the particles will live (when they disappear)

X, Y - the point where the particles are spawned

MinVelocity, MaxVelocity - the velocity of the particles would be random (randomized on client side) but within MinVelocity-MaxVelocity range.

MinAngle, MaxAngle - the starting movement angle of each particle would be random (randomized on client side) but within  MinAngle-MaxAngle range.


Date Posted: 08-10-2007, 15:40:26ChangePlayerName( PlayerID, NewName )

Date Posted: 08-10-2007, 15:49:13IsRegistered( PlayerID ) -- returns true if the player has a registered version of Soldat

[Toumaz]

GetCursorXY(ID: byte; X, Y: single);
GetPlayerColor(ID: byte; Hair, Shirt, Pants, Flames: longint);

Seconded, pretty please.

[EnEsCe]

I see no good reason for anything relating to the player's cursor, and what does flames have to do with a players colour, there is also no point in scripts knowing a players colour choices....

[Toumaz]

I see no good reason for anything relating to the player's cursor

Spawning objects at the position of the player's cursor, or to find out the direction between the player and cursor. Could be used for cheesy looking attacks in conjunction with CreateBullet; or to spawn stuff at the cursor position (shameless plug).

and what does flames have to do with a players colour, there is also no point in scripts knowing a players colour choices....

Think he means the player's jet flames, and there would be a use for it for more advanced statistic scripts. :/

[Aquarius]

I see no good reason for anything relating to the player's cursor, and what does flames have to do with a players colour, there is also no point in scripts knowing a players colour choices....

For example a script with classes, it could change your colours to white if you choose medic etc. This way player's class would be easily distinguishable. Not only colours but also hair/cap/chain style should be get/setable IMO. And flames shouldn't because it's for registered only.

[spkka]

ah nice enesce. Did you thought about setplayerdeaths by the way?

?  ^^

[freestyler]

I see no good reason for anything relating to the player's cursor, and what does flames have to do with a players colour, there is also no point in scripts knowing a players colour choices....

For example a script with classes, it could change your colours to white if you choose medic etc. This way player's class would be easily distinguishable. Not only colours but also hair/cap/chain style should be get/setable IMO. And flames shouldn't because it's for registered only.

Yeah I meant something like that. It would be cool to modify player's colors depending on class, k/d, level, idle-time or whatever you imagine.

[Kavukamari]

(shameless plug).

SPAWNER GUN!!!

(my sound idea was shameless and I apologise )

I think setting player colors might give errors, but would be fun to make purple team
and maybe make a custom respawn point for purple and orange, or maybe white, but it changes depending on player color...

Date Posted: October 08, 2007, 01:43:21 pmadd a CPUUseageLimit const in Server.ini and OverCPULimitDo const, so if the server script makes CPU useage go crazy, you can set what the Soldatserver should do

(shutdown: shut down soldatserver.exe; disable: disable script causing problem; ignore: ignore CPU useage spike and continue running server(Default))

(CPUUseageLimit=600
OverCPULimitDo=Disable

//on cpu spike from script, soldatserver will disable script)

[Avarax]

ForceWeaponRate(position: single)

affects the current state of this blue bar



And a definitive support for GetCursorXY and SpawnParticle here.

[DorkeyDear]

SetPlayerAmmo(Spot, Ammo: byte); (spot so u know if its primary or secondary we're changing) (0 auto reloads)
SetPlayerNade(Type, Number: byte); (so it also works with clusters)

GetCursorXY(ID: byte; X, Y: single);
GetPlayerColor(ID: byte; Hair, Shirt, Pants, Flames: longint);

Seconded, pretty please.

*in support*

ForceWeaponRate(position: single)

affects the current state of this blue bar



And a definitive support for GetCursorXY and SpawnParticle here.

The cursor thing would be awesome! Could make fistbox like 200x easier..
And SpawnParticle is just o.O Could make some wicked effects with that Im definitely in support of these!

Date Posted: October 11, 2007, 06:29:33 am

Heh, no way. Server's don't communicate with each other

Which reminds me, is there any chance for the server to listen for sockets so servers can communicate directly to each other and not needing to bounce off of something?

[EnEsCe]

I wont be adding listening sockets, and mouse place won't help anyone at all, what are you going to do with an integer from 0->480,0->640. They aren't world XY like those used in spawning stuff.

[Aquarius]

EnEsCe, you are disappointing me. If we have player's world XY position and cursor's screen XY position, we can calculate the cursor's world XY positions very easily. I believe it's playerX-640+(cursorX*2),  playerY-480+(cursorY*2). So stop the stupid excuses