Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - quixadhal

Pages: [1] 2 3 ... 43
Open Chat / Re: Quick and Easy MediaBox
« on: December 09, 2017, 11:42:47 AM »
Is there a popular digital tuner card that works well for such things these days?  I think I had a "happague" back in the days of analog TV, but these days you'd need a card with multiple digital tuners to be able to properly take the place of a tivo device.

Also needs to cost less than a tivo. :)

Code Vault / Re: New RealmsMUD core library
« on: December 08, 2017, 09:14:50 AM »
I just put all my stuff on github.  You can manage your local repository with whatever system you like and push a copy to github for "release" whenever you want.  No need to actually USE github for anything beyond a public repository host.

Open Chat / Re: Elder Scrolls Online
« on: October 07, 2017, 01:40:17 AM »
There are always dungeons that need doing.  I think I have a quest for the Undaunted guild that needs me to go into Spindleclutch, normally a 4 man dungeon.

Open Chat / Re: Elder Scrolls Online
« on: October 05, 2017, 11:19:43 PM »
The nice thing about TESO is that everything level scales, so you don't need to be any particular level range to play together.  I'm just working my way through the Glenumbria content, trying to remember to actually do some crafting research.  Not a big dungeon person though... not adverse to trying one, but the only game I ever did casual dungeons as a normal daily thing was World of Warcraft back in the Lich King expansion.

Drivers / Re: Link for repository of fluffos-2
« on: September 15, 2017, 11:16:52 PM »
I'm not sure how much more clearly I can possibly state this.

Code: [Select]
tar xvf dw_fluffos_v3.tar.bz2
cd dw_fluffos_v3
git clone fluffos_quix
git clone fluffos_carter
cd fluffos_quix/src
... adjust local_options to work for discworld ...
make install
cd ../../bin
... adjust dw.cfg ...
cp -p ../fluffos_quix/bin/driver .
cp -p ../fluffos_quix/bin/addr_server .
cp -p ../fluffos_quix/bin/portbind .
cd ../lib
... adjust a couple of well-known issues in the mudlib LPC files ...
cd ../bin
./addr_server 4999 &
./driver dw.cfg &
... telnet to game, verify that commands work and I3 connects, chat on I3, shutdown game ...
... kill addr_server process ...
cd ../fluffos_carter/src
cp -p ../../fluffos_quix/src/local_options .
make install
cd ../../bin
mv driver driver.quix
mv addr_server addr_server.quix
mv portbind portbind.quix
cp -p ../fluffos_carter/bin/driver .
cp -p ../fluffos_carter/bin/addr_server .
cp -p ../fluffos_carter/bin/portbind .
./addr_server 4999 &
./driver dw.cfg &
... telnet to game, notice that I3 connects, but all commands are queued ...
... kill driver and addr_server processes ...

You see what I'm getting at here?  ZERO CHANGES to the mudlib.  ZERO CHANGES to the local_options file.  CLEAN BUILDS of the C and C++ versions.  C version works, C++ one does not.

Now, if you want to leave fixing it as an exercise to the reader, that's perfectly fine.  I'm simply trying my best to report that this is a bug, a change in behavior, between the C version of the driver and the C++ one.  If this isn't clear enough to convince you that I'm not an idiot and did indeed plug the power cord into the wall, I don't know what else to do. :)

Drivers / Re: Link for repository of fluffos-2
« on: September 12, 2017, 04:41:46 PM »
The post I found said they fixed their problem but never elaborated on HOW they fixed it.

There may well be a workaround in the LPC code, but I assumed you were aiming for the driver to be a drop-in replacement for the older C version.

For my test case, I unpacked the discworld lib, compiled the driver from my own git repository (version 2.27.2), and verified that it worked, connected to I3, and I could walk around and do a few basic things.  Then I compiled the newer C++ version of the driver using the same local_options files and booted the same mudlib, in place, with that newer driver.  The result is that it boots, connects to I3, but logging in results in "Command Queued" no matter what you type.

Since the mudlib code has not changed, and the configuration has not changed, this must be a change in the driver's code, somewhere.  Since it has to do with delays, my initial guess is that it might be related to the posix timer stuff, but that's just a guess.

Drivers / Re: Link for repository of fluffos-2
« on: September 12, 2017, 05:26:57 AM »
It's a change in the driver behavior... for good or bad, I don't judge.  However, I'm using the exact same mudlib on your driver that I'm using on the old 2.27.2 driver.  What Discworld uses to do its "queued command" logic, I don't know... but whatever it is, the driver is acting differently.

Drivers / Re: Link for repository of fluffos-2
« on: September 09, 2017, 06:27:30 PM »
Almost there!

Compiles fine, boots up, connects to I3, I can log in, however every command now shows up as a "queued command" and never actually executes.

I vaguely remember this being commented on elsewhere, perhaps in the discworld section of the forums even.  I'll try to poke around a bit later and see if I can find it, if you don't beat me to it.

Drivers / Re: Link for repository of fluffos-2
« on: September 09, 2017, 04:35:21 PM »
Just a quick bug report.  In trying to boot the ancient discworld mudlib, I get an "undefined function stringp" while loading the sefun object.

Code: [Select]
/secure/simul_efun/add_a.c line 40: Undefined function stringp before )
No error handler for error: *Error in loading object '/secure/simul_efun/add_a'
program: (none), object: (none), file: (none)
The simul_efun (/secure/simul_efun) and master (/secure/master) objects must be loadable.

The local options file used:

and the runtime config file:

The same options and config files worked on my older version of fluffos 2.x, so there's that. :)

Drivers / Re: A sad day in history - FluffOS-3
« on: September 05, 2017, 02:33:52 AM »
As I recall, the original reason FluffOS 3.x was forked from FluffOS 2.x was an unwillingness to allow the maintainer of Discworld to verify that the series of changes being worked into the driver wouldn't destroy a game with an active population in the thousands.

So, it's not so much that Discworld has no desire to migrate to a newer driver, it's that they had no desire to move to a rapidly moving target which showed no interest in maintaining compatibility with any game other than the one they, themselves, were running.

Now, there's no requirement to keep everything 100% backwards compatible.  FluffOS itself, when it was MudOS, broke things on a somewhat regular basis.  The difference is that during MudOS's evolution, compatibility issues were detected and described in the patch notes as each new revision was released, giving MUD admins the information they needed to fix their mudlibs, or decide to remain at the older version.

I'd like to think everyone has the same overall goals here... to try and improve the game driver for as many people as possible.  Since what's done is done, the only useful way forward now is to try and identify what things have been broken and determine if fixes will be simpler in the driver, or in the mudlib(s).

If I'm wrong, then perhaps a new name for the driver would be appropriate.  Afterall, MudOS became FluffOS because the maintainer of MudOS showed no interest in making the changes the Discworld people needed for their game to grow.

Open Chat / Re: Elder Scrolls Online
« on: September 05, 2017, 02:19:30 AM »
I have an xbox one, but won't play any games where a keyboard/mouse is superior.  Which rules out MMO's and FPS games.  Driving games, XCOM, Diablo... all better on the console, in the comfy chair!

Open Chat / Re: Elder Scrolls Online
« on: September 04, 2017, 07:36:45 AM »
If you ever wander to the side of the PC Master Race, I'm pondering a shiny new templar build to be able to slowly solo but never die. :)

Open Chat / Re: Elder Scrolls Online
« on: August 30, 2017, 02:22:57 PM »
I play on the PC version.  Since they can't do cross-platform, I'm not likely to do anything on the console versions since I already have time and money invested in the PC.

Drivers / Re: which driver would you use?
« on: August 09, 2017, 04:45:49 AM »
I would probably pick DGD, although LDMUD is a nice and well polished driver too.

It boils down to what kinds of features you want moving forward.  DGD puts a lot of effort into supporting persistence, with state dumps and atomic functions, so if that sounds like something you might want to use, it's a clear winner.  If not, it's still a nice fast and small driver.  Dworkin's philosophy has been to try to keep features that can be done in LPC out of the driver, so it can remain efficient and manageable.

LDMUD is far closer to LPMUD 3.1.2, and has a history leading back into the Amylaar driver.  It has lambda closures and seems pretty solid, although there aren't many mudlibs publicly available as examples.  I know BatMUD runs on it.

FluffOS is probably my last choice for the simple reason that it's currently not really maintained, and has some issues.  However, there are quite a few mudlibs available out there to use as comparisons to see what you'll need to change in your own.  If you do pick that one, the 2.x branch is the stable and not-really maintained version that you will likely want.  The 3.x branch was spunoff to try and convert to C++ and has evolved to be incompatible in many ways.

Open Chat / Re: Merry Christmas and a happy New Year!
« on: July 23, 2017, 11:39:40 PM »
Christmas in July?

Pages: [1] 2 3 ... 43