If the codebase has become a mess I really recommend starting again with a new codebase from scratch rather than trying to fix it.

It might seem crazy if the codebase has taken months to develop. But starting again with reference to the old project seriously takes only a matter of days to produce something better with a better architecture.

I do similar restarts, but on smaller scale. If I think I can refactor a function or a section of code I will copy the function and start reshaping it. Allows for a point of reference if things go pear shaped. :)

Thank you guys. I won't be doing a complete restart. One of the big refactors I did to this project a while back was to make it more modular. Since then I've actually ripped out huge chunks and re-wrote them from scratch. The dungeon system was a big one I almost tore out completely and re did to handle features and object interactions far easier. It's nothing new to the project.

There's a few major pieces I think can be made to be more flexible and contained then they are right now. it can be as simple as the fact I didn't realize my LOS code was broken till I started casting rays to determine what a ranged ability would hit. Fixing that broke alot of what I was striving to consider a standard for the project.

Though one major aspect has been nagging me and tempting a complete rewrite for some time. I started this project with the intent of making it as data driven as possible. It was supposed to make things easier to edit and tweak. Unfortunately the project started off with a huge burst of motivation and drive like none other. I coded like a mad man, I had no desire to bog myself down coded alot of fluff just to load everything from scripts. The project quickly migrated to the hard coded style of the first one.

Now that the project is gotten to a moderate size, and I've seen how everything fits together.... I really want to tear things apart and make it data driven. So I can tweak things without waiting the 3 minutes or so to build. Three minutes doesnt sound long but when you tweaking one variable over and over again, sometimes 10-20+ times before it feels right. I've eaten up a half hour or more just letting it compile. When I only have 1-3 hours to code, that's alot of wasted time.

I haven't and won't abandon the project. I enjoy rogue likes way too much not to make one with the specific features I like :). I'm keeping a list of brainstorms and ideas that I add to quite regularly, for the project. It's still the busy year here on the little island I call home, and some annoying responsibilities reared their ugly heads in the middle of it.

The project is till on hold for basically the same reason as before, I don't have the time to devote to it right now. The projects getting to that scale were an hours' worth of time doesn't get anything done. I find atleast three hours has become needed. I've been needing half and hour or so just to skim over the planned features and figure out my angle of attack before I can even get some decent coding done.

I won't deny the thought of a restart, but I don't things are that a mess, yet. I'll have to see where my brainstorming leads me when I can spend some time on the project.