Byond 516 Fixes#543
Conversation
|
This will be merged once It is cleared by @Constellado |
|
This appears to conflict with one of the TMs, so I can't test it. likely the cherrypick. |
|
this is a simple PR and doesnt need to be TMed by us... This only exists so that the server becomes future proof for 516.1670+ |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
This PR has been inactive for a month. This means it is at risk of being auto closed in a week, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself |
2 participants
REQUIRES BYOND 516.16XX
Due to Byond 516.1670 forcing associated lists to now be alists this forces the code base to become incompatable with 515 versions for the server.
About The Pull Request
Byond 516.1670 and newer no longer allows numeric associative lists.
IE lists that are"
1 = 3
#DEFINE = 2... Where DEFINE is a number as well.
Why It's Good For The Game
Allows Servers running newer versions of the code to not get these critical errors.
I am no longer sure when alists were added to the code. As the github workflow failed when trying to use the last 515 branch. Meaning this forces the server/coding side of the codebase into 516 forever.
Changelog
Nothing Player Facing