[CommanderDJ]

Hey guys,
So in light of this guide created by The_E for writing new SEXPs, I decided to try my hand at writing my first ever SEXP: set-jumpnode-name.

It does what you think it does, but here's the description text anyway:

Code: [Select]

Sets the name of a jump node. Takes 2 arguments...
1: Name of jump node to change name for
2: New name for jump node

Now, I've tested it and it works, the only thing is that SEXPs referencing the old jump node name will obviously not work after the name change. That, and I have no idea whether I've done something inherently dangerous with the code. This being my first FSO coding endeavour, I need feedback, so here's a link to a .patch file showing the changes I've made. Any feedback and constructive criticism is greatly appreciated.

CommanderDJ

EDIT: .patch file updated with The_E's corrections.

[The E]

Committed to trunk in revision 7155.

[General Battuta]

Awesome. Did DJ's note get included in the help text?

[headdie]

Nice 1 CDJ

[CommanderDJ]

Thanks for the commit!

I've actually updated the SEXP so it's now multiplayer compatible. I've also added the relevant note to the help text.

Here's an updated .patch file. In it, I also took the liberty of correcting a spelling error in another sexp (it used muli_sexp instead of multi_sexp).

EDIT: Thanks headdie.

[Echelon9]

Alternative solution provided by The_E