Mystic Software Forums
Miscellaneous => Archives => General Discussion => Topic started by: DarkElite on July 08, 2004, 02:50:51 PM
-
Could someone tell me all of the problems with RPGCode on some computers so i can make my game formattable for everyone? (like xorlak's computer wont work with #color, and only #colorRGB)
-
RPGCode dosen't work on my computer....well...when I make it...and it seems that #MP3 dosen't want to play...MP3s, only wavs...but that's useally only for my games....and also when I try to make good programs they don't work...So only things that are so makeing games, so yeah. No probloms here really...I think...Well I have the latests non powerhouse of TK so yeah....
-
A bloody load has been fixed (by me...) for the next TK3.
Literally everything should work.
-
Literally everything should work.
Exept the Delay(.4) Razz
-
I dont mean the TK3, I mean the PowerHouse edition of TK2.2b
-
Well you're insane.
TK3! TK3! TK3!
Plus, 3.04 actually has an exe compiler (programmed by yours' truly...).
-
Well you're insane.
How is he insane? TK3 has been less then optimal in the area of RPG Code since the begining. If it will be better in a future release, we'll see. But he's talking about what currently works.
As for the original topic, the only other problem I can think of is decimal delays, in which things like #delay(.1) causes problems for some people, but #delay(0.1) doesn't (unless you're Cesque, in which case pratically any use of a period anywhere causes problems, heh...)
-
When TK3 first came out, I'll admit, I hated it.
But now it's actually looking good.
And all that do not submit... shall be destroyed! =P
Edit: Oh, sorry. I keep forgetting that not everyone has my trans3, heh.
-
also you #color() problem, right xorlak?
No, im not insane....why would i buy the tk2, and then never finish a game with it....plus i can only sell it (if i do...not sure yet) if i use TK2...
-
Yep. Interesting that it turned up on both my last two computers. It's only with the TK2.20b powerhouse, though (some sort of DOS incompatibility, I'm guessing, since those are DOS color codes).
-
I'm looking into that Color() thingy now. (In 2.20, that is)
The little bugger...! CBM didn't include the source for actkrt2.dll which contains the function for dos colors. Bah.
( I have that problem too )