Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Dysiode

Pages: 1
Old Bugs (1.x/2.x) / Adding New Key Mappings
« on: July 04, 2011, 12:06:27 am »
This is a formal bug submission of my reply to,1429.msg10616.html

Code: [Select]
FlxG.keys.addKey("HOME", 36); throws this:
Code: [Select]
ReferenceError: Error #1056: Cannot create property HOME on
Which yielded no results through my brief search through their 2.35 branch on Github so sadly I can't be of any help :<

Maybe that's the reason it was protected in the first place.

As usual I'm not sure what else is useful for this report but hopefully it's enough!

In my game at least when I use
Code: [Select]
setTileAt(__y, __x, tileLayer.layerID, __TilesetID, __TileID); it adds a 1.5 * tilesize collision area below and to the right of the tile.

I attached my logs just for kicks. And my game is private on the Forge.

The two relevant scripts are Explode in Actor Behaviors > Collisions and Tile API Wrapper in Scene Behaviors > Other. Move around with the arrow keys/keypad (with Numlock on) and fire by holding CTRL + Direction.

Archives / Actor Type Block
« on: June 25, 2011, 07:23:44 pm »
While I was discussing uses for Lists a pretty significant roadblock popped up in both inventory and random mob generators: There's no Actor Type block to easily add uninstantiated actors to a List to choose from. This more specifically affects inventories as scenes would still be easier to configure using behavior attributes but they could still benefit from the addition.

Focusing on inventories, it would be possible to display items by getting the Actor Type and passing it to "draw image for ___" (at least that's how draw image was explained to me). And adding items would be as simple as selecting them from the actor list, but as it stands either behavior attributes have to be defined for each item or the actor needs to be created and the type retrieved via "type of ___" both would be exceedingly messy to maintain with large numbers of items.

Part of my argument is that in the palette under Actor > Properties > Groups / Type there's
  • type of ___
  • group of ___
  • collision group selector
but there's no actor type selector.

Archives / Behavior Dependencies
« on: June 25, 2011, 12:04:26 pm »
It would be pretty neat if Stencyl let behaviors explicitly depend on each other so that if one behavior is attached to an actor/scene the behaviors it depends on would be attached automatically.

My simple use case for this is:
My `Tile Based Movement` behavior depends on `Snap to Grid` which I factored out because not everything that needs to be snapped moves. When I create a new moving actor I have to attach both which isn't terrible to remember but it would be super convenient if when I attached `Tile Based Movement` Stencyl automatically attached `Snap to Grid`

If the basic idea isn't convincing enough then I'll leave you with this:
Unity does it. You're not going to let Unity one up you, are you? ;3

Ask a Question / Adding new key mappings to FlxG.keys
« on: June 19, 2011, 02:25:58 am »
Howdy, I'm wondering if it's possible to add new key mappings to FlxG.keys. The addKey() method is protected and trying to replace the instance with a custom class that exposes it gets results in no apparent change.

If it's not possible to add new keys it should would be nice if Home, End, Page Up, and Page Down were added to the list of keys. Doing so would make the numpad (I know, poor design decision, hush.) at least usable if Numlock is off. As it stands Shift + Numpad 7 = Home but Home isn't registered so Flixel gets all kinds of pissy.

While I was working with the numpad (ignore my choice of design for a moment ;) I decided to use it with numlock off to avoid the Shift+2468 = Arrow Keys bug Flash has meaning the diagonal keys were mapped to Home, End, Pg Up, Pg Down. However, while Stencyl is wonderful and found even the obscure menu button (keycode 564 or something silly like that) there's no corresponding name for the keys in Flixel ( so Flixel throws a fit (in the form of "TypeError: Error #1010: A term is undefined and has no properties" (damn you useless errors).

Pages: 1