fix: properly cap negative syndicate standing #2393

Merged
Sainan merged 2 commits from fix-cap into main 2025-07-03 11:08:58 -07:00
Owner

Closes #2388

Closes #2388
Sainan added 1 commit 2025-07-02 14:25:29 -07:00
fix: always apply negative standing cap
All checks were successful
Build / build (pull_request) Successful in 45s
ef6e60fd11
Sainan added 1 commit 2025-07-02 16:49:06 -07:00
fix operation
All checks were successful
Build / build (pull_request) Successful in 1m23s
1df5153a77
Sainan changed title from fix: always apply negative standing cap to fix: properly cap negative syndicate standing 2025-07-02 16:49:15 -07:00
First-time contributor

This fix only modified the TypeScript source code; the JavaScript files were not updated. At the same time, using the update batch file on the server is unable to synchronize updates and replace the fixed data.

This fix only modified the TypeScript source code; the JavaScript files were not updated. At the same time, using the update batch file on the server is unable to synchronize updates and replace the fixed data.
Sainan merged commit 41686aea88 into main 2025-07-03 11:08:58 -07:00
Sainan deleted branch fix-cap 2025-07-03 11:08:58 -07:00
Contributor

This fix only modified the TypeScript source code; the JavaScript files were not updated. At the same time, using the update batch file on the server is unable to synchronize updates and replace the fixed data.

I am not sure what you exactly mean, but if you manually paste code (use git instead, I recommend) and then run the provided bat... no surprise that it won't work for you. You can grab the branch directly, do npm i, build & start and you don't have to worry about changes getting overwritten. Stuff is getting overwritten (for the most part) for a good reason, to update existing files correctly.

> This fix only modified the TypeScript source code; the JavaScript files were not updated. At the same time, using the update batch file on the server is unable to synchronize updates and replace the fixed data. I am not sure what you exactly mean, but if you manually paste code (use git instead, I recommend) and then run the provided bat... no surprise that it won't work for you. You can grab the branch directly, do npm i, build & start and you don't have to worry about changes getting overwritten. Stuff is getting overwritten (for the most part) for a good reason, to update existing files correctly.
First-time contributor

I am not sure what you exactly mean, but if you manually paste code (use git instead, I recommend) and then run the provided bat... no surprise that it won't work for you. You can grab the branch directly, do npm i, build & start and you don't have to worry about changes getting overwritten. Stuff is getting overwritten (for the most part) for a good reason, to update existing files correctly.

Thanks! The issue has been resolved now.

> I am not sure what you exactly mean, but if you manually paste code (use git instead, I recommend) and then run the provided bat... no surprise that it won't work for you. You can grab the branch directly, do npm i, build & start and you don't have to worry about changes getting overwritten. Stuff is getting overwritten (for the most part) for a good reason, to update existing files correctly. Thanks! The issue has been resolved now.
Sign in to join this conversation.
No description provided.