Credits 1.17

[Yuri Patrick]

I didn't want to be asking for help again so soon, but I can't get Credits 1.17 script to work. When I import it, everything goes fine. When I run the demo everything is fine. Yet, when I try to compile my game after importing the credits scm file, it tells me:

Credits.asc(80): Error (line 80): Undefined token 'StrCopy'

Anyone know how to fix this?

And before anyone asks, I've already tried to Credits 2.0 plugin, but can't remember how to install a plugin nor can I find any decent information on how to work Credits 2.0. The .chm help file that comes with 2.0 is utterly useless. There is nothing in it. Just blank sections. Soooo....?

[Khris]

StrCopy is old-style code. You can try turning on backwards compatibility in the General settings (set "Enforce object-based scripting" to false).

Also, if you link to the place where you got the modules / plugins, we can look at them without having to search for them ourselves.

[Yuri Patrick]

OH! I didn't even think of that. Thanks. And as for where I got it, I got it at http://americangirlscouts.org/agsresources/AGS%20resources/plugins/agsCreditz.zip

I tried what you said about making it allow old-style scripting, but it still won't compile. Exact same error. I'll go through the demo's settings and try to find out which one is the one that will make this work.

If I still can't get it to work, is there a updated version of StrCopy? I tried String.Copy() and it totally freaked.

[Yuri Patrick]

Alright. I got it. In the General Settings, under Backwards compatibility, you have to set "Enforce new-style audio scripting" and "Enforce new-style strings" to false. "Enforce object-based scripting" doesn't even fix it, and that can stay true.

And now it works.

[Yuri Patrick]

Alright. I got credits to work finally. But now I have a new issue. And hopefully someone is familiar with this plugin...

I can get my credits to do the standard scrolling movie style, I can even get the right font and stop them where I want them to start. However, no matter what I do, they start at the bottom of the screen. Hopefully someone can help me figure out how to get them to start at a different Y location.

I have tried

Code: ags

credits[0].StartY = 100;

and it still won't start at Y 100. It insists on starting at the bottom of the screen. Help please.

[Gilbert]

BTW, the most recent version of the module is v1.19. Is there reason to use an older version? I think there are some bugs fixed in the newest version and that it's more compatible with the new scripting method, so there should be fewer problems, as you're using a fairly new version of AGS already.

P.S. Questions regarding a particular module or plugin are best asked in its respective thread in the 
Modules & Plugins section. I have thought of moving this thread there and merge with the module's thread, but since this thread is about a particular (former) version of the module I decided to leave it here at the moment. If you eventually decided to move on and use V1.19 instead, do post in that other thread if you still encounter problems, and I will lock this thread.

[Khris]

It should be pointed that some (most?) of the stuff on that page is really outdated. It's always best to search the modules section of the forums first.

[Yuri Patrick]

Yes. The problem with your statement is that as I said at the beginning, I did search for a newer version and I found 2.0. But it's a plugin, instead of a mod, without any instructions at all.

[Yuri Patrick]

ARGH! Alright. I managed to get the 2.0 plugin installed, finally. Feel kinda dumb now. Also... I managed to track the creator back to their home page but cannot get in touch with them. I think that their page has gone stale as the contact us form is broken and so is the registration page for their forums.

So, I'm starting to wish I knew how to program in C++ and that there was more info on this plugin. I found a rather weak tutorial on our forums about 2.0, finally. *SIGH* If only I knew C++, then I could do all of this myself.

[Gilbert]

Since you no longer use V1.17 now, I'll lock this thread.

Do post in the proper thread if you still encounter problems in the future:
Module version
Plugin version

And if you don't know already, these two are different things. V2.0 of the plugin is actually even older than V1.19 of the module.