Server Model Allocation (Part 1): Refactor entity datasets and handlings into external configs - #5232
Open
MohabCodeX wants to merge 1 commit into
Open
Conversation
…l Allocation Part 1) - Move hardcoded handling array to handling.conf - Add objects.conf, peds.conf, and vehicles.conf - Add config loader classes for handling, vehicles, objects, and peds
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.
Summary
Moves hardcoded server entity data and vehicle handlings from C++ into separate
.conffiles.This is Part 1 of adding custom model allocation to the server. Follow-up PRs will add the model manager, dynamic ID allocation, and server-side Lua functions.
Changes
mods/deathmatch/:objects.conf(14,339 lines)peds.conf(299 lines)vehicles.conf(214 lines)handling.conf(213 lines)CHandlingManager.cpp.Next Steps
CModelManagerand dynamic ID allocation.Test Plan
runcode: