GuiPMEditCtrl Problem

[Warcaptain]

there is no text variable for this text edit GUI... which sucks.. because i cant read or modify the value of this text box (for sending pm's)

please.. stefan if you read this fix this!!

[napo_p2p]

GuiPMEditCtrl brances off of GuiMLTextEditCtrl, which branches off of GuiMLTextCtrl. GuiMLTextCtrl has the text field.

[Warcaptain]

Unfortunately not

I dumped getvarnames and it didnt show up...

I also tried NAME.text="" and it wouldnt work Sadly.. text is NOT a variable on GuiPMEditCtrl

[ApothiX]

Maybe this was done on purpose to stop people from attempting to log PMs? Try to use NAME.getText() and see if that works, though.

[Warcaptain]

No settext() and gettext() do not work.

:-\ make it work

[napo_p2p]

Hmm, you're right. I think it is because the GuiPMEditCtrl is meant for the players to edit the text field. I guess it is partly to prevent irresponsible staff members from sending false PMs from other accounts.

[Warcaptain]

Grr... I see why that is.. but still.

Should be serveroption: rwpm=true

[ApothiX]

Originally Posted by Warcaptain

Grr... I see why that is.. but still.

Should be serveroption: rwpm=true

I don't really see how a serveroption would change the fact that staff would try to log/send false PMs?

[Warcaptain]

It wouldnt try and stop them... but it would make it so servers that wanted the ability do to that can. IE: putnpc enabled or something like that... commands that might be dangerous can be enabled if the manager things its okay.

If a dangerous script gets created.. maybe the GST can get off their butts and find it and have the staff remove it. But dont disable features just because it MIGHT be used in a bad way.

[ApothiX]

Originally Posted by Warcaptain

It wouldnt try and stop them... but it would make it so servers that wanted the ability do to that can. IE: putnpc enabled or something like that... commands that might be dangerous can be enabled if the manager things its okay.

If a dangerous script gets created.. maybe the GST can get off their butts and find it and have the staff remove it. But dont disable features just because it MIGHT be used in a bad way.

How exactly would you use the manipulation of player's private messages in a 'good' way?

[Warcaptain]

I was making an 'away message' type system for starters...

[Rick]

Originally Posted by Warcaptain

I was making an 'away message' type system for starters...

So use something other than PMs?

[napo_p2p]

Originally Posted by Warcaptain

I was making an 'away message' type system for starters...

You can probably make use of onPM() then.

I am not sure, but I think the syntax is:

PHP Code:

function onPM(pl) {

} 


Where pl is the player that pmed you.

[Warcaptain]

I know that.. but the thing is its supposed to send a PM back saying, "Im away right now, so leave me a message" or something like that (whatever the player says)

And while its 100% possible to have it sent from the NPC-Server ie: NPC-Server messages you back and says, "So and so is away, leave a message for him" thats dumb.. and since the capabilities ARE THERE.. I should be able to use them.

[ApothiX]

Originally Posted by Warcaptain

and since the capabilities ARE THERE.. I should be able to use them.

But they are NOT there, and I agree with them being not there. Personally, I would not like scripts to be able to send PMs to players under my name, without my knowledge (and I'm pretty sure I'm not the only one who feels this way.)

[Rick]

Perhaps Stefan could allow some sort of message system where it distinctly marks the sent message with text saying it's not actually from that player.

Like the "Mass Message:" prefix on mass messages. Maybe "Automated Message:" or "Script Message:".

[ApothiX]

Originally Posted by Rick

Perhaps Stefan could allow some sort of message system where it distinctly marks the sent message with text saying it's not actually from that player.

Like the "Mass Message:" prefix on mass messages. Maybe "Automated Message:" or "Script Message:".

That could work