In-game clock based on PC clock.

[NeoPGX]

So, you want a full menu scene with the options of changing the stuffs you mentioned?

Because you haven't mentioned this yet anywhere...

Are you using an options script? If not, would it be okay if I would make an addon for Yanfly's Options script with the features you want?

I am not up for making a new scene from scratch right now.

Yeah, that's what I wanted. Menu option.

I thought when I said "configurable in-game." would make it obvious I wanted menu options, apparently not. Next time I'll be more specific.

I am not using any options script. But I have considered adding one for audio configuration. (Of course you already know that since you replied to the topic.) So yes, go right ahead.

 

[Sixth]

Ok, I made an addon for Yanfly's System Options script with (hopefully) all of the features you wanted.


I also updated the main PC Timer script.


Here they are:


sixth_pc_timer_display_v_1_1.txt


sixth_pc_timer_yf_options_addon_v_1_0.txt


You should put them in this order in the script editor:


- PC Timer Display


- Yanfly System Options


- PC Timer Options Addon


You will need to edit the settings before you can use it, so make sure you do that!

 

[NeoPGX]

Ok, I made an addon for Yanfly's System Options script with (hopefully) all of the features you wanted.

I also updated the main PC Timer script.

Here they are:

sixth_pc_timer_display_v_1_1.txt

sixth_pc_timer_yf_options_addon_v_1_0.txt

You should put them in this order in the script editor:

- PC Timer Display

- Yanfly System Options

- PC Timer Options Addon

You will need to edit the settings before you can use it, so make sure you do that!

Thanks a lot I will be sure to test it out when I can. Right now I have a script conflict error to deal with.

 

[NeoPGX]

Thanks a lot I will be sure to test it out when I can. Right now I have a script conflict error to deal with.

Ok, I made an addon for Yanfly's System Options script with (hopefully) all of the features you wanted.

I also updated the main PC Timer script.

Here they are:

sixth_pc_timer_display_v_1_1.txt

sixth_pc_timer_yf_options_addon_v_1_0.txt

You should put them in this order in the script editor:

- PC Timer Display

- Yanfly System Options

- PC Timer Options Addon

You will need to edit the settings before you can use it, so make sure you do that!

OK  I finally got the chance to test it out and for some reason the option is not showing up when I go into system. What do I need to do exactly?

 

[Sixth]

Read the instructions in the header of the addon script.


You need to add the extra options in the 'COMMANDS' array in the settings of Yanfly's script.


It is explained in the instructions.


The options available depend on your settings in my addon script, so you will need to edit those before you can make working options for the timer window.


This is especially important with the windowskin and background image options, because if you try to change to a non-existent skin or background, you will get a crash for sure!

 

[NeoPGX]

OK I did as you instructed:

http://i790.photobucket.com/albums/yy186/starwarrior00/clockScript_Capture_zpshigu9m8a.png
 

But then I get this error:

http://i790.photobucket.com/albums/yy186/starwarrior00/clockScriptError_Capture_zpsagwa3jse.png

 

[Sixth]

You haven't removed the comment signs ( # ).


Remove them where it needs to be removed and it should work.


Anything colored green in the editor is a comment, so it won't count as the part of the code.

 

[NeoPGX]

I removed the comment signs like you instructed but the error is still there.

http://i790.photobucket.com/albums/yy186/starwarrior00/clockScriptError_Capture2_zpsw8dzijij.png

 

[Sixth]

Yeah...


That line, number 163... Yanfly wrote "Do not remove this.". Seems like you managed to remove it anyway.


That line should have a } bracket, not a ] bracket.

 

[NeoPGX]

well the game is coming up now that fixed it BUT the options are not there at all.

 

[Sixth]

Have you read my instructions? All of it?

Read it, letter by letter, ALL of it.

I don't think that my English is that bad, that one can not follow my instructions, or is it?

From line 57 to line 76, 20 lines in my addon script, not much, that is what you should read.

If after that you still don't know what to do, please tell me what part of my instructions you did not understand so I can write it in a more understandable way (if I can, that is).

Sorry if I sound rude, but it seems to me that you just skimmed through my instructions and expect things to work magically by their own.

I could have simply hard code all the things for you, but I always write my scripts in a way that all people here could use them if they want to.

Therefore, all of the settings I added are optional and they require to be setup before any of them will show up and work.

Even if you only use scripts and not make them, you will still need to learn to use them. And that is only possible if you read the instructions, more times if needed.

Hidden shortcut:

Spoiler

    COMMANDS =[      :window_red,   # Changes the red tone for all windows.      :window_grn,   # Changes the green tone for all windows.      :window_blu,   # Changes the blue tone for all windows.      :blank,      :volume_bgm,   # Changes the BGM volume used.      :volume_bgs,   # Changes the BGS volume used.      :volume_sfx,   # Changes the SFX volume used.      :blank,      :autodash,     # Sets the player to automatically dash.      :instantmsg,   # Sets message text to appear instantly.      :animations,   # Enables battle animations or disables them.      :blank,      :switch_1,  # add this line!      :switch_2,  # add this line!      :switch_3,  # add this line!      :timer_pos,  # add this line!      :timer_skin,  # add this line!      :timer_back,  # add this line!      :timer_color,  # add this line!      :blank,      :to_title,     # Returns to the title screen.      :shutdown,     # Shuts down the game.    ] # Do not remove this.

 

[NeoPGX]

Its fine really. The problem with me is that I tend to get confused very easily and my mind doesn't catch on to something unless it is given to me straight.

But give me time and I'll eventually figure it out.

Your instructions tell me that I should configure the settings below but I'm not quite getting it But I'm guessing the spoiler you added is a pointer.

EDIT:

Ok I got it working now. Thanks.

 

[Sixth]

That spoiler is from Yanfly's script. That is the setup for what shows up in the system options menu in the game. I marked the lines which you should add there if you want those extra options available in the system menu.


But you will need to configure the settings in my script to make these new options function how you would want them to function.


The "settings below" refers to my settings in my addon script.


Several things can make your game crash if they are not configured correctly:


- The most important ones are the windowskin and background setups. If you enter a non-existent file name there and change the skin or background to one of them, you will get a crash upon exiting the main menu. Windowskins used should be in the /Graphics/System/ folder, while backgrounds should be in /Graphics/Pictures/ folder.


- The other one is that the 'Position_Setup' and the 'Position_Names' should have the same amount of available options set up in my script. If one got 5 defined available options, than the other should have that many too. These settings are paired, just like the 'Color_Setup' and 'Color_Names', so the same rule applies to them too.


- And the last one is entering an incorrect format for a setting.


For the position setups, it is always an array with 2 numbers, where the 1st number is the X value on the game's screen and the 2nd one is the Y value.


For the color setups, you can either enter a single number or an array with 4 numbers in it. The first way would take the color from your windowskin used for the timer window, the second way will take the direct RGBA values you have entered in the array.


For the rest of the settings, they are all strings.


These are the most important things to note in my addon settings. If you did everything right, you will not have any problems.


The position setups I made were made for a timer window with the following properties:


- width = 150


- height = 48


If you got the same properties for your timer window, you can keep those settings. Those settings will add the options to position the timer window to any of the corners on the screen or to the top center or bottom center on the screen.


Well, I covered most of the stuffs, so I hope you will make it work without issues.

 

[NeoPGX]

Seems I am now having another issue. Incorrect position of clock on the map. Presumably caused by using a resolution much bigger than than the VX Ace default. I have a resolution setter script and and using the modified Dll of the high res project.

http://i790.photobucket.com/albums/yy186/starwarrior00/Capture_clock_topright_zpscvuivwz2.png

http://i790.photobucket.com/albums/yy186/starwarrior00/Capture_clock_bottomleft_zpsiwrh7awd.png

http://i790.photobucket.com/albums/yy186/starwarrior00/Capture_clock_bottomright_zpsv3ppctu2.png

Top left's position is correct however. I didn't test the top and bottom center positions. 

 

[Sixth]

That should not happen.


I used Graphics.width and Graphics.height to always count the correct values.


Only one thing could influence this.


The script which you use to change your resolution should always be at the top of your custom script list. If it comes below my script, it will read the old resolution (the default one) for the settings of the timer window.


So, make sure that the script where the resolution change happens is at the top of your custom script list.


Optionally, you can change the settings of the position options in my addon script.


You can use simple numbers to set up the X and Y positions directly on the screen instead of using Graphics.width and Graphics.height.

 

[NeoPGX]

That should not happen.

I used Graphics.width and Graphics.height to always count the correct values.

Only one thing could influence this.

The script which you use to change your resolution should always be at the top of your custom script list. If it comes below my script, it will read the old resolution (the default one) for the settings of the timer window.

So, make sure that the script where the resolution change happens is at the top of your custom script list.

Optionally, you can change the settings of the position options in my addon script.

You can use simple numbers to set up the X and Y positions directly on the screen instead of using Graphics.width and Graphics.height.

The resolution setter script was at the very bottom, I put it at the very top and the issue persists.

Here is the script I use:

http://forums.rpgmakerweb.com/index.php?/topic/33783-resolution-selection-script/

 

[Sixth]

Yes, that script changes the resolution after the game has started up, and that is after the modules has been loaded, so the module will not recognize the change in Graphics.width and Graphics.height.

I made a little tweak in my base script, so it will be possible to get the correct width and height of the game's screen even with that script:

sixth_pc_timer_display_v_1_2.txt

After you replaced my base Timer script with the new one, you can change the settings for the position options in my addon script like this:

Position_Setup = { # <-- No touchy-touchy! 0 => [0,0], 1 => [[-Window_Setup_Map[:size][0]],0], 2 => [0,[-Window_Setup_Map[:size][1]]], 3 => [[-Window_Setup_Map[:size][0]],[-Window_Setup_Map[:size][1]]], 4 => [:center,0], 5 => [:center,[-Window_Setup_Map[:size][1]]], } # <-- No touchy-touchy!Window_Setup_Map[:size] will read the settings from my base script, so you don't need to edit the width and height at both places, only in my base script.But of course you can change those to direct numbers if you want.

I explained what changed with the position setups for the map timer window in the new script, so make sure to read them.

It should work now, regardless of what resolution you are using, because the correct position is decided in the class itself, and not in the module.

I haven't tested it thought, so that waits for you to do!

 

[NeoPGX]

I tested it out and the alignment is perfect now! Thanks!

 

[ShinGamix]

What about the pc date? That could be useful in an animal crossing style game?

 

[Lunarea]

This thread is being closed, due to being solved. If for some reason you would like this thread re-opened, please report this post and leave a message why. Thank you.