Corescripts with the renders

[FagaBV]

Describe the problem

No corescripts folder in site/

Describe the proposed solution

Hi!

I've succesfully followed the tutorial from the readme page [great one tbh], on a local server and it works with no problem.

I got everything set up, and after that i saw that the avatars do not load, i tried to look in the configuration and i saw that it searches for site/corescripts [folder that it's not on the repo], with the renderavatar.lua [for the avatars], is it uploaded somewhere and i didn't see it? or we need to script it from scratch?

[the1ev234]

https://github.com/tp-link-extender/2013 turn the luau files to lua

[FagaBV]

And to do that I need to clone the repo from TP-link-extrnder/2013 and go to compile and run the go from there?

I haven't done anything like this so idk

https://github.com/tp-link-extender/2013 turn the luau files to lua

[Heliodex]

The process is in the process of being documented due to recent changes to how corescripts are loaded, but the gist of it is the following:

1. Use the version of Mercury Core on the assets branch for now
2. Clone tp-link-extender/2013
   • This contains corescripts suitable for the 2013 client & studio, as well as render scripts suitable for 2015 RCCService. These will probably need to be modified to fit your environment if you have different versions.
3. Install darklua as a command-line tool, or install aftman/rokit and run the install command in the 2013 directory, which will install darklua for you
   • We're planning to remove the dependency on darklua for Luau-to-Lua compiling soon, though it works fine for now.
4. The compile directory contains the compiler, run go run . from there, which will compile the corescripts & loadscripts and copy related assets into the out directory
5. The out directory will contain out/server. Open the Mercury Core repository and place this folder into the data directory, as data/server.

We're planning to release the documentation site soon which will contain a more in-depth guide on how to set up corescripts.

[FagaBV]

Thanks for the info, got it working pretty much, but still for the render it doesn't work as it doesn't have an RCCService [i guess] running on the port.

Here's the error I get every time on the dev server {bun dev} :
error: Unable to connect. Is the computer able to access the url?
path: "http://localhost:64990/3hsn25cp8rh3otsf68m0",
errno: 0,
code: "ConnectionRefused"

9/29/2025, 9:14:12 AM ZBX POST /user/ZBX?/rerender
9/29/2025, 9:14:12 AM ZBX GET /user/ZBX
9/29/2025, 9:14:12 AM ZBX GET /api/avatar/ZBX?r=0.8666481936529877
9/29/2025, 9:14:12 AM ZBX GET /api/avatar/ZBX-body?r=0.7804827346625417
9/29/2025, 9:14:27 AM ZBX POST /user/ZBX?/rerender

I also tried to do it in the build server, but there i don't get any error but neither a render

The process is in the process of being documented due to recent changes to how corescripts are loaded, but the gist of it is the following:

1. Use the version of Mercury Core on the assets branch for now

2. Clone tp-link-extender/2013

   • This contains corescripts suitable for the 2013 client & studio, as well as render scripts suitable for 2015 RCCService. These will probably need to be modified to fit your environment if you have different versions.

3. Install darklua as a command-line tool, or install aftman/rokit and run the install command in the 2013 directory, which will install darklua for you

   • We're planning to remove the dependency on darklua for Luau-to-Lua compiling soon, though it works fine for now.

4. The compile directory contains the compiler, run go run . from there, which will compile the corescripts & loadscripts and copy related assets into the out directory

5. The out directory will contain out/server. Open the Mercury Core repository and place this folder into the data directory, as data/server.

We're planning to release the documentation site soon which will contain a more in-depth guide on how to set up corescripts.

[the1ev234]

we also need to setup the proxy server, which the link is barely in the docs
https://gist.github.com/Heliodex/639fea9aa7808a7d9cf9c1ed4cfc4eff
also we need a .env file with this
IP=::1
ENDPOINT=http://xtcy.dev/api/render/update

[Heliodex]

A newer version of the proxy server can now be found at tp-link-extender/RCCService/Proxy. I'll continue work on documenting it and adding a setup tutorial soon, which should also help with #356 and #405.