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 - FallenTree

Pages: [1] 2 3 ... 33
Drivers / FluffOS in 2019.
« on: December 31, 2018, 02:03:12 AM »
Hello long time friends, happy holidays! I just want to post an update on FluffOS.

During the course of 2018 there have been a few patches here and there , and some slow progress converting build system to cmake.  Here is the plan for 2019 onward.

1. Master branch will start receive active development, mostly 2 features: Cmake build system support, Integration with NodeJS via N-API, with Javascript interop.
2. v2017 branch will not receive build system upgrade, and will continue receive BUG fix support until new version is ready for general use.

So, there will be 2 supported version in 2019.  *FluffOS will always remain backward compatible*.

If you found an compaitibilty issue, please raise an issue at

FluffOS's primary website will be hosted at and primary discussion forum will be at

Open Chat / Re: Elder Scrolls Online
« on: October 02, 2017, 03:11:11 PM »
I have a account on NA server, @fallentree if anyone want to play together.

Drivers / Re: Link for repository of fluffos-2
« on: September 12, 2017, 08:39:02 PM »
@quixadhal, are you talking about the latest fluffOS-3.0.20170907 version ?

It's definitely not about posix_timers because all that does is for max_eval.  If you see anything in /log/debug.log  that might be more useful.  I may give it a try in next few weeks to see how to make it work.

Drivers / A official statement of FluffOS 3.0
« on: September 07, 2017, 12:57:48 AM »
Status of FluffOS 3.0: FluffOS 3.0 (last release fluffos-3.0-20170831) is actively used by a few big chinese MUDs actively, right now. The primary channel for discussion is via an QQ group .  (a Chinese IM software). I am actively refactoring codebase and fixing any bugs reported anywhere. It's a living driver, with no big issues.

As for the other Libs and general direction of the driver codebase,  this is my statement:

1. The driver will have a rolling release, there will only be 1 version supported at anytime.  No patch will be backported into old releases. If you want to ride the train, then you have to stay with the train, try to migrate to latest version as soon as possible, otherwise it maybe difficult to do so later. (although very few breaking changes are going to be added anyway).
2. The driver will be mostly an runtime config based configurations style. Meaning there are a few knobs in the config file you need to tweak, very very few #define will be added.  That means also you won't need your local_options anymore, just keep your config file.
3. Anything (EFUN, features guarded by runtime config etc) is welcome to be added to the driver,  as long as it has reasonable coding standard and an basic tests.

If you have a lib, and you want to ride the fluffos 3.0 train, you are welcome to do so, I personally will help you find solution for any issues you might encounter during the transition.
If you have a lib, and you don't want to migrate to fluffos 3.0 , that's also fine, no one will force you to migrate, ever. Just ignore FluffOS3 and be happy.

The primary way to reach me is by creating a issue at  .


Drivers / Re: A sad day in history - FluffOS-3
« on: September 05, 2017, 01:14:07 AM »
The fact is that it hasn't been working for discworld + FluffOS 3 for a very long time. And I still says that if you want to make it work, I can help. Just work with me on the github instead of yelling it here.

Drivers / Re: new driver development.
« on: September 05, 2017, 01:11:47 AM »
TBH, I didn't say I won't add support for older libs in FluffOS3, In fact, all compatibility issues that ever been raised on GITHUB already has a solution, I'm not sure what the exact issue is.

All in all the driver is generally going towards an configuration based instead of compile options based system, which make it possible for people to pair an generic driver with some runtime config and run all the old mud.  If there are some specific active MUDs that want to try to transit to FluffOS 3 , I'm willing to work with you and support them. 

Please submit your question with specifics on the github, instead of just say, stuff doesn't work.

Drivers / Re: which driver would you use?
« on: August 17, 2017, 05:51:19 PM »
Please submit issues you encountered in FluffOS 3.0 to


Drivers / Re: new year resolution
« on: January 13, 2016, 04:17:31 AM »
To me it seems that all we need to do is to bridge with nodejs, it will solve all extension problems.

Drivers / Re: new year resolution
« on: January 08, 2016, 07:03:10 PM »
I'm pretty disappointed that no one decide to write anything, maybe it is not the correct forum for such discussion?

Drivers / new year resolution
« on: December 30, 2015, 11:45:18 PM »
hi all, let's write something you wish to happen to fluffos/mud in 2016


Drivers / Re: WIP: Fluffos 3.0 Alpha 9.0
« on: November 28, 2015, 03:37:28 AM »
I assume there are no more crashes?


Drivers / Re: WIP: Fluffos 3.0 Alpha 9.0
« on: November 24, 2015, 05:19:36 AM »
o yeah, the wonder of broken attacker!

Drivers / Re: WIP: Fluffos 3.0 Alpha 9.0
« on: November 23, 2015, 08:31:29 AM »

First: I think this is caused by broken client, not a server side problem (although we certainly can do better than crashing..)

This is a very interesting problem: I have a workaround checked in , but I want to you do do something with the core, to verify something for me.

Here's how: use gdb driver core , use bt to find stack that belongs to "", and use "f X" to select that frame:

> print ip->local_port
> x/4ub ((in_addr*)&((struct sockaddr_in*)&(ip->addr))->sin_addr)->s_addr
> x/36xb buf

First command will print out the port it connected to,  second command prints out IP address,   the rest will show me the whole packets.

Here is what I found: The port is 8000,  remote ip address is in "208.100.*",  and raw data look like this

(gdb) x/36xb buf
0x7fff4271eff0: 0xff    0xfc    0x22    0xff    0xfa    0x22    0xff    0xf0
0x7fff4271eff8: 0xff    0xff    0xfc    0x03    0xff    0xfc    0x18    0xff
0x7fff4271f000: 0xfc    0x1f    0xff    0xfc    0x27    0xff    0xfe    0x56
0x7fff4271f008: 0xff    0xfc    0x5b    0xff    0xfe    0x46    0xff    0xfe
0x7fff4271f010: 0x5d    0xff    0xfe    0xc9


Also, don't forget to try the latest fix :-p

Drivers / Re: WIP: Fluffos 3.0 Alpha 9.0
« on: November 19, 2015, 09:50:22 PM »
How come your core size is so big......How much memory do you have?

hmm, your crash looks different than what I have been hearing. I will take a look early next week.

Pages: [1] 2 3 ... 33