Roadmap

Here is where de­vel­op­ers can find what fea­tures and ser­vices are com­ing to Con­struct Ar­cade. APIs that af­fect graph­ics will like­ly re­ceive in­te­gra­tions with A-Frame, three.js and Mag­num.

Recently Released

Fil­ter by sup­port­ed in­put

In the games over­view, you can fil­ter out games that don’t sup­port cer­tain in­put meth­ods (e.g. “6-dof”, if you on­ly have a “3-dof” con­troller).

In Construction

Lead­er­boards API

Sim­ple to use and se­cure sub­mis­sion and re­trieval of scores per play­er and game. Cur­rent­ly test­ing an ini­tial im­ple­men­ta­tion on QUAK.

Au­tode­tect sup­port­ed in­put

In the games over­view, the in­puts fil­ter will be au­tode­tect­ed based on con­n­tect­ed VR de­vice, if pos­si­ble.

Play­er API

API to re­trieve a play­er’s pro­file pic­ture and user­name.

On Our Minds

These APIs do not have an es­ti­mat­ed re­lease date, de­vel­op­ment has not nec­es­sar­i­ly start­ed and may not even start this or next year.

Gen­er­ic Mul­ti­play­er API

Easy means for syn­chro­niz­ing head­set and con­troller in­puts for users in a game room. Your game will be able to cre­ate a room that can be joined by oth­er play­ers. It will be re­quired to sim­u­late the game state on all play­er in­stances us­ing the in­put re­trieved from the API. While this makes the API not vi­able for physics based games, it should be very use­ful for ba­si­cal­ly all oth­er types of games.

This is a first step to­wards so­cial VR gam­ing, al­though very tech­ni­cal­ly lim­it­ed.

Avatar API

With mul­ti­play­er there is a need for play­er avatars. This will ini­tial­ly just of­fer a sin­gle col­ored mesh, but en­sures for­ward com­pat­i­bil­i­ty of your game with po­ten­tial cus­tom­iz­a­ble avatars in the fu­ture.