Topics created by skew

@skew What?! No more Balrog trolling in the middle of Cove? 😉

From Bennet, the developer, on BeipMU's discord:

Why is the store app stuck on build 312? Well here's why and how to fix it:
https://github.com/BeipDev/BeipMU/blob/master/Documentation/store_update.md
(This link is also on the main web page so more people can find it, spread the word!)

@skew said in Welcome to Chontio! A Star Wars MUSH:

Web-portal is down this morning. Being worked on!

If anyone is in a dire need of their Tuesday morning RP, you can connect to the game via ip: 209.97.149.128 port 3268.

Oh, we're back. That was fast.

And the Chontio web archive is live! Much love to Farday.

https://arescentral.aresmush.com/wiki/chontio/index.html

@skew said in Coming Soon: Chontio, a Star Wars Stand Alone MUSH:

Force powers are kinda neat, but for every force power there's likely a career talent that can do it better. Which is to say: The Force is low power and is more a story element than a game-changer.

"Hokey religions and ancient weapons are no match for a good blaster at your side, kid."

@highfalutin said in Unnecessary Messenger System - +txt code:

I love this so much I can't even. Installed just now, working beautifully. "Cheiron Group Simple Messaging System" got me chortling.

I thought I changed that in the default. Oooooh well. Enjoy.

Code has been deployed on Fate's Harvest for a beta version. Already squashed a lot of bugs. Will be adding the preferences commands, then staff commands, then packing up v1. Few more days!

That code block goes into your /var/www/wiki/ folder, and should be newly created as:

.htaccess

It doesn't go into the site.conf (or default.conf file if you are using that).

In the site.conf or (default.conf file if you're using that) file, you just want to make sure that wiki.site.com is pointing to /var/www/wiki, not /var/www/html, which is often set as the default.

https://www.digitalocean.com/community/tutorials/how-to-set-up-apache-virtual-hosts-on-ubuntu-16-04 covers the other steps you want to peek at that address how you want to handle the site.conf file (and any other *.conf files) specifically.

This covers .htaccess and how to get it going, which has a bit more info than the other link. https://www.digitalocean.com/community/tutorials/how-to-use-the-htaccess-file

Between those two tutorials, I've been able to get multiple wikis and a default index page landing running off of one droplet, with each site in it's own folder in /var/www/ with things pointing where they need to be pointed to get people to the right places.

EDIT FOR EXAMPLE:
For an example following the two tuts above:
https://pantheogenesis.world/
https://www.pantheogenesis.world/
https://forum.pantheogenesis.world/
...and while these have nothing on them/done to them yet, note the footer text, which demonstrates they are each distinct wiki installs:
https://core.pantheogenesis.world/
https://7d.pantheogenesis.world/
https://7dstaff.pantheogenesis.world/
I puttered out and stopped giving a fuck before finishing up the intended interwiki links to pipe the data around, but eh. (The goal here is to store all RPG data on core to pipe to whatever game wiki is active as needed, with each game having a private staff wiki and a player-side wiki that can all talk to each other in a fairly fine-grained way.) They otherwise share some core files with symbolic links to what would otherwise be needlessly duplicated data; this is all stored in 'core' and linked to 7d and 7dstaff, to control edit permissions and access to data on the various wikis as needed. You don't need anything from this latter paragraph, probably, but the two linked tutorials explain all the steps needed to do what you're trying to accomplish above.

IMPORTANT: Note that if you choose to use no additional text or swap in place of index.php and just go straight from the domain to the content, you will need to lock down the main namespace so no one can edit it to prevent potential conflicts. This means using custom namespaces for your various categories of things rather than dumping everything into the main namespace. Doing this also gains you access to the DPL namespace=<whatever> selection criteria, which may help prevent the need for as many categories on the wiki, and allows you to use the categories for more fine-tuning in your queries.

@arkandel said in How to type &#x60;quit&#x60; and quit PennMUSH?:

If I just close the window from either the other connection will stick around. Now, sometimes that's what I actually want, but if I type 'quit' then I know I'm logged off from all my clients.

Quit doesn't close all your connections, just the one you're quitting from. At least, that's true of Tiny and Evennia. Penn could be different. (Though, yes, if you are active on another account you don't necessarily need/want the quit effects.)

The 1890s version makes me think of Arcanum. And I really, REALLY love that game. So I'd have to pick that option, even though I'm not totally against the first option. They both sound good, but giving me flashbacks to Arcanum make me like #2 more.

@skew

As long as you remain within the functions, or command-lists, it should be fine.
It's when your command lists start containing the following specific commands: (@dolist, @wait, @trigger, are the ones I can think of)

@emit a; @dolist b c d=@emit ##; @emit e;

That you'll get stuff like:

a e b c d

This is because of how command queues work. This gets resolved with doing stuff like:

@emit a; @dolist/notify b c d=@emit ##; @wait me=@emit e;

@Thenomain said in Idle timer? (Tiny):

@faraday said in Idle timer? (Tiny):

most random idle timeouts are the client's router

Which means there's no solution from the game. Finding out what is causing these people to be disconnected becomes an exercise for someone who knows networking tools.

Yes. Or talk to whomever implemented the web client and see if they can do some kind of client-side keepalive feature.

+getcast

This is a bit of quick'n'dirty for TinyMUX systems using one of the standard +finger commands I see in WoD games (and elsewhere). It's designed to be plugged into the SGP that comes with Tiny. Specifically, it's looking for SGP - Main Globals which is usually #6.

Please update the #6 if you want this elsewhere!

The code will check the current room you are in and grab every player bit that's there, look for their "wiki" attribute that's set in +finger, and output a list of properly formatted Wiki names. This is extremely useful all the time, but especially where you're playing games where people have bit names that do not match their Wiki page names.

Note this code looks for ##/finger-wiki and ##/wiki. If your means of logging a wiki uses a different attribute on the player bit, you'll need to update the code. Note also it looks for everything after the / in that value, so http://fatesharvest.com/w/Green will return Green.

Usage:
+getcast : gets the cast for the room you're in.
+getcast <name> : get the wiki information for a specific person.

If the player does not have their wiki set in their +finger, it'll say "missing".

Output:

______________________________________________________________________________ Scene Cast List for OOC Nexus [[User:Skew|Flatirons]], [[Logan_Brenner|Logan]], [[Beats|Beatrice]] ______________________________________________________________________________

or

Wiki-Friendly Formatting for AJ: [[AJ_Ray|AJ]]

Here's the code...

// This should go on SGP - Main Globals &c.get.cast #6=$^\+?getcast(.*)$:@pemit %#= strcat( setq( 0, secure( %1 )), switch( %q0, , u( f.disp.cast.room, loc( %# ), %# ), %b*, u( f.disp.cast.target, trim( %q0 ), %# ), It's either something or nothing how did this go wrong?) ) &f.disp.cast.room #6= strcat( setq( l, %0 ), setq( p, %1 ), u( disp.rainbow ), %r, center( %xhScene Cast List%xn for %xh[name(%ql)]%xn, 79 ),%r%r, iter( lcon( %ql, connect ), strcat( setq( f, last( get( ##/finger-wiki ), / ) ), setq( w, last( get( ##/wiki ), / ) ), lit([[), switch( 1, t( %qw ), %qw, t( %qf ), %qf, %xh%xxMissing%xn), |, name( ## ), lit(]]) ), , %,%b), %r, u( disp.rainbow) ) &f.disp.cast.target #6= strcat( setq( t, pmatch( %0 ) ), if( t( %qt), strcat( %r, Wiki-Friendly Formatting for %xh[name( %qt )]%xn:, %b, setq( f, last( get( %qt/finger-wiki ), / ) ), setq( w, last( get( %qt/wiki ), / ) ), lit([[), switch( 1, t( %qw ), %qw, t( %qf ), %qf, %xh%xxMissing%xn), |, name( %qt ), lit(]]), %r ), %xh<+getcast>%xn Target must be a player. ) ) &disp.rainbow #6=%r%xx__%xh__%xn%xm__%xh__%xn%xb___%xh___%xn%xc____%xh____%xn%xg_____%xh_____%xn%xx___%xn%xx_%xh_%xn%xm_%xh_%xn%xb_%xh_%xn%xc_%xh_%xn%xh%xx___%xn%xg%xh_____%xn%xg_____%xc%xh____%xn%xc____%xb%xh___%xn%xb___%xm%xh__%xn%xm__%xx%xh__%xn%xx__%xn @set #6/c.get.cast=regex

That disp.rainbow makes a pretty rainbow line. Feel free to replace u( disp. rainbow ) in the code with header( +getcast ) or whatever you'd like. I liked the rainbow. It's a good rainbow.

And here's the copy+paste:

&c.get.cast #6=$^\+?getcast(.*)$:@pemit %#=strcat( setq( 0, secure( %1 )),switch( %q0,, u( f.disp.cast.room, loc( %# ), %# ),%b*, u( f.disp.cast.target, trim( %q0 ), %# ),It's either something or nothing how did this go wrong?) ) &f.disp.cast.room #6=strcat( setq( l, %0 ),setq( p, %1 ),u( disp.rainbow ), %r,center( %xhScene Cast List%xn for %xh[name(%ql)]%xn, 79 ),%r%r,iter( lcon( %ql, connect ), strcat(setq( f, last( get( ##/finger-wiki ), / ) ),setq( w, last( get( ##/wiki ), / ) ),lit([[),switch( 1,t( %qw ), %qw, t( %qf ), %qf,%xh%xxMissing%xn), |, name( ## ), lit(]]) ), , %,%b), %r,u( disp.rainbow) ) &f.disp.cast.target #6=strcat(setq( t, pmatch( %0 ) ),if( t( %qt),strcat(%r, Wiki-Friendly Formatting for %xh[name( %qt )]%xn:, %b,setq( f, last( get( %qt/finger-wiki ), / ) ),setq( w, last( get( %qt/wiki ), / ) ),lit([[),switch( 1,t( %qw ), %qw, t( %qf ), %qf,%xh%xxMissing%xn), |, name( %qt ), lit(]]), %r ),%xh<+getcast>%xn Target must be a player. )) &disp.rainbow #6=%r%xx__%xh__%xn%xm__%xh__%xn%xb___%xh___%xn%xc____%xh____%xn%xg_____%xh_____%xn%xx___%xn%xx_%xh_%xn%xm_%xh_%xn%xb_%xh_%xn%xc_%xh_%xn%xh%xx___%xn%xg%xh_____%xn%xg_____%xc%xh____%xn%xc____%xb%xh___%xn%xb___%xm%xh__%xn%xm__%xx%xh__%xn%xx__%xn @set #6/c.get.cast=regex

Thanks, you're the best!

@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.