Noob666 wrote:So you think almost nobody would need change owner inside lifetime of the room and so it is ok?
Well, this is the first time it's been asked. In 8 years.
Can you explain why it is important? This way we can see how we can help.
What other features must be reimplemented
I don't understand your question. I did not say that you have to re-implement anything.
What I said is that SmartFoxServer comes with a default Room management system which implements a few basic rules, which can be learned here.
http://docs2x.smartfoxserver.com/Develo ... chitectureIf those rules don't suit your game logic you
can simply bypass the automatic management, and decide when Rooms should be removed via server side coding.
We need product, which will help us in maximal amount of features, so we can concentrate on game logic and not product that will force us every single feature reimplement by ourself.
Room management is actually part of the game logic, since your game rules dictate how Rooms will be created and destroyed.
We provide an all-purpose Room management that covers some of the basic usages, but we can't cover every single possibility. In addition we provide high level API that allow you to control the creation and destruction of said Rooms.
Such product is useless for us, sorry. You will be happy, if you buy car and you will uncover, that you cannot use built-in rear-view mirror and you must manufacture your own? Me not.
I think there's a gross misunderstanding here, and I've explained why.
This is not a case of a rear-view mirror not working. We provide a rear-view mirror that behaves exactly as you'd expect in 90% of the use cases. Still, if your use case is not covered you're given high level API to control the mirror and customize it's behavior with very few lines of code.
Also it's not clear why you're immediately jumping to rash conclusions, when you haven't even explained what kind of use case you're working on.
We're here to help, if you let us