Client-Side Releases
142 topics in this forum
-
- 21 replies
- 54365 views
-
- 103 replies
- 111848 views
-
- 75 replies
- 83037 views
-
- 538 replies
- 242566 views
-
- 114 replies
- 101437 views
-
- 490 replies
- 199795 views
-
- 403 replies
- 649805 views
-
- 0 replies
- 770 views
-
- 0 replies
- 841 views
-
- 6 replies
- 4961 views
-
- 19 replies
- 13485 views
-
- 0 replies
- 3702 views
-
- 7 replies
- 5417 views
-
- 49 replies
- 28311 views
-
- 77 replies
- 78320 views
-
- 58 replies
- 39493 views
-
- 0 replies
- 1750 views
-
- 5 replies
- 10401 views
-
- 17 replies
- 25370 views
-
- 10 replies
- 18412 views
-
- 0 replies
- 2792 views
-
- 0 replies
- 2741 views
-
- 0 replies
- 2617 views
-
- 3 replies
- 5993 views
-
- 15 replies
- 14725 views
-
Featured Topics
-
-
Latest Commits
-
Topics
-
-
Posts
-
Thanks you:) https://www.youtube.com/@StayingHealthyTips?sub_confirmation=1 -
-
-
-
Weird.. the errors itself are suggesting that the parser is expecting something that is missing. but at least looking at the parts of code that are shown in the error, they look fine. For the 2nd one, I suggest reviewing the entire NPC and search if there is any unmatched "(" / ")" pairs, not only on this part where the error is appearing, but try checking the entire npc (modern editors can do parenthesis matching, so this might help). maybe even try commenting out parts of the script to check if the error is gone to limit the area to look at. This may also help for the 1st one. I don't remember seeing an so open error like that before, so unfortunately this is the only suggestion I hve
-
-
Download Statistics
