I take it you selected the SEND_CHANNELS_TO_CHAT_LOG option in the config scrtipt? If so, and the tells aren't being sent, its because the messenger isnt being spawned at the module stating location. Make sure he was imported into the mod, he should be under Special/Custom 1, as a blank name, resref and tag are fky_chat_sender. It's possible I neglected to add him to the erf, checkin that now. If so, you can export him straight from the test module. I'll post back in a moment. Funky
On client enter, I get a TMI from both fky_chat_clenter and my pw_cliententer script (which are merged, and were wroking fine before).
Also, my database is not connecting now. I didnt see anywhere in the scripting where the connection info was changed, so I have no idea why this would be. I am running this on linux, btw.
Upon rollback, this error continued to be reported. I went about removing the new plugins, but found that the one that was the problem was the nwnx_odbc.so plugin included with the SimTools 3.0 update. Reverting to the old one I used fixed the TMI and the database connections...was there something changed in that nwnx_odbc.so plugin?
Hi, I was wondering about the !setname (and !setnameall) command(s).
We use a socketing system on our server (Shadow Mountain, shameless plug) and most of our socketable gems have a standard description, so the main way to tell similar gems apart is the name (EX: Slashing 1d4, and Slashing 2d10). Rarity levels exist and these gems are heavily traded among players. Currently our Dev team implemented SIMTools and the !setname command is restricted to DMs only. We would like to open this up to players, but one concern was made obvious during testing.
Since the default text on renamed items is white, it makes renamed items indistinguishable from normal versions. In other words, a rude player could easily rename a "Slashing 1d4" gem to "Slashing 2d10" and attempt to trade it to an unsuspecting player. Now, I know we can edit the functions locally, but what I was wondering is if you would consider adding scripted defaul color changing for renamed items as a standard feature. A system where flags and commented-out color codes are used would work great, and you could even leave the default color white so the change is transparent to existing installs who have simply upgraded. However, I'd really like to see this as a base feature since I suspect this issue may exist on many servers.
Another option might be to allow a second parameter passed in (first is original name,@ is the delimiter, second is the new name, so use @ as delimiter again, and then a numeric value or constant to represent a color name as a third parameter).
Thanks for your time and consideration, and for your awesome scriptset. I voted it a solid 10 on The Vault... seriously, no server should be running without this.
The problem with this is that other servers use colorized names, so that even a default white color would not be transparent. I actually added to toggle on and off for < and > for someone else, to not 'translate' existing color codes for this reason. I could add a toggle to prefix with a color code, but I'm unsure of the value of doing so. We also have setname for dms only, so that experienced players can't try to pass off junk to newbs as valuable based on the name (we have a rarity system where some very rare items are very valuable). Colorizing WOULD provide some warning, at least, but if they can't look at stats and see the issue, I'm not sure they would read a warning posted somewhere saying that color X items are name changed, buyer beware. Anyway, it's a simple edit. Open fky_chat_inc, find the SetName section in the commands function, around linee 2245. Add this line just before the line that has the actual SetName command in it: if (sCText != "") sCText = COLOR_ORANGE + sCText;
Then, add the same line in the setnameall command, just before this line: sSort = GetName(oCTarget);
You may also want to add an asterisk or something for color-blind people. The check for != "" is so that a blank setname can still reset the name (and color) to default.
And please, if you post more feature suggestions, post them in the feature suggestion thread and not tech support.