GSoC Engine resource abstraction: Difference between revisions
From Spring
Jump to navigationJump to search
Brain damage (talk | contribs) |
|||
| Line 20: | Line 20: | ||
* The new system should completely supersede the current | * The new system should completely supersede the current | ||
* Sync check should be adapted to hash the new resource system | * Sync check should be adapted to hash the new resource system | ||
* Hardcoded assumptions such as cost-based targeting should be removed completely | * Hardcoded assumptions such as cost-based targeting should be removed completely and replaced with something better | ||
== Possible Mentor(s) == | == Possible Mentor(s) == | ||
Revision as of 16:47, 12 March 2010
GSoC idea: Engine level abstraction of resources
Why
Current hardcoded resource system generates defects and can produce effects which are hard to workaround for game designers which aren't willing to use it.
What
The old system needs to be replaced, the new one should be flexible enough to reproduce everything that the old system did and be able to imitate the behaviour of most common RTS game titles.
The engine's Lua API to fetch resources will have to be adapted to the new system and new calls will have to be added to modify its state.
Required skills
- Knowledge of C++
- Knowledge of Lua/C API bindings
Difficulty
Estimated: medium to hard
Technical details
- The new system should completely supersede the current
- Sync check should be adapted to hash the new resource system
- Hardcoded assumptions such as cost-based targeting should be removed completely and replaced with something better
