bladedpenguin

Thanks, I had updated this behavior. I first change angle(radians) to clamped degree which is 0~360, then get average of degree. Finally turn back average degree to angle(radians).

Savvy001

rex_ann plugin is a tool for AI, not for building any kind of neural network, sorry.

Actually, it is hard for normal user. So this plugin is not valuable.

xoros

If your requirement is a multiple dimension dictionary only, you might try Yann's JSON plugin, and put instance's uid at first level key.

For example

root

• uid:1

-- hp: 100

-- mp:60

• uid:2

-- hp: 20

-- mp: 7

And remove dictionary of uid while instance had been destroyed.

If you need querying, you might wait for my database plugin. It is also a multiple dimension dictionary, too.

Update

Add expression: A, n, B, m.

Display Parameters A,n,B,m on debug panel.

TiAm

I had merged them, thanks for sharing.

But I changed expression name Param_A to A, Param_n to n, Param_B to B, Param_m to m.

I am trying to make taffydb plugin recently. Hope it would be useful.

Type name will be minified while exporting. So you need to have another name-reference mapping by actions in event sheet.

I had made rex_nickname plugin which could create instance by a string name.

User need to link the string name and the object type by action before using it.

lukasal00

Sorry, I don't have time for this example recently.

You might try PM to jomo who is a C2 teacher, he could provide high quality tutorials for your requirements.

Firebase is a cloud data service. And it could broadcast data to all listeners (clients).

Ajax, php, MySQL only could polled requests from clients, server does not have ability to send notification to any clients, this is not the same with firebase, imo.

Ashley

The issue is not "cookie cutter" feature or "general-purpose", or event-base behavior.

The issue is "how to reduce programming cost":

• "cookie cutter" means users will program with pure events if they need new feature.
• "general-purpose" means users might add some or a lot of events to match their requirement.

( Some time they will never get it, so they will ask pure event-base behavior, I do not agree official plugins are "general-purpose" already, since users still could not reach their targets. )

• "pure event-base behavior" means a lots of events.

The better solution will reduce events in all cases.

A possible solution is start at pure event-base behavior-- "how does users modify it for new features?" Then breaking it into plugins(behaviors). Finally it will be a plugins-system which left some hooks for users to add new feature by events or by plugins-- It is not a single plugin or behavior, it is a reuse-able architecture.

Do not trapped by "single plugin/behavior", this kind of solution does not have enough flexible. Sprite(plugin) could have behaviors like extending slots/decorators, how about behaviors' extending slots/decorators?

I would build chat app with firebase service. Here is a demo.

You might try it.

https://github.com/rexrainbow/C2_plugin ... ime.js#L97