Shoutbox

quote:

---

Originally posted by Moh

quote:

---

Originally posted by CookieRevised
Moh Zayadi, no, he means disabling the message shown in the conversation when someone nudges him. This will not be hidden if you disabled "sending and recieving nudges".

This can only be hidden if you patch messenger.
(which could be done with a (advanced) script though).

---

From what I concluded, he uses Guru's script. So, if he disables sending and receiving nudges, people wouldnt be able to nudge him and thus the message will not appear. =p

---

No, disabling that option will only disable the actual shaking of the window. People will still be able to send a 'nudge' and the message "x has send you a nudge" will still be visible (if they have enabled sending and receiving nudges), no matter if you install that script or not.

quote:

---

Originally posted by hokxj
does anyone know why when i send a nudge it doesnt stop sending?
eg. i type: /sendnudge<2> and instead of only sending 2 it sends it non stop

---

If the help of a command says something like "/command <parameter>" then the stuff between < and > means it is a description of what the parameter is. So the actual parameter is without the < and >.

This is one of the many conventions used in the IT world to show the syntax of a command. The mean reason to use < and > is so the description could contain multiple words (with spaces between them), a sentence if you like. eg: /command <random number>

This to avoid confusion, because with the above example, if you would leave out the < and >, you could otherwise think that there are 2 parameters ('random' and 'number') and the following was a valid command line:
/command blahblah 42

Another way is using italics (eg: /command parameter), but obviously this isn't always possible since there isn't always an italic font available and it wouldn't solve the above confusion.

Another very old convention is for example the use of [ and ] which is usually used to for optional parameters.


All this can also be used to nest parameters into other parameters. For example:
/command [<IN:sourcefile> <type number>] <OUT:destination file>

Notice that 'type number' is nested together with the 'sourcefile' parameter between [ and ] meaning that if you use the optional 'sourcefile' parameter you also must use the 'type' parameter. If you don't use the 'sourcefile' parameter, you don't need to enter the 'type number' parameter. The 'destination file' parameter isn't optional in this syntax.  Also notice that the textual descriptions here are in italic while 'IN:' and 'OUT:' aren't. This means that the 'IN:' and 'OUT:' are part of the actual parameters. Valid command lines are:
/command IN:myfile.txt 5 OUT:myfile.doc 
/command OUT:myfile.doc 

There are many more ways of showing the syntax of a command line and sometimes they can become very complicated though, also using '...' (repeat as much as you like) and '|' (or).


Anyways, in general, for Plus! related commands, just remember that stuff between <> is a description and that the actual parameter is always without the < and >...


Last but not least, there is _always_ a space between the command and the parameters.

------

Anyways, the command /sendnudge<2> should actually not do anything at all as it is not a valid command and/or valid parameter. So if it starts sending nudges continuously it should be considered a bug.

Can the script be updated to the updated messenger 14.0.8089.726

are you sure it doesnt work with the latest build?
whats new in the new build of wlm anyway?

I'm sure it doesn't work and the main post states that it can only be used up to version 14.0.8064.206

There are only bug fixes in the new version

NudgesToolsScript 1.38

Changes Log:

Updated To Build 8089.726

------------------------------------------------------------

how do u stop when u have done this

/sendnudge <8>

Send /stopnudge =)

quote:

---

Originally posted by hokxj
does anyone know why when i send a nudge it doesnt stop sending?
eg. i type: /sendnudge<2> and instead of only sending 2 it sends it non stop

---

ok now i do understand the syntaxing of this command. however when i try /sendnudge <2> <2> (send 2 nudges at a 2 second delay) it does not accept the command. as above when i write /sendnudge <2> (send 2 nudges at 1 second default interval) it goes into unlimited mode and just keeps sending them. ideas?

still no update for wlm 14.0.8089.726?

First of all thanks for the script
i was using an old version of msn and nudgestoolsscript, and now i had to change to newer msn (it wouldnt login otherwise). Cant this version of nudgestool send nudges to those who appear offline?

editTHIS FEATURE IS NOT PRESENT IN 1.35 VERSION,IT WILL BE IMPLEMENTED IN THE APPEARINGOFFLINE HELPER SCRIPT)
i guess its not present in 1.35 and all after that. :/