Jump to content

Intersect Development Road Map


Recommended Posts

Thanks a lot for the copy & pasting event commands! This will save so much time! :)

Also, when you say you will add multiple data types for variables, does this mean you can have string variables as well as int? Thx

Link to comment
Share on other sites

  • 3 weeks later...
  • 2 weeks later...
15 minutes ago, varinyc said:

Petition for delay of Beta 6, till the API includes permissions, roles, ranks, etc. Or for introducing a Beta 7 before RC1.

 

B6 API actually has internal permissions that must be custom set. (IE: Access to user accounts/user endpoints) and there are more to come.

Link to comment
Share on other sites

2 hours ago, jcsnider said:

 

B6 API actually has internal permissions that must be custom set. (IE: Access to user accounts/user endpoints) and there are more to come.

what about chat commands that tie to permissions? or the manipulation of a commands list? Is this possible through api/json?

Link to comment
Share on other sites

2 minutes ago, varinyc said:

what about chat commands that tie to permissions? or the manipulation of a commands list? Is this possible through api/json?

 

You'd have to elaborate further for me to provide a decent answer.

 

Basic API access is all that's required to send chat messages. The API cannot trigger /commands.

Command lists? Assuming you're talking about events the API can modify event switches/variables but not alter events themselves. You can trigger stuff with the API by changing switch/variable values but not change event structures at this time.

Link to comment
Share on other sites

Updated the roadmap again. Beta 6.1 will be the final Intersect Beta. Once 6.1 is relatively stable we will be releasing the engine's source code ^^

 

With some help from the community we will work on future plans for the engine, and a roadmap to a Steam release once the source is out :) 

 

Source release is imminent!

Link to comment
Share on other sites

Updated the roadmap again. We've been working so hard on getting the engine ready for the source release that we haven't really kept up with and fully decided upon our future goals.  We're working on final code cleanup now, and we will be shifting versions soon (6.0 will become obsolete, 6.1 will become stable, 6.2 will become dev).

 

Source will be released very shortly after we have 6.2 dev builds working. (Expected within the next 2 weeks!)

 

There won't be any new features/enhancements for 6.2 over 6.1 at the time of launch, but it's important that we phase out 6.0 as we head into the world of open source :) 

 

After we open source the engine we will work on user enhancements, bug fixes, overall stability, and eliminating performance bottlenecks. Our ultimate goal is to launch the engine on steam but we will need a project management control panel type app in order to make that viable. The engine could use a bit more polish, and we are exploring ways for people to host in strict networks without port fowarding or paying for a VPS.  Right now our goal is for a smooth open source release. We will get together and make a list of goals for a Steam release soon!

Link to comment
Share on other sites

  • 4 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...