Essentials bug please help :D (FIXED)

Status
This thread has been locked.

Doughnut

Entrepreneur | Electrician| Financial Help
Premium
Feedback score
32
Posts
1,298
Reactions
466
Resources
0
Ok, Title says it all. When a player connects for the first time. They get a mesage. saying Welcome XYZ to the server (The player number that has connected) It should only send it the first time. This sends it everytime they connect. Any ideas?
 
PebbleHost
High performance, consistent uptime and fast support. Minecraft hosting that just works.

1AndOnlyGod

Feedback score
7
Posts
197
Reactions
13
Resources
0
Change the custom join message
 

Court

Freelance Developer
Supreme
Feedback score
16
Posts
129
Reactions
103
Resources
0
Not sure if Essentials tracks the number of players. I might be wrong though.

JeboSetups, Essentials tracks the unique players who have joined using {UNIQUE} configuration tag. It also checks how many players are online using the {ONLINE} configuration tag.


Ok, Title says it all. When a player connects for the first time. They get a mesage. saying Welcome XYZ to the server (The player number that has connected) It should only send it the first time. This sends it everytime they connect. Any ideas?

Doughnut, check if your join message includes {UNIQUE}.
 

Ayiu

(⌣_⌣”)
Feedback score
4
Posts
69
Reactions
13
Resources
0
Ok, Title says it all. When a player connects for the first time. They get a mesage. saying Welcome XYZ to the server (The player number that has connected) It should only send it the first time. This sends it everytime they connect. Any ideas?
Try checking the custom join message input, and see if it has {UNIQUE} as I court said. Then check the first join part of the config.
 

Doughnut

Entrepreneur | Electrician| Financial Help
Premium
Feedback score
32
Posts
1,298
Reactions
466
Resources
0
JeboSetups, Essentials tracks the unique players who have joined using {UNIQUE} configuration tag. It also checks how many players are online using the {ONLINE} configuration tag.




Doughnut, check if your join message includes {UNIQUE}.
Try checking the custom join message input, and see if it has {UNIQUE} as I court said. Then check the first join part of the config.
Sorted, The issue was. I had the UNIQUE part however the playerdata was not saved in the correct folder. I just had to move it.
 
Status
This thread has been locked.
Top