FileReader now ignores BOM when reading UTF-8 (with signature) files, Fixed laggy zombie AI#195
Merged
Bravo555 merged 3 commits intoHopsonCommunity:masterfrom Apr 18, 2017
Repertoi-e:master
Merged
FileReader now ignores BOM when reading UTF-8 (with signature) files, Fixed laggy zombie AI#195Bravo555 merged 3 commits intoHopsonCommunity:masterfrom Repertoi-e:master
Bravo555 merged 3 commits intoHopsonCommunity:masterfrom
Repertoi-e:master
Conversation
…which are default saved from Visual Studio and cause crashes with JSON parsing (unexpected symbols) + fixed laggy Zombie AI
Author
|
Wait.. what? It wasn't zombie. Its when you get in the test particle updates get rekt.. But still the fix improves performance. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
FileReader now ignores BOM when reading UTF-8 (with signature) files (default encoding for Visual Studio) and cause crashes with JSON parsing (unexpected symbols)
Access player from level was only possible via ID and a for loop which was a very stupid idea and I don't what was I thinking. When you got closer to Zombie UPs got -20 and caused an Illusion that player was again moving faster certain directions...