Register - Login
Views: 99393052
 Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies		 04-24-22 10:19:18 AM
Jul - Projects and Creations - WaGa 2 [demo ver: 0.35] New poll - New thread - New reply
Next newer thread | Next older thread
setz
Member
Level: 24


Posts: 87/103
EXP: 74237
For next: 3888

Since: 07-02-08

From: Pittsburgh, PA

Since last post: 4.1 years
Last activity: 4.0 years
Posted on 02-03-18 05:59:11 AM Link | Quote
Hi I'm an old guy who made things in the past, and currently am making a new thing.

This will be a devlog thread where i just dump stuff and rant and talk about how I solved some issues sometimes.

What is WaGa 2?
It's the sequel to WaGa, which was a Pico8 RPG I made that was heavily influenced from SaGa.

WaGa 2 will carry on a similar race and durability system, add some fancy 3d map movement like Wizardry, weapon skills and magic, and Other Stuff.

Currently it's being developed with Three.js and being designed for web distribution. I also want to release it on android because the whole reason I'm making it is I wanted a dungeon crawler rpg on androind.

Sounds cool can I try it
Sure. I periodically upload demos at this url. At the time of writing it's at 0.35. I'll upload the title if I have a new demo.

What are some asspains you've already had to deal with?
Three.js is definitely a 3d framework and not at all an engine suited for what I want to do. A lot of the examples I've found detailing how to do things I want to do (like sprites based off screen position instead of scene coordinates) were apparently taken out of the library years ago.

Instead of placing sprites by screen coordinates, I had to make a seperate scene, with a seperate orthographic camera, and then render that scene ontop of my current scene to get HUD type stuff. But even then, placing objects on that scene had really, really weird coordinates. I kind of had to hack up the cameras top/left/etc coordinates, and then write my own translation function to place things accordingly.. but hey, it works now.

I have no idea how to 3d model, so I spent too much time trying to make a cube with different textures on it in blender, and eventually gave up and now I am just making all the geometry in the game with code. It's much, much easier for me this way.

afaik three.js doesn't seem to have any kind of input handling helpers. So I had to write my own stuff there.

Creating 2d sprites from canvas textures was a huge pain to get set up but now it works and let me make my own dynamically sized textboxes. That was a big hurdle in a game that's going to be almost entirely menubased.

Ok cool show me screenshots

Basic maze navigation with overlay.


in-engine mockup on how the battle backdrops might look.

____________________
-----
I have some games on splixel.itch.io and a twitter.
setz
Member
Level: 24


Posts: 88/103
EXP: 74237
For next: 3888

Since: 07-02-08

From: Pittsburgh, PA

Since last post: 4.1 years
Last activity: 4.0 years
Posted on 02-04-18 05:59:05 PM Link | Quote
Cool new things
Polished up my textbox generation routines, added functions for multiline text since threejs doesn't support that out of the box.
Cleaned up some textures, made some other new ones.
Did some tweaks to the room generation so I can have more than just walls or not walls. Added a nonfunctional door. This worked out in the end but there have been some really fuckin weird javascript things happening that I don't get at all. Collision is broken until I can figure out why an array of ints is getting turned into an array of meshbasictextures.

Next biggie to work on
Definitely figuring out what the fucks up with that meshbasictexture thing and fix collision.
I'm currently in the middle of writing functions to manage grid menus across the game
After grid menu setup is done - Battle Flow, Pause Menu/Party management

Bonus media
theres a video this time https://imgur.com/a/pKOIy
just showing off the new textures, and the start of a menu system

also heres one of the human enemies


____________________
-----
I have some games on splixel.itch.io and a twitter.
a tiny fairy

Level: 18


Posts: 41/80
EXP: 28248
For next: 1649

Since: 01-16-18

Pronouns: —

Since last post: 4.1 years
Last activity: 3.6 years
Posted on 02-06-18 12:12:06 AM Link | Quote
There's very little "delay" on the turn keys so sometimes I accidentally turn multiple times before I can unpress the key. You might want to slow down the animation a little?

The maze it made also had some 0 thickness walls, I'm not sure if that's something you want to keep since it could make mapping confusing?

Overall it looks really nice though!

____________________
setz
Member
Level: 24


Posts: 90/103
EXP: 74237
For next: 3888

Since: 07-02-08

From: Pittsburgh, PA

Since last post: 4.1 years
Last activity: 4.0 years
Posted on 02-09-18 11:34:31 AM (last edited by setz at 02-09-18 11:35:18 AM) Link | Quote
The wall thickness was something that always bothered me, but only recently got around to addressing (though it was ugly, it was pretty low priority to fix).

The keyboard controls are currently kinda only there for debugging (considering making the game entirely mouse driven, so theres no issues where you have to grab the mouse just to do one simple thing). I am planning this as an android game, but it's not the first time I've heard this complaint, so I'm going to add it to my notes to refuckulate input sensitivity and all that.

Got some good stuff done since the last update but no new demo because I'm in the middle of making the battle scenes.

Cool new things
completely gutted the map loading routines. Now room properties are auto-generated based off the colors in a tile map, I'm going to need around 50 floors of maze, so this is a big help.

completely gutted the map drawing routines. Now instead of drawing a cube for each room, i'm just drawing 6 planes. I'm drawing the walls offset from the edge, and made corner tiles so that things are less ugly.

wrote some stuff so i can render a scene on a texture. I could have just used a plain 2d backdrop for battles, but I really wanted to be able to do some camera and 3d effects during battle, and have the battle area itself be able to have 3d effects, so this is the only way I could think to make that happen.

made art more pretty.

Next biggie to work on
i need to make a universal menu system
currently working on the battle flow (how turns get decided, how actions get processed, win/lose conditions, etc)

Media
new wall thickness


battle scene


sidenote
I just started a new job, so work on this is probably going to slow to a crawl for awhile.

____________________
-----
I have some games on splixel.itch.io and a twitter.
lion

Level: 19


Posts: 18/84
EXP: 30310
For next: 5467

Since: 01-25-18

Pronouns: he/they
From: Portugal

Since last post: 1.2 years
Last activity: 1.2 years
Posted on 02-17-18 08:59:39 PM Link | Quote
Looks pretty cool, good luck with the project!
SaGa 4lyfe

the human enemies are cute too btw
Next newer thread | Next older thread
Jul - Projects and Creations - WaGa 2 [demo ver: 0.35] New poll - New thread - New reply


Rusted Logic
Acmlmboard - commit 47be4dc [2021-08-23]
©2000-2022 Acmlm, Xkeeper, Kaito Sinclaire, et al.

28 database queries, 2 query cache hits.
Query execution time:  0.105520 seconds
Script execution time:  0.011508 seconds
Total render time:  0.117028 seconds


TidyHTML vomit below
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 119 column 11 - Warning: <form> isn't allowed in <table> elements
line 118 column 10 - Info: <table> previously mentioned
line 120 column 11 - Warning: missing <tr>
line 120 column 119 - Warning: missing </font> before </td>
line 124 column 16 - Warning: plain text isn't allowed in <tr> elements
line 120 column 11 - Info: <tr> previously mentioned
line 125 column 68 - Warning: missing </nobr> before </td>
line 141 column 68 - Warning: missing </nobr> before <tr>
line 147 column 35 - Warning: missing <tr>
line 147 column 50 - Warning: missing </font> before </td>
line 148 column 37 - Warning: unescaped & or unknown entity "&id"
line 147 column 194 - Warning: missing </font> before </table>
line 149 column 35 - Warning: missing <tr>
line 149 column 50 - Warning: missing </font> before </td>
line 149 column 91 - Warning: missing </font> before </table>
line 156 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 158 column 9 - Warning: missing <tr>
line 176 column 13 - Warning: missing <tr>
line 177 column 102 - Warning: unescaped & or unknown entity "&postid"
line 213 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 215 column 9 - Warning: missing <tr>
line 233 column 13 - Warning: missing <tr>
line 234 column 102 - Warning: unescaped & or unknown entity "&postid"
line 255 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 257 column 9 - Warning: missing <tr>
line 275 column 13 - Warning: missing <tr>
line 276 column 102 - Warning: unescaped & or unknown entity "&postid"
line 285 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 287 column 9 - Warning: missing <tr>
line 305 column 13 - Warning: missing <tr>
line 306 column 102 - Warning: unescaped & or unknown entity "&postid"
line 339 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 341 column 9 - Warning: missing <tr>
line 359 column 13 - Warning: missing <tr>
line 360 column 102 - Warning: unescaped & or unknown entity "&postid"
line 368 column 17 - Warning: missing <tr>
line 368 column 17 - Warning: discarding unexpected <table>
line 371 column 35 - Warning: missing <tr>
line 371 column 50 - Warning: missing </font> before </td>
line 371 column 91 - Warning: missing </font> before </table>
line 373 column 35 - Warning: missing <tr>
line 373 column 50 - Warning: missing </font> before </td>
line 374 column 37 - Warning: unescaped & or unknown entity "&id"
line 373 column 194 - Warning: missing </font> before </table>
line 375 column 17 - Warning: discarding unexpected </textarea>
line 375 column 28 - Warning: discarding unexpected </form>
line 375 column 35 - Warning: discarding unexpected </embed>
line 375 column 43 - Warning: discarding unexpected </noembed>
line 375 column 53 - Warning: discarding unexpected </noscript>
line 375 column 64 - Warning: discarding unexpected </noembed>
line 375 column 74 - Warning: discarding unexpected </embed>
line 375 column 82 - Warning: discarding unexpected </table>
line 375 column 90 - Warning: discarding unexpected </table>
line 377 column 9 - Warning: missing </font> before <table>
line 389 column 25 - Warning: discarding unexpected </font>
line 398 column 57 - Warning: discarding unexpected </font>
line 376 column 1 - Warning: missing </center>
line 120 column 63 - Warning: <img> lacks "alt" attribute
line 125 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 125 column 93 - Warning: <img> lacks "alt" attribute
line 141 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 141 column 98 - Warning: <img> lacks "alt" attribute
line 148 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 161 column 22 - Warning: <img> lacks "alt" attribute
line 161 column 63 - Warning: <img> lacks "alt" attribute
line 161 column 112 - Warning: <img> lacks "alt" attribute
line 161 column 162 - Warning: <img> lacks "alt" attribute
line 162 column 11 - Warning: <img> lacks "alt" attribute
line 172 column 15 - Warning: <img> lacks "alt" attribute
line 205 column 2514 - Warning: <img> lacks "alt" attribute
line 208 column 2617 - Warning: <img> lacks "alt" attribute
line 218 column 22 - Warning: <img> lacks "alt" attribute
line 218 column 63 - Warning: <img> lacks "alt" attribute
line 218 column 112 - Warning: <img> lacks "alt" attribute
line 218 column 162 - Warning: <img> lacks "alt" attribute
line 219 column 11 - Warning: <img> lacks "alt" attribute
line 229 column 15 - Warning: <img> lacks "alt" attribute
line 251 column 1179 - Warning: <img> lacks "alt" attribute
line 259 column 11 - Warning: <img> lacks "alt" attribute
line 260 column 22 - Warning: <img> lacks "alt" attribute
line 260 column 63 - Warning: <img> lacks "alt" attribute
line 260 column 112 - Warning: <img> lacks "alt" attribute
line 260 column 162 - Warning: <img> lacks "alt" attribute
line 261 column 11 - Warning: <img> lacks "alt" attribute
line 271 column 15 - Warning: <img> lacks "alt" attribute
line 290 column 22 - Warning: <img> lacks "alt" attribute
line 290 column 63 - Warning: <img> lacks "alt" attribute
line 290 column 112 - Warning: <img> lacks "alt" attribute
line 290 column 162 - Warning: <img> lacks "alt" attribute
line 291 column 11 - Warning: <img> lacks "alt" attribute
line 301 column 15 - Warning: <img> lacks "alt" attribute
line 329 column 1766 - Warning: <img> lacks "alt" attribute
line 332 column 1846 - Warning: <img> lacks "alt" attribute
line 343 column 11 - Warning: <img> lacks "alt" attribute
line 344 column 22 - Warning: <img> lacks "alt" attribute
line 344 column 63 - Warning: <img> lacks "alt" attribute
line 344 column 111 - Warning: <img> lacks "alt" attribute
line 344 column 161 - Warning: <img> lacks "alt" attribute
line 345 column 11 - Warning: <img> lacks "alt" attribute
line 355 column 15 - Warning: <img> lacks "alt" attribute
line 374 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 374 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 374 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 383 column 25 - Warning: <img> lacks "alt" attribute
line 388 column 267 - Warning: <img> lacks "alt" attribute
line 149 column 50 - Warning: trimming empty <font>
line 368 column 17 - Warning: trimming empty <tr>
line 371 column 50 - Warning: trimming empty <font>
line 125 column 68 - Warning: <nobr> is not approved by W3C
line 141 column 68 - Warning: <nobr> is not approved by W3C
line 177 column 27 - Warning: <nobr> is not approved by W3C
line 234 column 27 - Warning: <nobr> is not approved by W3C
line 276 column 27 - Warning: <nobr> is not approved by W3C
line 306 column 27 - Warning: <nobr> is not approved by W3C
line 360 column 27 - Warning: <nobr> is not approved by W3C
Info: Document content looks like HTML5
Info: No system identifier in emitted doctype
Tidy found 116 warnings and 0 errors!


The alt attribute should be used to give a short description
of an image; longer descriptions should be given with the
longdesc attribute which takes a URL linked to the description.
These measures are needed for people using non-graphical browsers.

For further advice on how to make your pages accessible
see http://www.w3.org/WAI/GL.
You are recommended to use CSS to specify the font and
properties such as its size and color. This will reduce
the size of HTML files and make them easier to maintain
compared with using <FONT> elements.

You are recommended to use CSS to control line wrapping.
Use "white-space: nowrap" to inhibit wrapping in place
of inserting <NOBR>...</NOBR> into the markup.

About HTML Tidy: https://github.com/htacg/tidy-html5
Bug reports and comments: https://github.com/htacg/tidy-html5/issues
Official mailing list: https://lists.w3.org/Archives/Public/public-htacg/
Latest HTML specification: http://dev.w3.org/html5/spec-author-view/
Validate your HTML documents: http://validator.w3.org/nu/
Lobby your company to join the W3C: http://www.w3.org/Consortium

Do you speak a language other than English, or a different variant of
English? Consider helping us to localize HTML Tidy. For details please see
https://github.com/htacg/tidy-html5/blob/master/README/LOCALIZE.md