i am still using Nesmaker to work on the game if that is what you're asking but yes, at it's current state, not everything of the engine can be one-click controlled from the UI.
It's basically the same deal than with the whole CHR business where the UI's hardcoded actions go against what im doing, and as such, i simply go around them by poking the assemblies in notepad from the parts i need to.
like i mentioned in the previous post, there simply isnt enough screenflags for example, to manage the scrolling in the way it is currently implemented, so parts of it is done outside.
i suppose it depends on what you count as "with nesmaker" or not.
it's a game that started it's life from nesmaker, and the world layout and a large portion of the screens are made with nesmaker's screen tools.
the object settings and placements are also done with nesmaker.
currently what doesnt work in nesmaker:
- half of my graphics dont display due to the whole path/hud deal
- some of my graphics are not manageable at all as i've manually added more CHR files
- bankswitching is not manageable from the UI (this brings extra complications to normal graphics managements, as the animations require chr tables to be written for each screen that loads / uses more than one bank)
- scrolling settings are not manageable from UI
- weapon(s) are only manageable as raw assembly, due to the way you can only define weapon offset for one weapon for the UI (DS uses/will use varying sizes of animated sprite based weapons which are plain out typed out by hand.)
there's lots of little things that add up making it a constant juggle between the tool and external means to get things done.
there are also various extra things such as the sound test, which are 100% detached from the base engine and nesmaker doesnt really know they're there.
the sound test screen for example, uses it's own routine to draw 8x8 tiles for writing the texts on screen, and has it's own chr file embedded within the bank it sits at.
i do tend to try and keep things manageable with the tool to the extend i can, but it's simply not possible for everything.
as for what comes to turning this into a core, the scrolling for example is several thousands of lines of new/modified code, across.... i believe 19 files now, and those files were already modified to do things specific to this game even before the scrolling even came into the picture.
cleaning everything up and turning this into an empty core would require way more free time than i currently have available.
edit: oh also, the game currently has no enemy/object handling at all, so it's not like it even works yet.