LainMOO

I have set up a LambdaMOO server, tentatively called LainMOO, at 162.243.84.213 port 7777. Anyone is free to connect and build/program.

>>1800 107.170.21.35 is the new address.

I am having some difficulty with setting up my character: @describe A bemused individual. I don't understand that. Try this instead: @describe A bemused individual. as

>>1805 The syntax of the parser is: <verb> <verb> <noun> <verb> <noun> <preposition> <noun> This is literally all the forms that are possible to write using the standard parser for verbs, verbs being thin wrappers over functions on objects. So for an indirect value there is always a preposition. Read "help @describe", also - the help files are very extensive.

>>2100 Also, I'm sorry for not replying earlier - I've spent the weekend away visiting my aging grandparents.

>>1800 The quotas are now 100x times the default. I'm still looking to make it less horrible but for now you need to "@measure new" regularly in order to be able to keep building and coding.

Nightly backups have been implemented.

There's no guest character system? I like to explore MUCKs a little before I make a character. Well, if people have the good will to not change the password: connect EternaGuest passpass after I'm done exploring with it myself.

Woah, the MOO implements "look" but not "smell"?

Will you use stunnel to provide encrypted connections?

>>2153 No guest characters. But I do not care if you share your passwords, that is up to you. All controls implemented is to just prevent outright malicious behavior. >>2154 Create an RP object that implements socials, then inherit from that to create your RP areas. Share it with your friends if you want - you're going to have to query me to get something assigned as a core object but anyone can inherit from anything. >>2161 This is a good idea. I will take it under consideration.

The permissions of $player.owned_objects have been set to +c and all players have had their permissions retroactively changed. This means that you can "@chmod me.owned_objects -r" and other people will not be able to see what you own. The do_audit code has been modified to cleanly take this into account.

>>2166 Yeah, you already discussed the first two with me, as I made those posts before seeing you were online. I suppose you should delete eternaguest. >good idea Thanks! Most MUCKs I use have encrypted connections, and many clients support it, like tinyfugue 5.

I found the guide I wrote once for easily adding stunnel to a MUCK: make a key/cert with this command: openssl req -new -x509 -nodes -out stunnel.pem -keyout stunnel.pem mv stunnel.pem /etc/stunnel/ make a stunnel.conf with the following text at /etc/stunnel/stunnel.conf: cert = /etc/stunnel/stunnel.pem [stelnet] accept = insertporthere connect = 7777

>>2199 >>2192 SSL is now running on port 7797.

>>1800 If people are having issues starting out: 1. Type "help" after creating a character. Especially "help movement" - you will get a list of topics. The help system is very large, not at all like other mud systems you may be used to. 2. After getting the hang of the interface, go north. Remember that you can look at things. Look at the sign. Look at the bum. 3. "examine thing" allows you to get a list of "obvious verbs" - that is the things one may do to or with the object you are examining. Remember that rooms and players are objects and that "here" and "me" are valid aliases for the current room and the player object you are controlling, respectively. 4. If you are utterly lost and confused, either "page whiteline with <message>" or, if I'm not about, "@send whiteline" to send me a message via the internal mail system.

>>1800 Also i guess that got bumped off the main catalogue list... but the address is 107.170.21.35 port 7777

Hey OP, I just want to thank you for this. I've been looking for a game to play on my phone that would actually appeal to me. I can't wait to dive in!

>>1800 Have fun! ^_^

I am trying to create a way for people to build off of the "starting area" without having to ask questions first since I felt that this was a requested thing. Due to the permissions system this is somewhat tricky to implement. One is able to drop locked portal objects - see the yellow taxi cab for how to implement portal functionality - and the room owner can always eject things so that solves itself, rather. What would be required, besides solving the permissions issue, is to create a room with decorator code that appends exit descriptions to the room into the room description and then create an exit subclass with an appropriate msg property that holds that description. The normal locks would prevent the exit from being modified and the room description from being vandalized - you normally want people to add things to other people's work and not modify it, after all - wiki style functionality would be possible but too expensive and complicated to implement - and I think the existing code would prevent people from adding exits with the same name or alias as an existing one but I'd have to check. Anyway, just thinking out loud - I'm currently working on an object pool class with demonstrations for people who might not be good enough at coding to think to implement one. Recycling and creating is cumbersome but object pooling via re-parenting and then deleting all defined properties upon "recycling" is very efficient under the LambdaMOO data model.

I've made a "heavy thing" object, which can't be picked up. it might be of use to people creating their own objects. You can make a heavy thing like so: @create #230 named Mjolnir @heavy Mjolnir is "It does not budge. You are not worthy." The implementation of #230 is pretty short, and shows how to override the generic get/take verb: @create $thing called heavy_thing @property heavy_thing.heavy_msg "This is far too heavy to pick up!" @verb heavy_thing:heavy_msg this none this @program heavy_thing:heavy_msg return this.(verb); . @verb heavy_thing:"g*et t*ake" this @program heavy_thing:take player:tell(this:heavy_msg()); . @chmod heavy_thing rf

>>2401 (forgot to mention) The advantage of a heavy_msg verb and property is so that you can set the property if you just want a constant string, or override the verb if you want something fancier.

>>2401 I realised there was a much better way to do what I wanted to do. The purpose of the heavy objects was to make it possible to add descriptive features to a room which can't be picked up and carried off: => look The Reading Room The walls are covered in bookshelves, with no windows or doors in sight. All light in the room comes from a single bright lamp in the corner. In the centre of the room is a mahogany table, between two leather sofas. A tattered rug protrudes from beneath the table. There is a faint smell of dust and old paper. You see a lamp, a table, a rug, and two sofas here. => look lamp The lamp really is fearsomely bright. Probably best not to look at it directly for too long. But this isn't ideal, as every descriptive feature in the room is listed twice: once in the description and once in the object list. A much better way to do it is to add descriptive features to a room, which are not objects, but still work with look. So that's what I did. I have a prototype "generic_rpg_room" as object #234, if other people want to build off it. => look The Reading Room The walls are covered in bookshelves, with no windows or doors in sight. All light in the room comes from a single bright lamp in the corner. In the centre of the room is a mahogany table, between two leather sofas. A tattered rug protrudes from beneath the table. There is a faint smell of dust and old paper. => @detail fairy,leprechaun as "It smiles at you strangely. Why is it here?" A fairy pops into existence. => look The Reading Room The walls are covered in bookshelves, with no windows or doors in sight. All light in the room comes from a single bright lamp in the corner. In the centre of the room is a mahogany table, between two leather sofas. A tattered rug protrudes from beneath the table. There is a faint smell of dust and old paper. => look leprechaun It smiles at you strangely. Why is it here? I'm planning to add more interaction to the generic_rpg_room, like being able to smell things, or sit in chairs.

>>2423 This exactly - this also works for more complex things like maze rooms which limit visibility to things which share a coordinate with another object.

>>2423 Also you must set your object @chmod #234 +f if you want others to be able to inherit from it.

>>1800 A list of all objects intended for public derivation have been instated in a room twice north from the starting point, for reasons of discoverability. If you have made any objects, add them to this list.

>>2564 Could I have the object number of the starting room pls? I locked myself in a room with no exits and @sethome to it ;_;

>>2587 oh dear, sorry >_> The room with the bum is #97

>>2602 <3 thanks a lot senpai

hey so is this multi player? it looks cool as heck.

>>2624 Yeh, is. And yes, it is cool. ^_^

>>2602 >>2614 So I added an exit from my isolated room to the "lobby" (or, the Utility room). I am wondering if it'd be possible to have an exit lead to a random room from an array. Or an object teleport likewise. Do you know if any of that i spossible, admin-senpai?

>>2624 >>2626 i just connected and signed up. im in the store room, come say hi lol this makes me feel like a teenager again, discovering the internet

>>2628 Yes, as long as the exit is blessed by the room or set to free entry, which rooms are by default you may code any sort of system that uses player:moveto(room) to move the player anywhere.

Bump since I enjoy it, and both .org and .jp can enjoy it too.

>>2932 Sorry for non-activity tbh, my grandma passed away and it's gonna be a bit hectic for me for a while.

Glorious bump for glorious new domain name, lain.codes, courtesy of TheStranjer. Also more activity, probably.