SpringEngineTODO: Difference between revisions

From Spring
Jump to navigationJump to search
← Older edit
Jk (talk | contribs)
0 edits
mNo edit summary
Gajop (talk | contribs)
0 edits
No edit summary
 
(24 intermediate revisions by 8 users not shown)
Line 1: Line 1:
'''This page is badly out of date. Some of these items have been done, abandoned or replaced with better ideas.'''
A collection of ideas which could improve Spring. Before starting anything, please ask in the forum [http://springrts.com/phpbb/viewforum.php?f=60 developement-forum] so that you go in the right direction.  


Here is a TODO list for anyone interested in developing the spring code. If you are not involved in the development, please contact one of the developers first before you add things here.
* Get a '''stable OS X version''' working. Contact the developers on the forums for this, as there are people who build and run it successfully. Still need proper packaging and maintaining,
** Requires: C/C++, CMake and MacOS
** Time: < 1 month
** Level of difficulty: Medium
** More information at http://springrts.com/wiki/Spring_on_MacOSX


* Implement saving/loading. There are a lot of direct LoadSave() functions in the game code, but the easier way would probably to finish the serialization in the class registration type interfaces (rts/System/creg), so everything can be serialized automatically.  
* clean up, sanitize, and implement a '''consistent error handling''' scheme in the engine
* add '''general serializing''' to the engine, which touches the following:
** Implement saving/loading. There are a lot of direct LoadSave() functions in the game code, but the easier way would probably to finish the serialization in the class registration type interfaces (rts/System/creg), so everything can be serialized automatically.  
*** Requires: C/C++
*** Time: ~3 months
*** Level of difficulty: medium - hard
** [[Syncing System|Implement re-sync]]. After a sync problem is detected, and a re-sync of the random seed does not fix it the game would pause and use the rsync to adjust game state (current plan if for float3 data) to resync. After using rsync on it should be able to continue normally until the next sync error is detected.
*** Requires: C/C++, network programming
*** Time: ~3< months
*** Level of difficulty: Hard


* [[Syncing System|Implement re-sync]]. After a sync problem is detected, and a re-sync of the random seed does not fix it the game would pause and use the rsync to adjust game state (current plan if for float3 data) to resync, as suggested by Jesse Schoch in [http://lolut.utbm.info/pipermail/taspring-linux/2006-February/000810.html]. After using rsync on it should be able to continue normally until the next sync error is detected.
* Implement a '''general sensor system''' replacing the radars, as described in http://taspring.clan-sy.com/phpbb/viewtopic.php?t=6105
** Requires: C/C++, 3D/2D math (Lua knowledge not required, but prefered)
** Time: ~2 months
** Level of difficulty: Medium


* Abstract and improve unit rendering:
* '''Abstracting the resource system''' to allow more than two resources (metal/energy)
** 3DO/S3O support is not abstracted, many parts of unit rendering are spread throughout spring and assume 3DO, and the rendering is a messy mixture of 3DO and S3O stuff. Abstracting the model rendering with a sort of IModel and IModelInstance interfaces would allow adding other model formats as well (Such as a skeletal animation format).
** Requires: C/C++ (Lua knowledge not required, but prefered)
** Time: ~1-3 months
** Level of difficulty: Easy-Medium


* Implement a general sensor system replacing the radars, as described in http://taspring.clan-sy.com/phpbb/viewtopic.php?t=6105
* '''Exposing more Spring functions to the Lua world''' (command AIs, move types) or/and small frameworks
** Requires: basic C/C++, Lua
** Time: ~1-3< months (depends on the goal)
** Level of difficulty: Easy-medium


* Add a dynamic-lighting system: Allow units to have dynamic lights on them that affect lighting of other units and landscape, with sort of "approximating lights" for cases where a lot of units get close together. This is a big thing, but it would improve spring graphics a lot if done well. Or Deferred Lighting/Shading?
* Implement '''MD5 as a model format or add other model formats'''.
** Requires: C/C++, 3D math (Lua knowledge not required, but prefered)
** Time: ~1-3 months
** Level of difficulty: Medium


* Get a mac version working. Contact the developers on the forums for this, as there are people looking into this already.
* Add '''p2p/round-robin for hosting''' (so host exit does not stop the game)
** Requires: C/C++, network programming
** Time: ~3< months
** Level of difficulty: Medium


Even though this isn't really about the Spring engine:
* '''Fix bugs'''
 
* SpringLobby is a cross-platform lobby client, implemented in C++ and wxWidgets. We encourage you to look into our todo list on http://springlobby.info and see what you could do for it.
 
Lua:
 
* Create a Mission Development Kit: ie, do whatever it takes to make it easy to create campaign missions, eg create a gui tool that makes it easy to place units on the map, create triggers, and so on.
 
[[Category:Source development]]

Latest revision as of 05:00, 5 November 2017

A collection of ideas which could improve Spring. Before starting anything, please ask in the forum developement-forum so that you go in the right direction.

  • Get a stable OS X version working. Contact the developers on the forums for this, as there are people who build and run it successfully. Still need proper packaging and maintaining,
  • clean up, sanitize, and implement a consistent error handling scheme in the engine
  • add general serializing to the engine, which touches the following:
    • Implement saving/loading. There are a lot of direct LoadSave() functions in the game code, but the easier way would probably to finish the serialization in the class registration type interfaces (rts/System/creg), so everything can be serialized automatically.
      • Requires: C/C++
      • Time: ~3 months
      • Level of difficulty: medium - hard
    • Implement re-sync. After a sync problem is detected, and a re-sync of the random seed does not fix it the game would pause and use the rsync to adjust game state (current plan if for float3 data) to resync. After using rsync on it should be able to continue normally until the next sync error is detected.
      • Requires: C/C++, network programming
      • Time: ~3< months
      • Level of difficulty: Hard
  • Abstracting the resource system to allow more than two resources (metal/energy)
    • Requires: C/C++ (Lua knowledge not required, but prefered)
    • Time: ~1-3 months
    • Level of difficulty: Easy-Medium
  • Exposing more Spring functions to the Lua world (command AIs, move types) or/and small frameworks
    • Requires: basic C/C++, Lua
    • Time: ~1-3< months (depends on the goal)
    • Level of difficulty: Easy-medium
  • Implement MD5 as a model format or add other model formats.
    • Requires: C/C++, 3D math (Lua knowledge not required, but prefered)
    • Time: ~1-3 months
    • Level of difficulty: Medium
  • Add p2p/round-robin for hosting (so host exit does not stop the game)
    • Requires: C/C++, network programming
    • Time: ~3< months
    • Level of difficulty: Medium
  • Fix bugs
Retrieved from "https://springrts-wiki.p2004a.com/mediawiki/index.php?title=SpringEngineTODO&oldid=17111"