I might try that out today and see what I can do with it. I have to try the extension though before I can really say for sure. I just checked the data structures extension and it looks pretty good but I think I'd have an easier time with the lists and maps. I was looking at the external data extension but hadn't seen the data structures. This is just because it seems easier to do it this way and not sure how else to do it.Īnyone have any pointers? Maybe a cleaner or simpler way of doing this? I guess I can add an extra random value to the map/list of a player's creature to make the stats different after multiplying by the level & random value.
This means every creature of the same type and of the same level will have the same stats.
Also it feels a bit cheap because instead of tracking the stats of each creature I would just track the level and multiple by the base stats. I can already feel how messy this will be if I need a map for every creature. I would then keep track of those creature's levels and multiply the base stats of the corresponding creature by the level when they are in a battle to get atk, def, etc. My way would consist of using a lot of maps/lists to keep track of each creature's stats and then use maps/lists to store the players party & storage creatures. I recently made a calorie/food tracker and I am keeping track of quite a bit of stuff but it is kind of messy. I have an idea how to achieve this by taking some shortcuts and using lists/maps but it doesn't seem efficient. You can't import classes using wildcards.Hey I'm making an RPG and I need to keep track of many "creatures" (something similar to Pokemon). No Dictionaries, but Haxe has strongly-typed Maps.įunction pointers have to be typed explicitly.Īll package must be in lower-case, but all class names must start with upper case. Constructors are defined using new rather thanĬhecking for "null" has to be done explicitly. Package Declarations are done Java-style.Ĭlass Definitions don't include public.
We recommend reading this while we build our own guide.Īreas where the basic syntax and structures are different include.īasic Types are slightly different and all capitalized. This guide is a light introduction to Haxe for AS3 developers.Īll differences are clearly illustrated on OpenFL's Haxe for AS3 Primer. With our move towards a unified, cross-platform enginem we've adopted Haxe, a language that's remarkably similar to ActionScript 3, but at the same time, has enough small differences to force all existing code to be ported.
0 kommentar(er)
