Dialogue NPC Script

Put the scripts in these places, with names matching exactly, capitals included: DialogueConfig (ModuleScript) inside a folder named DialogueSystem in ReplicatedStorage DialogueData (ModuleScript) and DialogueServer (Script) in ServerScriptService DialogueClient (LocalScript) in StarterPlayer > StarterPlayerScripts

Select any Model or Part, add a string attribute called DialogueId, and set it to a name from DialogueData (like Guard). A “Talk” prompt appears automatically.

Almost always a naming problem. Check the script names and types (DialogueServer is a Script, DialogueClient is a LocalScript), and check the attribute name and value are spelled exactly. The Output window warns you if a DialogueId doesn’t match anything in DialogueData.

Yes, give them the same DialogueId. Each player has their own conversation, so several players can talk to the same NPC at once.

The server controls the conversation and checks every choice (valid option, player nearby, anti-spam), and your dialogue data is never sent to clients. Your own Action functions run on the server, so write them as carefully as any other server code.

Not by default. Flags are kept in server memory while the player is in the server. To make them permanent, save and load them with a DataStore where DialogueServer sets up the flags table.

Everything is in DialogueConfig: colors, font, text size, typing speed, typing sound, prompt key, distances, and whether to freeze the player while they talk.

Yes, with Action functions on a node or a choice. The Merchant example takes coins from leaderstats and the Guard example sets a quest flag.