Not seeking to resurrect this topic. But for those who come one day later, a new feature now exists in PennMUSH which allows this behavior more easily: help monikers

You can lean on the moniker() function, or fall back on the default exit format, for this functionality.

@Ashen-Shugar Mwah!

@skew said in Quiet Quiet Rooms?:

Thank you, @Chime!

Anytime!

Hate to do this, but can anyone break down how to apply this patch in very, very simple terms? I can get into the console as necessary, I know what git is, I just have no idea how to apply a patch to a game. Or, well, most anything else linux-related.

Sorry for being a bit terse. I spend most of my waking hours at some sort of unix prompt (Linux or otherwise). First, you'll need several tools. If you don't have administrator (root) access, then hopefully your host has already got these installed. On deb-derived systems (Debian, Ubuntu, Mint, etc etc) you'll want something like

$ sudo apt-get update ... some lines downloading package lists ... $ sudo apt-get install build-essential g++ make patch tar bzip2 wget git ... some lines describing additional packages it wants to install ... ... question about if that's okay (say yes, generally) ... ... many lines about downloading and installing each package ...

If the tools are already there, then you won't need to do that.

$ cd $ mkdir mux-src $ cd mux-src $ wget ftp://ftp.tinymux.org/tinymux-2.12/alpha/3/mux-2.12.0.3.unix.tar.bz2 --2017-05-09 23:35:06-- ftp://ftp.tinymux.org/tinymux-2.12/alpha/3/mux-2.12.0.3.unix.tar.bz2 => ‘mux-2.12.0.3.unix.tar.bz2’ Resolving ftp.tinymux.org (ftp.tinymux.org)... 52.34.23.255, 2600:1f14:2a0:2201:ab7d:7d:8dd3:57fc Connecting to ftp.tinymux.org (ftp.tinymux.org)|52.34.23.255|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD (1) /tinymux-2.12/alpha/3 ... done. ==> SIZE mux-2.12.0.3.unix.tar.bz2 ... 1080619 ==> PASV ... done. ==> RETR mux-2.12.0.3.unix.tar.bz2 ... done. Length: 1080619 (1.0M) (unauthoritative) mux-2.12.0.3.unix.tar.bz2 100%[===============================================================================>] 1.03M --.-KB/s in 0.09s 2017-05-09 23:35:06 (11.6 MB/s) - ‘mux-2.12.0.3.unix.tar.bz2’ saved [1080619] $ tar xjvf mux-2.12.0.3.unix.tar.bz2 mux2.12/ mux2.12/INSTALL mux2.12/SGP mux2.12/CHANGES mux2.12/LOCAL mux2.12/REALITY.SETUP mux2.12/NOTES mux2.12/src/ mux2.12/src/move.cpp mux2.12/src/Doxyfile mux2.12/src/autoconf.h.in mux2.12/src/muxcli.h ... many more files unpacking ... $ git clone https://github.com/lashtear/tinymux.git Cloning into 'tinymux'... remote: Counting objects: 59424, done. remote: Compressing objects: 100% (2/2), done. remote: Total 59424 (delta 0), reused 0 (delta 0), pack-reused 59422 Receiving objects: 100% (59424/59424), 18.34 MiB | 17.20 MiB/s, done. Resolving deltas: 100% (46787/46787), done.

Now, you should be in a folder called 'mux-src' right underneath your homedir, with the tar.bz2 archive of upstream tinymux from Brazil and a git checkout of my quirky version.

$ ls -laF total 1080 drwxr-xr-x 4 lucca lucca 4096 May 10 00:01 ./ drwxr-xr-x 104 lucca lucca 12288 May 9 23:56 ../ drwxr-x--- 5 lucca lucca 4096 Feb 13 2016 mux2.12/ -rw-r--r-- 1 lucca lucca 1080619 May 9 23:35 mux-2.12.0.3.unix.tar.bz2 drwxr-xr-x 11 lucca lucca 4096 May 9 23:58 tinymux/ $ cd tinymux $ git show 5fd6080286dc36fe7ba6673a208dbfb445a6d056 > ../blind-room.patch $ cd .. $ ls -laF total 1088 drwxr-xr-x 4 lucca lucca 4096 May 10 00:03 ./ drwxr-xr-x 104 lucca lucca 12288 May 9 23:56 ../ -rw-r--r-- 1 lucca lucca 4606 May 10 00:03 blind-room.patch drwxr-x--- 5 lucca lucca 4096 Feb 13 2016 mux2.12/ -rw-r--r-- 1 lucca lucca 1080619 May 9 23:35 mux-2.12.0.3.unix.tar.bz2 drwxr-xr-x 16 lucca lucca 4096 May 10 00:03 tinymux/

Now we have that same bit plus that blind-room.patch file. Now before you start suggesting that it'd be really handy if we kept all those patches somewhere easy to access-- that's exactly what any revision control software (like git) does. Anyway, time to apply.

$ cd mux2.12 $ patch -p2 <../blind-room.patch patching file game/text/help.txt patching file src/move.cpp patching file src/netcommon.cpp

Congrats. You now have a tinymux tree from Brazil but with just that one patch of mine added. If you were instead building from his git repo, you could do this all much easier with the git cherry-pick command, but you probably aren't. If building against an archive export of his git tree, change the parameter to -p1 because of the slightly different directory structure.

This should work for most any 2.12 or 2.10 version, though if you use 2.10 the file offsets are slightly different, so you would see instead:

$ cd mux2.10 $ patch -p2 <../blind-room.patch patching file game/text/help.txt Hunk #1 succeeded at 5009 (offset -12 lines). patching file src/move.cpp patching file src/netcommon.cpp

Yes; git, patch, diff, etc are all rather clever and indispensable tools that I can't imagine getting through my day without. Game should build as normal with these changes.

@Lotherio
Battletech MUX is a hardcode fork. You can get it from https://sourceforge.net/projects/btech/

For what I do: Discrete Math, Finite Math (I know, that's like barely basic math, but include logic symbols), Logic Symbols...

Following Logical lines of thought. Truth Tables... I fall back on Truth Tables and Discrete Math a lot. For everything else, I just use a program to do it for me because I'm lazy.

Also, Evennia is fun to play around with. Don't take the whole "Well then you need to learn more about Django, and this, and that." For me, that's exactly why I am playing around with it. Then again, I'm a nerd and I just love learning things (I'm also a grunt and shiny objects generally make me happy, so take whatever I say as a grain of salt).

@Derp Ooooh. Ok. Thanks.

Yeah, I can't help! But I understand!

Thanks @Ashen-Shugar @Lotherio. That's about what I figured, but it was worth asking.

Run everything on an old server. Not only will all your function calls be delayed, but everything else will too! It'll be just like the 90s, only with better hair and no shoulder pads.

@Sparks said in Client-Side Spacing:

I also do think there could be an argument made for functional expansion; if I had the origin command in a register, I could do interesting conditional things like add out-of-band data for the client to process. Like adding a conveniently, consistently parseable string saying 'this is a page from <X>' with a begin/end tag, so that even multi-line pages could be pulled into a specific spawn.

Of course, at that point, you're making this wildly more complicated, but it's still a personal pipe dream... to have a way to snag multi-line outputs for client-side processing. And if we're discussing adding user-specific formatting hooks that have a chance to alter output, making them conditional based on the origin command and enactor makes me happy.

And..... done.

This is optionally available in the latest RhostMUSH 4.0 engine with the @admin (config) parameter posesay_funct enabled (default disabled).

The SPEECH_PREFIX and SPEECH_SUFFIX attributes only work for connected player types, and will not work if the attribute is set NO_COMMAND.

If you trigger the cpu alert (by blowing away the cpu alert) it naturally logs the attempt then sets the attribute NO_COMMAND for safty sake.

So, you got your pipe-dream. Enjoy 🙂

I know it's been forever since I asked about this, but I finally got this all set up and working and wanted to pass along a thank you to @Seamus and @Ashen-Shugar for their help.

I was able to tweak it just a teensy bit and work a title change for the room in to adjust how it displays on +where and in the room list, too, which I'm hoping will also be helpful.

Thank you again, this was enormously helpful.

@Reason Thanks, that's appreciated!
.
Griatch

Yeah I'm not aware of anything in Penn/Tiny that would do this.

You could also ask the coder to create a global altmail() function that just wraps around mail(). Would only take them a minute, vs. asking them to build something unusual into +finger to let you capture the output, or implement your alt mail check as a global.

For the longest time, I've had issues where I wish there was a way to save information to a database like SQL, in some known format, and be able to query it. I don't just mean 'just use SQL', but I mean advanced features like... 'related topics', etc.

I basically wanted Graph based storage. I tried using oqgraph, since MariaDB gives access to that, and with MariaDB being binary compatible with MySQL, I could use it. But it isn't well maintained, and it tended to crash things. So I dropped that. (Read: Don't use OQGraph for SQL Graph Storage, it's a trap!)

I recently actually started work on this anew, and in doing so fixed a bug in PennMUSH's SQL handling that enabled single-return Stored Procedures -- creating Graph based functions in SQL. However, SQL isn't really made for this... with enormous tables, this'll get slow. (Read: Stored Procedures for SQL Graph Storage is the best option at the moment)

It's roughly detailed here:
http://mush-mercutio.tumblr.com/post/153345784737/pennmush-graph-framework

If I finish this, I may at some point rewrite SceneSys to use this kind of storage, and launch some basic things along with it, like a basic BBS and a basic Jobs system as a POC.

Being reflected on the MUSH and on SQL, would allow easy grabbing through websites, etc.

@skew said in Hook Help:

@Thenomain I am thirty (one). >=|

My nieces are older than you... all three of them. 🙂

Binary is still code and still in use every day 🙂

I'm well versed with Dahan's D6 in both Penn and Rhost.

@Thenomain Right, and it works well for a currency system if you're not using it to fuel code. If you take that approach, a global balance would still be nice to have. You'll also need to code an object to handle paychecks, because the paycheck configuration parameter is global and a daily allowance based on signing in. I'd suggest leaving that at 0 and then looking at paycheck as a monthly job, just like it would have to be for rent.

@skew

Good looks good.

As a FYI to toss out there, for those who use PennMUSH or TinyMUSH3, it will need adaptation as the @hook code for Penn and TM3 uses the TM3 standard @hook functionality while MUX uses the Rhost @hook functionality. The syntax for @hook is different for those platforms.

So in that regard the code should work on Rhost likely without changes as well.