Looks like it's going in a good direction -- good luck!
On Sat, Oct 8, 2016 at 6:24 PM, Steve Winfield wrote:
>
>
> Am Samstag, 8. Oktober 2016 22:09:46 UTC+2 schrieb Justin du coeur:
>>
>> (Although my first impression is that I'd probably use a repeated
>>
Am Samstag, 8. Oktober 2016 22:09:46 UTC+2 schrieb Justin du coeur:
>
> (Although my first impression is that I'd probably use a repeated
> schedule, and on each call decide whether to stop, rather than a lot of
> scheduleOnce's.)
>
Players are not always moving and I guess (!!) that a
On Fri, Oct 7, 2016 at 6:35 PM, Steve Winfield wrote:
> What do you think about it? (it's calling
> context.system.scheduler.scheduleOnce
> for every step - too much?)
>
Honestly don't know -- I don't use the scheduler heavily myself. I'm sure
that at *some*
Am Freitag, 7. Oktober 2016 22:06:26 UTC+2 schrieb Justin du coeur:
>
> When the player wants to move, the Player Actor sends an "I'd like to move
> to X" message to the Space Actor responsible for that location, and the
> Space returns either a "yes, go ahead, you now own that position" or
So this:
On Fri, Oct 7, 2016 at 11:28 AM, Steve Winfield <
mail.stevewinfi...@gmail.com> wrote:
> I want everything to be synchronized
>
is something you basically have to give up -- global synchronization is
fundamentally contradictory to the Actors view of the world. Mind, though,
it doesn't