Community for the Sphere game engine

New? Contact Us to register an account!

Ooh, another Zelda project, huh? Can I ask, what generation of Zelda are you basing this on? Or is it a little more generic and combining the general 2D top-down Zelda style in general?

So, using miniSphere, v2 api? Any chance I can persuade you to use some of my new scripts? (MapEngine, Sprite Engine and HUDSystem)

I know they're not 100% ready but they're pretty close and having someone else use them would help them get polished.

My game is at 640x360, which I just found out is exactly on the edge for 2x.
640x361 works well for recording a gif to showoff new menu.

Quote from: Fat Cerberus – on September 27, 2017, 01:15:43 pm

Quote from: Rukiri – on September 27, 2017, 01:04:47 pm

Focus on minisphere, make sure there's really only 1 sphere to work with and make it blatantly clear that 1.5x is legacy and not supported for future development.

That's what I keep telling people, but they insist on writing new code against the Sphere v1 API anyway.  I guess it doesn't help that most of our active members are still old-timers and there's no Sphere v2 map engine yet (though @Rhuan is slowly working on one).  The classic map engine just isn't conducive to writing idiomatic Sphere v2 code, and the divide has widened even further with ES6 being supported in the beta.

I think the absence of a v2 map engine is a pretty major issue, I'm trying to fix that but getting it right is taking time (plus I was away for almost a month since starting it which delayed me quite a bit).

Also the v2 API still feels a little new/untested, it's not a stable 100% there definitely good to go platform yet, it's getting there and when it's finalised it will be great just needs a little bit longer IMO.

Quote from: Rukiri – on September 27, 2017, 01:25:04 pm

Still think a rpg template would go a long way in bringing in people, use xp stuff "everybody does..." just put a disclaimer for assets use *can not be used for commercial projects.   I'm also thinking about moving my rpg project from unity I was going to use RPG Maker MV only because I could do entire 5hr story arks in a month or 2, Dragon Ball currently has 10 so the game would be around 50hrs "the Future trunks ark is going to be 10+ only because I love Black <3"  So imagine doing a project like that in Unity especially with how scenes are organized... even tho I have most of my Zelda kit done it was quite a pain in unity "especially the room transitions...". 

I'd love to make a full RPG template - just taking a while on the map engine; I have a full time job and other things in my life + recently have just been writing too much code both in and outside of work, been making my brain spin and I've had to slow down/do simpler stuff.

So you've got a project you're thinking of moving from unity? What do we need to do to persuade you to bring it to miniSphere?

Quote from: Rukiri – on September 27, 2017, 01:04:47 pm

Focus on minisphere, make sure there's really only 1 sphere to work with and make it blatantly clear that 1.5x is legacy and not supported for future development.

That's what I keep telling people, but they insist on writing new code against the Sphere v1 API anyway.  I guess it doesn't help that most of our active members are still old-timers and there's no Sphere v2 map engine yet (though @Rhuan is slowly working on one).  The classic map engine just isn't conducive to writing idiomatic Sphere v2 code, and the divide has widened even further with ES6 being supported in the beta.

Can I post a video?
I'm gonna post a video.
Using a screenshot.