1. "Make hit game" button.







Kidding... kidding. I actually enjoy the programming part.

- Ultimately if AppGameKit was structured so that we, the developer, could make plugins that would modify the java and obj-c code to our needs then it would be best for AppGameKit as they won't have to maintain the SDK compatibility so much. My idea for this is to give a handful of tier 1 dummy functions that are tied to java and obj-c methods so that we can repurpose them as needed. Unity and many other development packages make use of this structure. It would be a great boon to AppGameKit to do this as well and further their income opportunities.

This is where I feel AppGameKit will always run into trouble unless they add third party extension support. There are ties to so many SDKs and libraries (social networking, ads, IAP...) and history has shown that AppGameKit with just one developer cannot stay on top of all this.

Adding the ability to write to SD storage on Android. This would be super handy for games / apps that want to generate screenshots or drawing style apps.

Two small features I'd like to see:

SetTextAngle - at the moment if you want text shown at an angle you have to use a sprite.
SetViewAngle - this would make for some interesting effects.

Not ground breaking ideas,but commands I think would be useful to most people.

I would like to see save/load array implemented, from stretch goal number two in the Kickstarter.

This is a great list. fixed 360 controller, Steam support, full Box2d, and additional blend modes are at the top of my list. The ability to build a list of all supported display modes would be great for making PC games.

Hi all?,
Could be possible include the data/restore/read BASIC commands?
These commands are really useful.
Best regards.

Hi all,
Could be possible include the data/restore/read BASIC commands?
These commands are really useful.
Best regards.

Could be possible include the data/restore/read BASIC commands?

If they go for source data inclusion, I think a better way would be datablocks.

Effectively the same as a data statement, but with the type defined (byte, word, long etc.) and accessed with something like the memblock commands. Call them in-line memblocks if you like.

I don't know how well it fits into the android/ios way of doing things, but since you can do it in C, I don't see a technical reason why it couldn't be done in AGK.

String constants are probably compiled using something similar already.

Can a moderator pin this please? Don't want it to get lost and want it to be visible to others.

At Naphier's wise suggestion, I'll post my feature requests here:-

1) Support for Sqlite3 - this is pretty much essential - just look at how many mobile apps and games use it.

2) File I/O commands to Write or Read a Memblock - seems a shame not to with all those other memblock commands already supported...

3) Some more GUI - not akin to BlueGUI but a more graphics-customisable set of commands - tick and cross buttons, sliders, scroll bars etc.

4) Some basic pathfinding / AI commands.

5) Further Spine commands texture/mesh deformations etc.

6) Instr command and perhaps some other useful text commands like LSet/LPad, RSet/RPad etc.

Ok, here's my wish list.

* Add start position parameter to "playsound" , so you can play a sound from any start position. Surely this isn't too difficult to implement.

* Add save and load array as although it's easy to code a text writer it would be so much more convenient.

* Fix any issues with well known controllers and make sure new ones are supported like the fire TV for example.

* Full windows mobile support

* Augmented reality commands now we have sensor support it's a logical next step. Something like createimagefromcamera.

* Background load commands so you can load additional files while your app is running without pausing it.

* Implement a depth value for Video playback so you can place sprites over a playing video.

* File picker (similar to DB pro)

* Of course all the 3D commands we all want including FBX model and animation support.

I would like to +1 the load/save memblock & array file commands. We can write our own solutions for this, but interpreted math in AppGameKit is deathly slow. Parsing a bulky file is unneededly painful. Also, out of curiosity, why can't we load an entire file as a string, instead of reading line by line (or other small units)?

If I have to choose one: Further Spine commands.

1. "Make hit game" button.

DBPro has MakeGame()

etViewAngle - this would make for some interesting effects.

Yes to SetTextAngle, would be extremely useful.

SetViewAngle - Could this be achieved using shaders, or even sending an offscreen game to a sprite? I did this once in DBPro but it was a long time ago. I converted the left/right movement of the cursor into an opposing rotation of the screen.

Support for Sqlite3

+1

I am mostly looking forward to the 3D Engine enhancements and Physics.

The ability to have a gradient (2 or 3 base colours) instead of a single colour as the clear colour. Gradients are used so often so I wonder if there is a faster way of producing them in code (like the amiga had HAM mode for those who can remember that!) rather than relying on images.

Would it be possible to add a simple GetVirtualButtonVisible function? It would be really convenient in doing fancy things with the ui.

You can use DrawBox to create gradient (in V2 at least)...

The sound system could be improved a lot with a pan setting for PlaySound(). That should be very simple to do.