nilly's #22.4.0
Updated to latest version.
Don't know what this is? Look at these threads for info on features and changes:
Important changes/info:
Planned changes in future updates:
Information on new additions to this build:
I'll only discuss the new "enhanced quest portrait," and "chat notification" mod as the other changes are self explanatory.
Enhanced Quest Portrait
This mod basically adds information and functionality to the quest portrait and tool tip. It adds hp bars to both (portrait and tool tip) and shows the closest player distance on the tool tip. The portrait's hp bar will begin to flash once someone is within 20 tiles of the mob. Right clicking on the quest tool tip will teleport you to the player nearest the quest (like /tq for realm relay).
Chat Notification
This is a pretty big mod that I suspect most of you will have little use for at the moment as I didn't include any default notifications for this release. The basic idea of the mod is to allow the user to monitor the chat box for patterns. If a pattern is spotted, the user can take various actions. The user can either play a sound (that is "built" into rotmg), read some words via text-to-speech, or execute a chat (console) command.
An accompanying list is provided so that the user can manage their notifications like which ones are turned on or off.
Here is a rundown of the command:
The above makes use of some regular expression syntax to make it more clear on what is optional and the different variations one can enter in a command. If you know little to nothing about regular expressions, don't worry. I'll explain the commands in more detail.
We'll start by giving some examples of how to manage your notifications after adding them.
The first thing you should know is that all chat notifications are identified with a name, a name that you give it when you added it. This name is used when you want to enable/disable/remove it. Examples of managing your notifications are provided below.
Now we'll take a look at adding a notification. We'll first look at the options available to us and then we'll go through a few examples.
The first option is: -m (sound|command|tts)
-m specifies the mode the chat notification will be in. We have three different modes to choose from: sound, command, and tts. If selecting sound mode we would type, -m sound. If command mode, -m command. Similarly text-to-speech mode would look like this: -m tts. Sound mode will allow the user to play a "built" in rotmg sound when a match for our pattern is found. Likewise, tts mode (text-to-speech) will read some text. Command mode will execute a chat (console) command. These modes are further defined by the "modeString" which is where the user specifies exactly what is played or what command is executed. If this option is omitted, the notification defaults to sound mode.
The second option is: -s gwlms
-s specifies the scope of the notification. This is used to limit pattern matching to very specific types of chat. There are 5 different scopes defined which can be combined.
So for example if we only wanted to match our pattern to stuff from guild chat we would use this: -s g. Or if we wanted to match our pattern to guild, local, and whisper, we would use: -s glw or -s wlg or -s lgw. The order that you specify the scopes doesn't matter. If this option is omitted, it defaults to gwlm (looks in guild, whisper, local, and mob chat).
The third and last option is: -p "playerNamePattern"
-p option allows us to further limit our pattern matching to particular players (based on name). -p is immediately followed by a quoted string where the names of players are specified. It is a regular expression, so one can match player names based off that. For example, -p "Ruth" will pattern match text from all players named "Ruth" (which will be only one person). Depending on how we setup our scope (the option discussed before this) we can setup the notification to at very specific types of chat from Ruth (guild, whisper, etc...). If one wanted to match more than one player, one can use the | (regular expression or) to match multiple players. An example of a "playerNamePattern" with two players would be "Ruth|Bob". An example of three players would be "Ruth|Bob|Sandy". Currently the pattern matching of names is case sensitive so you'll need to capitalize characters correctly. If this option is omitted, the player name pattern defaults to ".*" (which is a regular expression for everyone).
So now that we know how to configure the various options for the add command, let's look at the required parameters.
The above add command omits all options. So in this case the default for those options is assumed (-m sound -s gwlm -p ".*").
The first quoted text is the notification name. This can be anything you want and is used to identify your notification for managing it as discussed previously.
The second quoted text is the pattern. This is a regular expression that is used to find matches. If a match is found based off this pattern, the sound, text-to-speech, command that is specified by the notification gets executed.
The third and last quoted text is the mode string, which is handled differently depending on the mode specified. If sound mode is specified, the user will enter in a sound name for this text. For example "enter_realm" will play the sound that some of you may have heard if you used @IziLife's Event Notifier that is found in Orape. If text-to-speech mode is specified, the quoted text will contain the text the user wants to verbalize. For example, "Holy shit, Sphinx!" will verbalize, "Holy shit, Sphinx!". Since text-to-speech is done via google translate, there is a maximum of 100 characters that can be used for the mode string in text-to-speech mode. Finally, if command mode is specified, the mode string will contain the command the user wishes to execute. For example, "Hello everyone" will type out hello everyone to local chat just as if you typed it in yourself. Another example, "/tell barf found potatoes" will whisper barf that you found potatoes.
The mode string also makes use of two special fields, "{name}" and "{message}" that function the same in all modes. If the user specifies "/tell {name} Hi" as the mode string in command mode, {name} will be replaced with the name of the player that the pattern found a match for. If in text-to-speech mode, the same mode string would verbalize, "tell insertPlayerNameHere Hi" where insertPlayerNameHere will be the actual name of the player. {message} works just like {name} except that it will be replaced with the chat text that the supplied pattern found a match in.
Alright now that we understand the add command lets look at some examples:
A few special notes:
Here's some sounds to use for notifications in sound mode. This list is small but it will do for now.
Screens:
Virus Scans:
Normal:
https://www.virustotal.com/en/file/b...is/1404377549/
nillys_22.4.0.zip - Jotti's malware scan
Reduced:
https://www.virustotal.com/en/file/6...is/1404445853/
nillys_22.4.0_reduced_steamFixed.zip - Jotti's malware scan
Added a reduced file size version. It has everything in it, just compressed more. You may see some pixelation with images.
Don't know what this is? Look at these threads for info on features and changes:
- http://www.mpgh.net/forum/599-realm-...v20-0-2-a.html
- http://www.mpgh.net/forum/599-realm-...-improved.html
- http://www.mpgh.net/forum/599-realm-...-21-0-3-a.html
- http://www.mpgh.net/forum/599-realm-...-21-2-1-a.html
- http://www.mpgh.net/forum/599-realm-...-21-3-0-a.html
- http://www.mpgh.net/forum/599-realm-...-21-5-0-a.html
Important changes/info:
- added enhanced quest portrait.
- added chat notification.
- fixed quest tool tip scaling issue when fsv3's scale ui is on.
- "remove trade accept delay" has been renamed and tweaked to function better.
- Projectile No-Clip changed to a keyboard toggle. *Suggested by @j358358w*
- Renamed loot exception command filter to loot ignore. The command names were changed as well. The new commands are /alig, /rlig, /liglist, /ligclear, /ligdefault.
Planned changes in future updates:
- Rework auto loot & loot notification. Seeing how the chat notification mod goes, I might implement a loot ignore/exception command based on regular expressions and remove the /alig, /rlig, /liglist, blah blah blah commands. Will separate the auto loot and loot notification so that one can see loot notifications for items they don't want to auto loot. Loot that is auto looted will have a different color notification than loot that isn't.
- Auto Ability improvements. Still thinking of ways to keep it simple and not have to resort to adding a million options so that one can get it functioning just the way they want.
- Stealth hack mode. Still hashing out how this will work exactly.
- auto potter
- damage percent indicator
Information on new additions to this build:
I'll only discuss the new "enhanced quest portrait," and "chat notification" mod as the other changes are self explanatory.
Enhanced Quest Portrait
This mod basically adds information and functionality to the quest portrait and tool tip. It adds hp bars to both (portrait and tool tip) and shows the closest player distance on the tool tip. The portrait's hp bar will begin to flash once someone is within 20 tiles of the mob. Right clicking on the quest tool tip will teleport you to the player nearest the quest (like /tq for realm relay).
Chat Notification
This is a pretty big mod that I suspect most of you will have little use for at the moment as I didn't include any default notifications for this release. The basic idea of the mod is to allow the user to monitor the chat box for patterns. If a pattern is spotted, the user can take various actions. The user can either play a sound (that is "built" into rotmg), read some words via text-to-speech, or execute a chat (console) command.
An accompanying list is provided so that the user can manage their notifications like which ones are turned on or off.
Here is a rundown of the command:
Code:
Add a notification: /cn add (-m (sound|command|tts))? (-s gwlms)? (-p "playerNamePattern")? "My Notification Name" "pattern" "modeString" Remove a notification: /cn remove all|"asdf" Show all notifications: /cn (show )?list Restore default notifications: /cn (default|restore|restore default) Enable all or a particular notification: /cn enable all|"asdf" Disable all or a particular notification: /cn disable all|"asdf"
We'll start by giving some examples of how to manage your notifications after adding them.
The first thing you should know is that all chat notifications are identified with a name, a name that you give it when you added it. This name is used when you want to enable/disable/remove it. Examples of managing your notifications are provided below.
- Example of how to remove a notification:
- /cn remove "My notification name"
- Example of how to remove all notifications on your notification list:
- /cn remove all
- Examples of how to show the notification list:
- /cn show list
- /cn list
- Examples of how to restore default notifications (currently not implemented):
- /cn restore
- /cn default
- /cn restore default
- Example of how to enable a notification:
- /cn enable "My notification name"
- Example of how to enable all notification:
- /cn enable all
- Example of how to disable a notification:
- /cn disable "My notification name"
- Example of how to disable all notification:
- /cn disable all
Now we'll take a look at adding a notification. We'll first look at the options available to us and then we'll go through a few examples.
Code:
/cn add (-m (sound|command|tts))? (-s gwlms)? (-p "playerNamePattern")? "My Notification Name" "pattern" "modeString"
-m specifies the mode the chat notification will be in. We have three different modes to choose from: sound, command, and tts. If selecting sound mode we would type, -m sound. If command mode, -m command. Similarly text-to-speech mode would look like this: -m tts. Sound mode will allow the user to play a "built" in rotmg sound when a match for our pattern is found. Likewise, tts mode (text-to-speech) will read some text. Command mode will execute a chat (console) command. These modes are further defined by the "modeString" which is where the user specifies exactly what is played or what command is executed. If this option is omitted, the notification defaults to sound mode.
The second option is: -s gwlms
-s specifies the scope of the notification. This is used to limit pattern matching to very specific types of chat. There are 5 different scopes defined which can be combined.
Code:
g - guild w - whisper l - local m - mob (non player generated chat) s - spam (chat that is blocked via the star requirement)
The third and last option is: -p "playerNamePattern"
-p option allows us to further limit our pattern matching to particular players (based on name). -p is immediately followed by a quoted string where the names of players are specified. It is a regular expression, so one can match player names based off that. For example, -p "Ruth" will pattern match text from all players named "Ruth" (which will be only one person). Depending on how we setup our scope (the option discussed before this) we can setup the notification to at very specific types of chat from Ruth (guild, whisper, etc...). If one wanted to match more than one player, one can use the | (regular expression or) to match multiple players. An example of a "playerNamePattern" with two players would be "Ruth|Bob". An example of three players would be "Ruth|Bob|Sandy". Currently the pattern matching of names is case sensitive so you'll need to capitalize characters correctly. If this option is omitted, the player name pattern defaults to ".*" (which is a regular expression for everyone).
So now that we know how to configure the various options for the add command, let's look at the required parameters.
Code:
/cn add "My Notification Name" "pattern" "modeString"
The first quoted text is the notification name. This can be anything you want and is used to identify your notification for managing it as discussed previously.
The second quoted text is the pattern. This is a regular expression that is used to find matches. If a match is found based off this pattern, the sound, text-to-speech, command that is specified by the notification gets executed.
The third and last quoted text is the mode string, which is handled differently depending on the mode specified. If sound mode is specified, the user will enter in a sound name for this text. For example "enter_realm" will play the sound that some of you may have heard if you used @IziLife's Event Notifier that is found in Orape. If text-to-speech mode is specified, the quoted text will contain the text the user wants to verbalize. For example, "Holy shit, Sphinx!" will verbalize, "Holy shit, Sphinx!". Since text-to-speech is done via google translate, there is a maximum of 100 characters that can be used for the mode string in text-to-speech mode. Finally, if command mode is specified, the mode string will contain the command the user wishes to execute. For example, "Hello everyone" will type out hello everyone to local chat just as if you typed it in yourself. Another example, "/tell barf found potatoes" will whisper barf that you found potatoes.
The mode string also makes use of two special fields, "{name}" and "{message}" that function the same in all modes. If the user specifies "/tell {name} Hi" as the mode string in command mode, {name} will be replaced with the name of the player that the pattern found a match for. If in text-to-speech mode, the same mode string would verbalize, "tell insertPlayerNameHere Hi" where insertPlayerNameHere will be the actual name of the player. {message} works just like {name} except that it will be replaced with the chat text that the supplied pattern found a match in.
Alright now that we understand the add command lets look at some examples:
- /cn add "Dex Spotter" " dex " "enter_realm"
This will use defaults for options (since they are not specified), which is sound mode and looks for pattern matches for all players in guild, whisper, local, and mob. The name is "Dex Spotter", the pattern to be matched is the literal " dex ", and the sound that will be played on a match is enter_realm - /cn add "Dex Spotter" " [Dd][Ee][Xx] " "enter_realm"
Case insensitive version of the notification discussed prior. - /cn add -s w "Got Whisper" ".*" "enter_realm"
The only option specified here is the scope. The two other option are left to default (sound mode and all player names). The scope option specified to only look at whispers received. The pattern ".*" will match any kind of text which means any whisper will cause the sound "enter_realm" to play. - /cn add -s g "Guild Chat" ".*" "enter_realm"
This is very similar to the "Got Whisper" notification above. The only difference (aside from the name) is that the scope specified here is g (which means guild). - /cn add -m command -p "LubsBBQ" "Copy Cat" ".*" "{message}"
With this add command, the only option left to default is the scope (defaulted to guild, whisper, local, mob). Command mode is specified and all pattern matching will be based off chat coming from LubsBBQ. The pattern is ".*" which means any kind of text and the mode string is "{message}" which is a special field that is replaced with the chat text that LubsBBQ provided. Basically what this does is repeats what LubsBBQ says in local chat. - /cn add -m tts -s m "Oryx Say Sphinx?" "Grand Sphinx" "{name} said {message}"
This one operates in text-to-speech mode and looks at all non player chat for the pattern "Grand Sphinx". If a match is found, the name of the mod and their message is verbalized. (This might not function correctly due to the way google translate handles special characters)
A few special notes:
- Command mode has a self imposed limit of 10 commands per every 5 seconds to avoid excessive spam. If your notifications begin executing commands in excess of that limit, chat notifications that operate in command mode will start to disable themselves.
- Pattern matching is currently case sensitive. This may change in future versions.
- If double quotes are used in a pattern or required string, make sure to escape them with \ .
Here's some sounds to use for notifications in sound mode. This list is small but it will do for now.
Code:
button_click death_screen enter_realm error inventory_move_item level_up loot_appears no_mana use_key use_potion
Virus Scans:
Normal:
https://www.virustotal.com/en/file/b...is/1404377549/
nillys_22.4.0.zip - Jotti's malware scan
Reduced:
https://www.virustotal.com/en/file/6...is/1404445853/
nillys_22.4.0_reduced_steamFixed.zip - Jotti's malware scan
Added a reduced file size version. It has everything in it, just compressed more. You may see some pixelation with images.
Originally Posted by nilly
