Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

FPSC Classic Product Chat / To some of those who have questions with commands.

Author
Message
Flatlander
FPSC Tool Maker
19
Years of Service
User Offline
Joined: 22nd Jan 2007
Location: The Flatlands
Posted: 15th Feb 2012 00:29
This is not a flame but some friendly advice.

Instead of asking at first how they work, or do they work, or whatever, please test, test, and test some more. This is what I have always done and always will do. I like to say that I play around with the script commands to see what they do.

All you need is a very simple map with scripts containing the commands you're interested in and then run the test level and see what happens. Be sure and look at any example scripts that are available and change values if values are required.

I just think this is the best way to learn. It will stick in head after doing this.

Of course, if you can't figure it out then you can ask but you might have more of an intelligent question to ask.



BlackFox
FPSC Master
18
Years of Service
User Offline
Joined: 5th May 2008
Location: Knight to Queens Bishop 3
Posted: 15th Feb 2012 00:39
Agreed. I'll go ahead and add my two cents Canadian.

It is hard on the testers, such as Scene Commander and Flatlander, to try and solve an issue if it originally works for them and they can't reproduce the issue. They dedicate their time to help solve the issues to make this product as stable as possible for the rest of us.

Also, to augment what Flatlander requested, please also remember to specify the version of FPSC. I made a post in the script section with the same request- in order to best help, we need to know what version you are running. For example, it does not take much to specify "FPSC v1.19 Beta X". Chances are the issue can be solved if it is determined that the problem is the beta/version you are running had a fix applied that you missed.

The idea here is to try and solve the issue as best you can, and if you are stuck then by all means ask away. But please provide as much info as possible- version (including the Beta version), what you are attempting to do, what actually happened, what was it suppose to do. You get the picture.


Twitter: @NFoxMedia
rolfy
20
Years of Service
User Offline
Joined: 23rd Jun 2006
Location:
Posted: 15th Feb 2012 01:43
You guy's are legends (no I am not drunk....yet) you do so much to help numpty's like me when I get stuck with something (after I am finished banging my head trying to work it out for myself).

Awesome! Its one of those threads.
Ched80
15
Years of Service
User Offline
Joined: 18th Sep 2010
Location: Peterborough, UK
Posted: 17th Feb 2012 18:13
Using test maps like suggested is also a great way to hone individual game mechanics and individual script mechanics before adding them to your latest WIP.
Whenever I create scripts I create a simple dedicated level to test it out. I almost have 1 level for each script command. It's so much quicker than trying to work with a WIP level as they compile so much faster. Plus when you have 100s of different scripts running it can be hard to determine where the problem is. Working with test levels is so much easier.

bruce3371
15
Years of Service
User Offline
Joined: 4th Aug 2010
Location: Englishland
Posted: 17th Feb 2012 20:20
Quote: "Whenever I create scripts I create a simple dedicated level to test it out. I almost have 1 level for each script command."


That's pretty much what I do as well. I have a huge mapbank sub-folder full of these small test maps!

I try to only ask questions when I've already tried everything I can think of myself. However, occasionally, I ask straight away, when I simply have no idea where to even start!

maho76
15
Years of Service
User Offline
Joined: 31st May 2011
Location: universe-hub, playing the flute
Posted: 18th Feb 2012 02:57
Quote: "Whenever I create scripts I create a simple dedicated level to test it out. I almost have 1 level for each script command. "


problem with this method is that some commands are working ... well, not exactly against each other, but troubleshoot each other what you can only explore when building a more complex testlevel.

but i totally agree to you all to testtesttest instead of crying for help. you cannot call yourself a developer when you cannot develop yourself and the tools you are working with ... up to a certain degree, not everyone can do everything.

so its not a blame when asking questions here, its just a blame when asking a question that is described in the manual on page 2.^^

bruce3371
15
Years of Service
User Offline
Joined: 4th Aug 2010
Location: Englishland
Posted: 18th Feb 2012 15:47
Quote: "problem with this method is that some commands are working ... well, not exactly against each other, but troubleshoot each other what you can only explore when building a more complex testlevel."


That's a good point maho, which why I also have test levels which combine individual scripts to check they work to gether. For example, in my game Seclusion, I have a major sequence where a cascading explosion occurs. Although I did have some help with writing the scripts, I used multiple test levels to make sure it all worked once it was put together.

007
14
Years of Service
User Offline
Joined: 22nd Aug 2011
Location:
Posted: 19th Feb 2012 14:28
As a not so begginer in FPSC Script, i totally agree with this statement, that testing and trying by yourself is the best way to learn scripting.

It`s not hard, indeed, when you "get it", things get easy. I have done a lot of cool scripts for FPSC in less than 5 months of studying.

Also a good start point is downloading scripts that users here in forum created, and also get the stock fpi scripts and see how they work, test, and such.

A good advice for those who are begginers in FPI Scripting, study the Official Community Guide, it helped me a lot. But study all the examples, not just reading this guide. "Eat" this guide, go deep on it, i`m sure you will learn Scripting.

And for those who already work with Scripting, never forget the "Complete Syntax List" from our dear Ched80, because this is a "must have guide" for all FPSC users. Also the new version with includes all the Gunspec commands is an awesome compilation and source of knowledge

I never open my FPSC before opening this amazing PDF file....

Cheers,

007.

Goldenye 007 N64

Login to post a reply

Server time is: 2026-07-01 18:07:31
Your offset time is: 2026-07-01 18:07:31