Can a character with the Actor feat mimic speech they heard before they learned the feat?

The Actor Feat:

You can mimic the speech of another person or the sounds made by other creatures. You must have heard the person speaking. or heard the creature make the sound, for at least 1 minute.

If a player learns this feat at 8th level, can they mimic speech they heard back when they were first level and did not have the feat?

What about a speech heard 200 years ago when they were but a small elven child?

RAW, I think it’s allowed. And I don’t think it breaks the game to allow it. But I’m curious if there are any aspects of this that I’m missing. I would assume that for the 200-year old speech, that it would at least have to have been memorable in some way! 🙂

Can the Actor feat allow a character to effectively speak a language they don’t know?

I have a player in my game I’ll call “Joe” running a Bard I’ll call “Hansel.”

Hansel has the Actor feat, and does not speak Orc. Hansel listened to an Orc for 1 minute a few adventures ago, a 2nd PC taught Hansel one short Orc phrase, and I allowed Hansel to repeat the new phrase, in Orc, mimicking the voice of the Orc Hansel had just listened to.

Joe has recently expanded this to insist that if the 2nd character now says several Orc phrases over the course of a minute, Hansel can repeat each phrase at will, mimicking the voice of that Orc. Joe believes that Hansel can also rearrange the words to create new phrases, on the fly in conversation with Orcs – and that this can also fool any Orc into thinking it is an Orc from their own War Band, so long as there is a door there to muffle the sound.

Joe claims that anything short of meeting this demand undermines the entire usefulness of the Actor feat, and therefore robs his character of 4 levels worth of adventuring.

Can the Actor feat allow a character to effectively speak a language they don’t know?

I think Hansel could mimic a specific Orc’s voice, after 60 sequential seconds of listening to it speak consistently (though not necessarily persistently), but only using languages Hansel already knows.

What are the correlation between Actor model and Reactive Programming

Could anyone explain the difference/correlation between the Actor model and Reactive programming?

It seems that they are located at different levels of abstraction – one can design the interaction between the components of any distributed system using Actor approach, they would send messages, and inside the actors, write code in reactive style?

this question related to How do Functional Reactive Programming and the Actor model relate to each other?

However, the answers wasn’t clear enough, and my question relates reactive programming in general, not FRP in particular.

How to get the actor to follow the mouse while clicking and holding?

I am trying to do the top down project from scratch.

I can already get the actor to move toward the mouse click:

enter image description here

Only I need to keep clicking several times to change its path and keep walking indefinitely.

I would like to know how to keep it moving while I hold the mouse button.

In the previous version (4.21) this code below fit perfectly, so I managed to do that (the condition was a variable that only became false when I released the mouse button):

enter image description here

But now I can’t make this connection (4.22).

I searched for some functions and even searched the new documentation for this loop (While Loop), but nothing worked.

Link (While Loop BP UE4):

https://docs.unrealengine.com/en-US/Engine/Blueprints/UserGuide/FlowControl/index.html#whileloop


Player Blueprint:

enter image description here

What are the ways to trigger Root Actor from Rest controller?

I am new to Akka, so not sure if this is an easy question. My current setup is something like this : I have a Rest Controller, which is getting lots of requests from different hosts. These requests then get queued into a common queue. From where they are dequeued by 4 worker threads. As the scale increased, this model started failing. Instead of creating and managing these threads and queue, I want to replace it with Akka model.

In the new model, I will have a RootActor, which will have different child actors based on type of request. Now where I am currently struggling is how to ‘send message’ to RootActor, whenever the RestController receive requests. In short, I am trying to interact with RootActor from outside of the ActorSystem. Couple of ideas which I thought about :

  1. Make RootActor itself a Controller. But that looked like coupling different concerns together.
  2. Use some Message Queue. Controller will keep pushing events on one side, Actor can keep listening to them from the other side.

Is there any other standard way to do this? As much as I searched, couldn’t find anything like this (which is suggesting I’m approaching the problem in the wrong way?). Any helpful links or design practices would be great. Thanks in advance!

Same Actor with multiple roles

What is the best way to represent two actors, of which sometimes it could be the same person?

I have a case where we have approver 1 and approver 2. In most instances, #1 approves and it flows to #2. In other instances, #1 and #2 are the same person, so they can act as both.

I tried drawing a box around the two actor icons.

Storing history in an Actor Model

Being a complete noob to the actor model way of doing things, I a struggling to understand how I would store transaction history in an Actor Model. In the example from ProtoActor Persistence (https://github.com/AsynkronIT/protoactor-dotnet/blob/dev/examples/Persistence/Persistence/Program.cs) the child actor produces a bunch of random names like this:

public Task ReceiveAsync(IContext context) {     switch(context.Message)     {         case Started _:             context.Self.Tell(new LoopParentMessage());             break;         case LoopParentMessage msg:             Task.Run(async () => {                 context.Parent.Tell(new RenameCommand { Name = GeneratePronounceableName(5) });                 await Task.Delay(TimeSpan.FromSeconds(2));                 context.Self.Tell(new LoopParentMessage());             });             break;     }      return Actor.Done; } 

And the parent then updates it’s state like this:

private async Task Handle(RenameCommand message) {     Console.WriteLine("MyPersistenceActor - RenameCommand");     _state.Name = message.Name;     await _persistence.PersistEventAsync(new RenameEvent { Name = message.Name }); } 

The question is, in an actor model, how should I store and retrieve a list of the previously generated names to display to the user.

Do I just store them in a separate database table? That seems a bit wasteful because I have already stored the events in the Event Store. So then should I use the Event Store as the journal? That also feels like I am mixing concerns of the events.

Another way of asking this: If I have a bank account modeled as an actor, how should I store the transaction history so that I can show it in the UI and not just the current balance?