0 Members and 4 Guests are viewing this topic.
As for running raw hex, you can use this program by Zeda: http://www.ticalc.org/archives/files/fileinfo/425/42536.html
Quote from: DJ Omnimaga on December 20, 2010, 01:56:01 pmAah ok. Just one thing, though, especially since it's an utility to help programmers: try to not make the readme excessively long. A lot of people are turned away by Celtic III readme because it's too long and they use xLIB readme instead. Some people prefer larger readmes, though, so it's a good idea to maybe include two versions. Some people just get lost when they see a wall of text. X.xMy favorite readme ever is the one for Celtic III. I like the huge ones. The DCS SDK is also one of my favorites. This sounds great, Hot Dog. As for running raw hex, you can use this program by Zeda: http://www.ticalc.org/archives/files/fileinfo/425/42536.html
Aah ok. Just one thing, though, especially since it's an utility to help programmers: try to not make the readme excessively long. A lot of people are turned away by Celtic III readme because it's too long and they use xLIB readme instead. Some people prefer larger readmes, though, so it's a good idea to maybe include two versions. Some people just get lost when they see a wall of text. X.x
Oh nice! Does that means we could also display strings of text that wraps on a less wide portion of the screen too? An example would be The Reign of Legends 3 convos.In my game, the text box took about most of the width where the map was displayed, but did not display over the HUD.
looks cool! I can't see what BASIC text games will become after this! btw, are you planning on making an APP version? I get a lot of RAM clear so keeping Corelate in RAM...
it could install and uninstall Parser hooks maybe?have a token to activate it and deactivate it.
Nice, this will change the token names only if the person desires, right?