This topic contains 3 replies, has 3 voices, and was last updated by 
rIKmAN
2 years, 4 months ago.
-
Posts
-
Sorry if these have been asked before, I have still not really touched Monkey2 yet due to other existing commitments – however I did a quick search and nothing popped up.
I’m a Patreon supporter so have access to the last released reward version which I’m hoping to get my head into over the next couple of weeks when I get a bit more free time, but I have a few questions before I start.
Are there any plans for Monkey2 to support UWP, more specifically XB1 retail consoles in dev mode?
Does the mojo2 Spine module currently work in Monkey2?
How far along is development in terms of export targets? ie. Can it currently export to iOS/android?
Any plans to support Nintendo Switch?
How viable is it to start a proper project in Monkey2 as it stands at the moment?
Apologies for the spacing, I can’t seem to get it working right on mobile and it seems to do a double line when I press enter rather than a single line so everything looks too spaced out.
Thanks in advance!
Are there any plans for Monkey2 to support UWP, more specifically XB1 retail consoles in dev mode?
There are no plans for any new targets right now. Each new target adds a considerable amount of extra work and I’m pretty much running at maximum capacity here!
Does the mojo2 Spine module currently work in Monkey2?
No idea, but it should be easy to convert. There is an ‘experimental’ monkey2 spine module but unfortunately it’s not open source so I can’t include it in the monkey2 release. It will need to go on a ‘special’ download page here as I am apparently required to include the license on the same page as the link, but I haven’t got around to it yet. In the meantime, I can send you the monkey2 code if you want, you’ll need to drop in the ignition C code from github yourself.
How far along is development in terms of export targets? ie. Can it currently export to iOS/android?
It can but these are fairly incomplete. They can handle the monkey2 side of things fine, but there are no monetization etc modules yet (hard) and you can’t yet build for multiple architectures (easier).
How viable is it to start a proper project in Monkey2 as it stands at the moment?
This is of course a really subjective question, but IMO very viable. The only major ‘gamey’ thing I think it’s missing (if I were to write a game that is…) is the ability to stream music, something I plan to fix soon.
I havn’t converted spine module to mx2 yet, I will get around to it at some point but it sounds like there might be a solution for the interim.
Damn, I can only apologise for not replying to this sooner!
I completely forgot about it as the Monkey2 forums aren’t on my usual round of forums / websites – doh!Thanks for the breakdown Mark, that fills in a lot of blanks for me as I have not been following/using Monkey2 much at all.
Regarding Spine, yeah that would be great although it’s not urgent at all.
I already have Ignition, and I decided to purchase Pyro yesterday which will help me dip my toes into mojo2 while I wait for Monkey2 to mature a little more first.The decision was mainly based on future Spine support as I know skn3 has said that mojo2 will be focus of the Spine module updates going forward, and future Spine features simply won’t be supported in mojo1.
A little off on a tangent, but are there any plans to have have a marketplace of any sort with regards to Monkey2 and modules etc?
I bought GMS in the Humble Bundle (because why not for $15 with all the exporters!?) and although the engine definitely has it’s flaws – the marketplace for its extensions is something which I feel would really benefit and help Monkey2 grow.It would encourage people to (a) write modules and wrappers in the first place, (b) keep them updated as they would have people who had paid for them and (c) take the burden off Mark to implement feature x/y/z.
Seems like it would be a win/win for everyone, maybe even Mark could take a small cut of each sale – every little helps right?
Again I can only apologise for such a late response, my bad!
You must be logged in to reply to this topic.