Jump to content

  • Log In with Google      Sign In   
  • Create Account

Servant of the Lord

Member Since 24 Sep 2005
Offline Last Active Yesterday, 09:27 PM

Posts I've Made

In Topic: Tactics RPGs with an actual "game" (world exploration, etc)?

Yesterday, 09:13 PM

If you are between the wall and the enemy, stay away from the walls - the closer you are to a wall, the more likely bullet ricochets, explosions, and shrapnel will hit you.

 

On the other hand, if the wall is between you and the enemy, hugging the wall gives you protection.

 

If you want to play with that mechanic, I think it'd need to be explained clearly, and also need to be visually noticeable (visible bullet trails and "Wall ricochet!" floating text when a ricochet hits you), especially with the explosions - if a rocket hits someone, it might spread out somewhat in the open space around him, but if it hits a wall, the explosion would not only be channeled along the wall, but shrapnel (especially wall-debris) and the heat/force would bounce back from the wall outward.

 

b42cc30c92.png

(Note: the above is me speculating - I have no knowledge of the actual physics in explosions)

 

I'd do it in a generic way that makes playing with explosions (from grenades and mines and etc...) in enclosed areas (like inside buildings or courtyards) an enjoyable almost bomberman-like experience. I haven't seen that done in a turn-based tactic game before. And I'd make shrapnel and ricochets be a big deal as well.


In Topic: defend sacred animals quest

28 August 2016 - 08:54 PM

Or let the player kill everything and everyone for no reason.

 

Don't forget to eat the hearts to gain their courage. Their rich tasty courage.


In Topic: Tactics RPGs with an actual "game" (world exploration, etc)?

27 August 2016 - 03:35 PM

Have you tried Final Fantasy Tactics for the PS1?

(There were some other installments for the GBA, but the story was supposedly less interesting)


In Topic: Week of Awesome IV - The after party/judging thread

27 August 2016 - 10:35 AM

I'm very pleased with the scoring our game got! I'm also very satisfied with the amount we were able to accomplish, and don't think I could've pulled off much better.

While we only got 7th place, it's obvious that our game wasn't scored badly (we got excellent scores), just that other competitors' games were slightly better.

 

Next year I'll know where to invest more effort: sabotage.  :lol:

 

Thanks for the enjoyable competition, slicer, and thanks for the judging effort, monsieur judges!

Having judged last year, I know that judging can be just as exhausting as actually competing.


In Topic: Errors that effect a computer's system.

24 August 2016 - 08:58 PM

what is BSOD and what are the blue screens about?

 

When the Windows OS encounters an error, it'll auto-recover from the error and sometimes pop up an error message, or even silently just record it and keep on going. This happens pretty frequently. In the last two months or so, your computer probably encountered several hundred errors and automatically recovered without you even knowing about it. A quick check (Windows key + eventvwr, on 'System' filter by 'Error'/'Critical') shows I encountered three yesterday, and 2,168 in the past year. That's very normal and isn't a blue screen.

 

When Windows can't automatically recover silently, it crashes and displays an error screen, which is displayed as a blue screen with white text. Here's an example:

 

unmountable-boot-volume.png

 

(Note how it says Windows automatically is shutting down to prevent harm - this is one of the reasons why you don't need to worry)

 

Here's the more modern one:

BSOD_Windows_8.png

 

Usually, after restarting, Windows continues to work fine, having recovered during the restart. Sometimes you have to do some repair work though. For example, if the blue screen was caused because a piece of hardware naturally wore out and broke (unrelated to any code you run), then obviously that piece would need to be replaced before the blue screen would go away.

 

Note: After 11 years of programming, I only saw a blue screen once (okay three times - I repeated the exact same process to see if it happened again :P), it didn't damage my computer, just crashed it and it restarted fine. That was eight years ago, and I haven't seen one since then.

 

I was under the impression that people incorrectly call blue screens "BSODs", but they are merely blue screens, and the true Blue Screen of Death is when Windows crashes so badly, the blue screen is shown but no error message - it's just a blank blue screen, and your system is bricked. However, I can't see anything to verify that on google.


PARTNERS