fuzzball-muck / fuzzball-muf Goto Github PK

There should be some better organization. Any MUFs specifically meant for fb5 should be in a /old/ or /legacy/ folder, and as more MUFs get upgraded for fb7 and to match our current fb7 dbs, ones specifically meant for fb6 should be put in a different folder too.
This could also help separate more-maintained and less-maintained/more-dusty MUFs.
I'm thinking this is important, as we might have an influx of new MUFs soon.

No other .muf file is, so I assume it shouldn't be. It just needs a chmod a-x applied to it. I apologise for the repeat! Not sure if I said this in an easily seen place earlier.

Pretty self-explanatory. Just a reminder to myself (or anyone else) that a README describing what these MUFs are (generally less-maintained extra programs compared to the dbs) and how to use and install these MUFs would be nice.

If you use the mv-cp MUF, it will turn all your properties into strings (i.e. dbrefs or ints will be come strings).

This is a blocker for something I'm working on, but also a super easy fix, so I will fix it tonight. Just wanted to get an issue in to 'track' it for historical purposes.

(Unless you wanna tackle it first @wyld-sw ! This is an easy one ... use getprop / setprop instead of getpropstr / addprop)

triggur/aibot/aibots.doc is a plaintext file. While aibots.doc is a valid filename, renaming it to aibots.txt would be less likely to confuse file managers into thinking it's a Microsoft Word file.

It's a shell script, and has a shebang, so it should be.

Copied the lib-install.muf into Fuzzball 6.18. Followed all the steps. On the last one, where it says to "@install lib-install.muf", it gives the following error:
ERROR: #0=_ver/lib-install.muf/prog points to #0, which is not a program!

i have attempted to reset the dbref a couple times in multiple ways, to both replace the first #0 and the second #0 but to no avail. i attempted to find a fix online, only for it to point to a sourceforge page from 04/05, and the author saying that @propset-ting a variable would work, except not saying what to propset.

Can somebody please tell me what i need to alter to make this thing work?

Eventually, do a release with an actual numbered tarball. This'd give us a tarball to actually make a checksum for, so this could possibly become a package too. fuzzball-muf is much like what autoconf-archive is to autoconf, a collection of useful things you can use with fuzzball. And autoconf-archive is packaged for many systems.
Given this isn't a cohesive set of programs, the versioning scheme would just be 1, 2, 3, etc (with +/-master in between) with the version number only being in the README and maybe also a CHANGES file. Releases could be on a whenever-we-feel-like-it basis.

Via some digging, I can see that several "considered-core" FB6 MUF files were eventually removed from here (and I would guess, from the basedb template at the same time). I surmise it's because their functions are present in FB7 so the MUFs are no longer needed. These include:

• lib-gui.muf
• lib-index.muf
• lib-look.muf

lib-mpi.muf, however, is still present in this repository but not in the basedb repo. Its latest commit comment suggests that at least at one time, it was present in the basedb.

The question is, is this oddity because lib-mpi.muf should have been deleted from this repo but wasn't, or because it should be in the Fuzzball basedb template, and isn't?