Atm, there are too many stupid comments, "to do's" and rants in my code . I usually update this thread every 1-2 weeks, so I will polish my code and hopefully also get the parser ready (not guarantee though) and upload it.

I'd like to encourage you to make the code public even if it's not polished. It's simply better. There was a nice talk (this one I think: https://youtu.be/0SARbwvhupQ?t=2m19s) where they talked about how programmers keep their code hidden until it's "ready" while it's actually important to start collaborating with others early to be able to fail early, fix stuff early, establish the team and avoid the project becoming a one man show. Not trying to force you of course, just saying no one's code is ever perfect, with maybe an exception of Linus Torvalds to be fair We won't laugh at TODOs

Atm, there are too many stupid comments, "to do's" and rants in my code . I usually update this thread every 1-2 weeks, so I will polish my code and hopefully also get the parser ready (not guarantee though) and upload it.

I'd like to encourage you to make the code public even if it's not polished. It's simply better. There was a nice talk (this one I think: https://youtu.be/0SARbwvhupQ?t=2m19s) where they talked about how programmers keep their code hidden until it's "ready" while it's actually important to start collaborating with others early to be able to fail early, fix stuff early, establish the team and avoid the project becoming a one man show. Not trying to force you of course, just saying no one's code is ever perfect, with maybe an exception of Linus Torvalds to be fair We won't laugh at TODOs

One example I can think of is to compare the two Daggerfall engine replacement projects I'm aware of: the XL Engine and Daggerfall Unity. XL Engine is currently closed source with the developer stating that he will open source it when it is ready. That was two years ago, the dev went silent around July last year and there appears to be no indication of when the next update will be available. Conversely, the Daggerfall Unity project was open source from the start and has seen a lot of development in the short amount of time since it started, multiple programmers are working together to get it finished and has an active modding community too.

But likewise, the owner of a program is free to do whatever they want with it's source code.

I'd like to encourage you to make the code public even if it's not polished. It's simply better. There was a nice talk (this one I think: https://youtu.be/0SARbwvhupQ?t=2m19s) where they talked about how programmers keep their code hidden until it's "ready" while it's actually important to start collaborating with others early to be able to fail early, fix stuff early, establish the team and avoid the project becoming a one man show. Not trying to force you of course, just saying no one's code is ever perfect, with maybe an exception of Linus Torvalds to be fair We won't laugh at TODOs

Yes, I am well aware of this problem, I personally feel quite uncomfortable when releasing "unfinished" code especially If there is something not going by the projects convention, if there are compiler warning ( -Wall ) or unoptimized algorithms. I will see that I will at least release the the lex and yacc files for the oblivion compiler, as this is basically done (MINUS code generation, I am thinking about using llvm here). What's keeping me from continuing right now is my playthroughs of The Witcher 3 and Far Cry 4, I somewhat regret it, I should have continued here as probably nobody wants OpenElderScrolls more than I.

I'm also encouraging you to release the code, this will be amazing! I understand you need a break and play games from time to time, but think that if code is public while you are playing witcher3 someone is improving and advancing OpenOB

I'm also encouraging you to release the code, this will be amazing! I understand you need a break and play games from time to time, but think that if code is public while you are playing witcher3 someone is improving and advancing OpenOB

Please?

Thank you for your work.

Seconding (or maybe fourthing?) this! It's hardly anything embarassing to have code that's not complete yet, and everyone needs breaks, so why not allow others to work on it while you take your well-deserved breaks?