Advertisement
Guest User

Untitled

a guest
Apr 17th, 2014
228
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.05 KB | None | 0 0
  1. 3) Considering there has been a lot of changes and progress in the code
  2. base since I removed New Vegas support, I don't recommend going back to
  3. the New Vegas state. Merging back the progress will be very hard /
  4. impossible. I recommend taking the up-to-date repository version and
  5. adding support back in. All of the data required can be extracted from
  6. these two commits http://fuch.si/3D http://fuch.si/3E
  7.  
  8. This includes (but is not limited to) the following stuff which needs to
  9. be done:
  10.  
  11. * Change client and server infrastructure to allow both New Vegas and
  12. Fallout 3.
  13. * Client: function handlers (Game.cpp), function definitions
  14. (API.cpp), startup routine (Bethesda.cpp), reverse engineered game
  15. calls (vaultmp DLL), vaultmp New Vegas ESP
  16. * Server / master server: New Vegas sqlite3 database, server INI
  17. setting, New Vegas flag in ServerEntry.cpp and query routines,
  18. scripting definition extensions (records.h) / changes to check for New
  19. Vegas
  20.  
  21. Some new features need to be ported to New Vegas as well. This is mostly
  22. reverse engineering.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement