RegalPrime-UnityEngine v1.4.1 - 8-18-15

[RegalPrime]

https://www.mediafire.com/download/a9awltjiqgw7fhi/I+Wanna+Help+the+Cat+v1.1.zip
Found some last minute bugs and got them fixed (that Reset function on the boss screen messing up again).
If you tested the first version, let me know how this version feels. There are still a couple of things I wish I could smooth out, but things are better than before.
If you haven't tested this game / engine yet, feel free to this version. There is a scene select on the main loading screen, so you can jump around to any place in the game.

Ooohh, also the new Unity version was just released this week. Which means I can update my version (hopefully nothing breaks)
They added in the new GUI stuff, which means I will have to watch all the tutorials and start testing it out. When I get things settled I can update the main loading game screen.
It should be a lot easier to create and design with the new patch. Seems like a fun mini-project.


Well, it is time for the new game / engine release. I will end up being gone all next week so I worked on getting this put out this week.
The amount of backend things I have changed, I would bet there are some bugs somewhere. I ended up adding in a few things I wasn't planning, but the game should run a lot better now (I'm sure its not 100% perfect, but its a big improvement).

** Update Notes **
I put back in the default unity pregame screen to allow for changes in resolution size.
It also has options to change the button settings, but do so at your own risk.
I have not messed around with that window and I have no clue how it interacts with my in game settings.

Platforms pull less when jumping through them (horizontally)
Vertically is still a bit pully though.

Torch pickup / drop is now the X button.

Changed how Button presses were done. They should be more immediate.
Hopefully this should lessen the unresponsiveness.

The below were added to detect when the character is close to a solid object and will move them a shorter distance to prevent the physics bug (where you could clip a deadly object in another block and die)
- Added in ground check
- Added in wall check
- Added in ceiling check (no preventive movement checks yet)
-- There is still a small possibility that you will clip a ground object when falling (you fall way faster per frame than moving), but it is an extreme improvement over the default.
-- This is because the AoE ground check is not as big as I would like atm due to another problem that arose (when I fix that, I should prevent this from happening)

Reset Data on the Loading Scene is no longer an option
- Difficulty options were added in instead (easy / medium / hard)
- Items without the proper difficulty permissions will be disabled
- Nothing in this game uses the difficulty option, but the option and script have been written

Boss Room - cant go backwards a screen
Boss - Spinny hands attack - No RNG on the attack, there should always be a safe spot.
Boss - Paws have 5hp each. 10 was just too much.
Boss - I noticed the death timer on the projectiles was too high and objects were hanging around too long.
-- Changed the death timers based on each attack to the smallest time needed for an object to leave the screen (less objects active at once, less calculations)

Object Pooling put in the new object spawner script (has a variable to disable it if needed)
- This effects any screen with constant spawning of objects (including the boss)
- Objects are now reused instead of constantly creating and destroying themselves (this should increase efficiency).

Object Pooling added to shooting script (reuses bullets)
I think the spike treadmill uses object pooling now as well (Im sure there are others as well).

Added the Reset() Event to every script
- This allows one script to call the Reset() function on all available scripts that are loaded in the scene
- The Reset() function is added to each script that needs it and will change the script back to the initial settings / position / etc
- Instead of constantly deleting and reloading the same scene (and its objects), using this will allow the scripts to reset themselves giving the illusion they have been reloaded
- More efficient, but there is the possibility that some of the Reset() functions could be wrong and thus have bugs.

Reloading the same scene will now call the Reset() Event instead of deleting and reloading the scene (and off of its objects)
- This will allow for key presses to be active when constantly reloading on the same screen (this however may not hold true between scenes)

Commented on every script and sorted them all out

Object pooling went in ok, but the Reset() event on some scripts was a pain (ie the boss / spinny room).
Im sure it is a lot easier to write a script from scratch with the Reset() event in mind instead of modifying an already existing script
It wouldn't surprise me if a few bugs might show up now.

Scene select is available on the loading page - This is for the people who want to jump to a certain scene to test (or just want to browse through my game).
Just move the slider bar to the correct scene number and click "Jump to scene"
Using the jump to scene will use either your current used slot or slot 1 by default.

It gets fairly old writing the back-end scripting so I took a few days off and wrote a nifty background effect.
When this script is triggered, it sends a shockwave-like color changing effect outwards through out the valid tiles.
+1 test scene - Has a few of these trigger objects on a empty scene with different variables set to give a feel of what this script does
+3 new scenes using this script - Created a simple gimmic involving this script.

For ease, I created a button on the loading screen that allows you to jump to these new scenes.
For now, they are in the game, but not attached to any other scenes (they are actually after the "you win scene". After I find they are bug free, I will put them somewhere in the middle of the game.

Picture of the first new scene

(click to show/hide)

[RegalPrime]

https://www.mediafire.com/download/slyxbav7kimpf3a/I+Wanna+Help+the+Cat+v1.2.zip

- New GUI system hype !! -
Took me a bit of time to figure how to use it, but I am getting the hang of it. I am also glad I waited instead of learning the old system then learning this one.

Created a new Loading screen using the new GUI. It look nice and crisp and allows for me to change design and whatever without totally breaking the connections anymore
It is pretty plain at the moment, but it is a lot better than the old version.

(click to show/hide)

Created a HP Bar GUI + prefab. The HPModule script can use this and it works well displaying the objects / enemies hit points.
Has various options on when to display the HPbar / speed of hp removal / etc.
- Enabled the option to show the HP bar when the bosses paws are hit.

Replaced the basic label script with the new GUI system. Signs and character chat boxes look better. I didn't go overboard creating boxes. Just a simple bordered square that can be expanded upon later. A lot cleaner to work with compared to the old script based GUI.

Created a game over screen using the new GUI. It looks 100% the same, but it needed to be updated.


Finally got around to totally rewriting the camera script. Whereas it worked well before, it was a huge ugly inefficient mess. After sketching out the design, the rewrite went smoothly.
Also updated the script that triggers the camera manipulations when the player trips a spot. This one had a few problems just because I totally changed how the camera script worked from before, but now I think it is all fine.

Save point added an option to reset the default camera position on trigger, which is helpful when resetting the camera on larger scenes (where the camera follows the player).

Put the 4 scenes added last patch into the main game scene lineup.

- Stuffs -
I am a bit disappointed in not being able to smoothly access preventive measures when using physics. Physics are calculated all the time (when there is free time), whereas my preventive checks are calculated once a frame. Most the time the guy will move very well and other times you notice a bit of a snapping effect when running into a wall. I mean its better than dying to objects inside of walls, but I need to dig more into how to do this better. I will probably flesh out the 100% transform 2d-controller and see how it works in game. Sadly it will not have the power to move up slopes and I will have to change a few things if that happens (will have to figure how to do slope climbing later I would guess).

I have been cleaning up the engine files as of late (when I haven't been programming) and am getting to the point where I am feeling better about releasing the engine to the public.
As long as people understand the state the engine is in (not perfect), I have no qualms about releasing it in a somewhat messy state.

[RegalPrime]

Hmm, didn't know it was that long since my last update. I probably said this above somewhere, but I really hate programming the more complex back end stuff for a long period of time, but it seems that's all I have been doing since the last update. Also, took some time to learn more about the inner workings of unity so I can program smarter.
No engine / game update, but I am working on a testing room I can use to test some problems / get feedback and might release that later.

Did some research on when unity polls key inputs and when the screen is rendered and changed how key inputs are done again.
Updated and cleaned up both movement scripts. After updating my pixel movement script I found a logic problem where even when not moving, the script was grabbing no movement as an input for that frame. This could cause a one frame delay when actually wanting to move. Knowing when the frame renders now allowed me to clean up the scripts and fix the weird snapping that happened at times when getting close to a wall.

Made the velocity and pixel movement scripts the child of the 2dcontroller and thus can be used interchangeably in the engine. Rewrote the parent to be more generic and encapsulated most of the variables. Was worried about getting this to work right, but the pixel based guy script interacts with all the game objects like he should, so I guess it worked.
IN SHORT, there is a prefab for the physics based movement and a prefab for the pixel based movement character. Both can interact with all of the other objects in the engine without having to change any other scripts.

Put a line of code in the spawn controller so that I can force which guy spawns through the entire game

After having some time, I finally found the new settings to change the size of the collider buffer (came in with the newest patch).
Previously, the default setting caused the player to have a 1.5 pixel extra buffer when "touching" another collider (ie a wall or even the triggering of a deadly object). This buffer made the character much fatter than its normal collider size and caused some weird issues (poor accuracy of jumping / bonking head early / etc)
The settings now allow to go down to 0.01 pixel buffer (a pretty big difference)

This is good HOWEVER, this buffer is used in the physics to help calculate collisions of solid objects. The physics guy collides with corners of certain square objects very weirdly when the buffer is set extremely low. He will kind of bounce off of edges a bit. I am not sure if there are settings that can increase the accuracy of these collisions or the rate in which they are calculated. The good news is that the pixel movement based character does not have this problem and no longer has this collider problem.

Of course, having lost this buffer, some of my objects started acted weird at times (falling through moving platforms and whatnot)
I spent a bit of time updating some major scripts. I haven't had the time to test many of the other object interactions to see if they held up.

I also took this time to figure how and when colliders trigger so that I can create more accurate "deadly objects"
Previously the spike's edge collider was just thrown on "by eye," but now I have a better idea of what to do next.
With that 1.5 pixel fatty buffer before, objects triggered before they should have and were inaccurate, so I shrunk the collider size to compensate. I no longer have to do this and I need to change it back.

Serious update on CalculateChecks script (used to calculate the distance between 2 object's colliders)
- This script is used to detect when the character is grounded and near other solid objects (for movement / gravity reasons)
- AoE calculations to detect wall / ground / ceiling / pits are now generic and will know how to calculate the offsets based on that objects current settings
- Took out the need to have separate code for if the object is flipped / if facing a certain direction / scaled a certain size / etc
- Increased the accuracy of these checks (there was a few places when the character was on the edge of a platform, but this script said he was not grounded and thus played the falling animation and caused him not to be able to jump / refresh the jump)

- Updated the formula to calculate the distance to a wall / ceiling / ground object to deal with all of the variables in one formula
- Calculating the distance to the ground for an edge collider was updated as well (distance to an edge collider for wall / ceiling are not in yet)

AI script now uses check surroundings script to detect walls / ground / etc (same script that is used on the main character. CalculateChecks.cs)
- Added pitcheck to the script to detect if there is a pit in front of the object (used to tell the AI to turn around when patrolling)
- No longer need the offset objects on the AI gameobjects, which should simplify things a bit.
- AI acts more stable because there is no need to manually set the offsets on the gameobject.

Climbing changed to detect walls so there is no studdering / wiggling when climbing and humping walls (also Uses the CalculateChecks.cs script)

Teleport in room script - maintain offset was bugged and fixed.

So, overall, a lot of progress in fixing some major problems that were plaguing the core of this engine (those colliders ).
Next thing to fix is the aftermath of shrinking that collider buffer and its effect on interaction with other gameobjects (will involve going through most of the prefabs / scripts that interact with the character). Also need to figure how to make the physics movement guy collide with corners better when the collider buffer is set very small.

[RegalPrime]

The whole collider issues was one of the main reasons why I haven't released the engine. With solving a majority of these issues + having a workable alternative character that works well (the pixel movement guy), I've found there's no reason to not release it in its current state.

There is still a lot of old items in the engine I wish I had time to rewrite or even add, but for now it is stable enough.
- Uploaded and downloaded and tested to make sure I could open it and whatnot.
- Seems everything is in order
https://www.mediafire.com/download/x1w70hkaq8b11y8/RegalPrime+-+UnityEngine+v1.1.zip


Updated the engine and released game version 1.03
- There are 2 downloads, one uses the physics guy and one uses the pixel based movements as the main player
- Pixel guy moves via transforms and requires almost no collider buffer. Only con is the inability to go up slopes
- Physics guy moves via physics forces but requires a larger collider buffer to remain stable. Increased collider buffer makes the player collider fatter
- Update includes what was listed in the last post + below
- Most of these deal with the aftereffects of messing with collider settings

Hill climbing works on physics guy again
Distance to wall calculation updated to deal with edge colliders
Distance to ceiling calculation updated to deal with edge colliders
Climbing works while upside down
De-childed the character if they are on the treadmill when the individual object recycles itself

Moving platform fixed
- It wasnt that much of the collider size, but the value used to determine when the player was above the collider
- Changed this to a public variable and increased the collider box. This way it can trigger earlier yet still calculate correctly

Reloading a scene with an animation of a dead unit cause a bug - Fixed (forgot to reset the IsDead tag)
Sliding down an edge collider - Am assuming some aftereffect of changing the collider buffer / penetration for penalty values (Fixed)

Found a bug that deals with some weird combination of pressing and releasing the jump button multiple times within one? frame. Happens very rarely.
Need to pinpoint what is actually the cause before attempting a logic fix.


Basic Tutorial
Simple tutorial to cover a few things

(click to show/hide)

- So you have no clue what to do -
Download unity at https://unity3d.com/unity/download
Download the engine at https://www.mediafire.com/download/x1w70hkaq8b11y8/RegalPrime+-+UnityEngine+v1.1.zip

Watch the 10 beginner videos on how the editor works. Each is a few minutes long
https://unity3d.com/learn/tutorials/modules/beginner/editor
The other tutorials are useful as well

Unzip engine and open unity.
Open project -> Open other -> select the folder of the unzipped project and open

- Creating a new scene -
File -> New scene
File -> Save scene. Put it into the scenes folder or create a sub folder of it
In order to add / remove scenes from the game goto File -> Build Settings
You should see a list of all of the scenes in the game. Clicking and pressing delete removes them and you can add current scene via that button. You can also move them around by dragging them.
You can probably remove all except the title and load game screen (the first 2 in the list)

- Your new scene -
Your new scene will have a camera in it. Delete it. Now your scene is 100% blank.
Goto Prefab -> Map Objects and select either Entire Room setup or the alt version and pull it onto the scene.
Make sure its X/Y/Z coordiates are 0
Press Play. Congrats your scene should works. Sorry the character is dark. This is because he has a shadow material on him so light effects him (no light = dark). Will tell you how to change this later.

- Objects on your new scene -
GameController = This is how game data is saved and loaded. It also includes a reference to the character for easy access.
The information on the prefab will be populated when the game runs. This is more for reference and not for you to put your own values into (havent hidden the data yet).

PlayerSpawnController = This contains which character spawns and also the locations (or indexes) where he can spawn.
The indexes are represented by the little yellow diamonds beside the warps.
The prefab already has the GuyCharacterPrefab_Physics preloaded into it.
Feel free to drag the pixel version from Prefab -> GuyExtras, GuyCharacterPrefab_Pixel

If you are using the pixel version you have to change a setting.
Edit -> ProjectSettings -> Physics2D, Min Penetration for penalty = 0.0001
If you are using the Physics version change it to
Edit -> ProjectSettings -> Physics2D, Min Penetration for penalty = 0.005

So, remember that your character was dark. If you arent using lighting, look on the SpriteRender component on the guy prefab.
Under material it should show "SpriteShadow." Change it to "Sprites-Default." This can be done for any sprite based object. I used lightning in all of my scenes for effect so by default I made the material shadow.

MusicController = This is the song that plays on that scene. Drag another song from the audio folder to change it.
If a scene transitions and the song is different it will automatically fade and play the new song.
If the scene transitions and the song is the same, it will continue to play.
The music controller also deals with saving / loading / playing / fade / unfade of sound settings

RoomNavigators (purple boxes on each side of the scene)
These navigate between scenes and tells which index / room the character should spawn at (click on the object to see its values)

Save point = It is a save point  :p

So thats it, if you create and add multiple scenes to the build settings. You will be able to traverse through them.

- So you wanted things in your room?? -
Hold V = Snapping

Prefabs are your friends. Everything in that folder is drag and drop stuff for your scenes.
Need some blocks?? Prefab -> MapObjects -> Blocks32x32
Need some Spikes?  Prefab -> MapObjects -> Dangerous
Want some more fancy objects?? Prefab -> IngameObjects

Remember you can also browse my game scenes for examples of the prefabs.

If you dont know what to do, drag it onto the scene and hit the play button.
Mess with the settings and whatnot. As long as you dont overwrite the object in the prefab folder, you can always grab a new default one. Also, settings made while the game is in play automatically revert when the game is stopped.

- Certain things -
A few things about certain tags and layer settings (you need a collider on these objects)
tag = deadly - An object with this tag will kill the player when it touches him
tag = bullet - An object with this tag will damage an enemy
tag = climbable - Player can climb these objects
tag = ground - Destroys bullets

layer = ground - This is important. This layer tells the player he is actually grounded, so objects with that layermask will reflect that.

There are some wierd advanced settings you can screw around with but I figure at this point I dont want beginners digging around in code. This should cover the basics. Let me know if anything needs to be expanded upon.

[RegalPrime]

After the initial release, I decided to take a week off of this project (ended up being almost 2 though).
I had a bit of trouble wanting to go back to it because I had no clue what to work on next.

Long story short, I figured I would try to make an avoidance boss.
I had a super script that did a whole bunch of stuff and was used in creating the cat boss in the game (and other things). This includes everything from movement to spawning of objects and shapes. I didn't want to fix what was there, because it will break the other stuff in the game and I really don't want to mess with the boss code anymore. I figured there was no better time than now to create a version 2.0 of that script.

So, I am slowly moving over each function and testing / expanding / and simplifying everything about them. Some of them were, /// uugh, such a stinking mess, Im surprised they worked, lol, those needed total rewrites. Luckily, I was able to condense a few functions together. I have a few more main functions to bring over and then I think I will try some basic avoidance timing and testing to see if  everything is working all right. I think it will go all right, but I am afraid that I may run across some unforeseen problem mostly dealing with manipulating multiple design options in an easy way. In the cat boss I was able to do it, but I wasn't happy with the way I had to code it, hopefully this will change with the new function design.

-Very minor engine code fixes

[RegalPrime]

Parsed the entire song for the avoidance fight and took notes of all the important times / repeats / stanzas / chorus and whatnot. Figured I would do extra work upfront so I dont have to do that later. Divided the song into 10 sections. Added simple actions for the avoidance fight and set them to the timing. I can start at any of those sections and test from there (dont have to listen through the entire song all the time). Its nice to be able to just plug in the starting time and how long you want something to go for and it just works. At this point I had a crappy avoidance with good timing.

Was a mix between jumping between the avoidance code and updating the major scripts, but for the most part, all of the old functionality has been put into the new scripts. All the new versions of the functions look so nice comparatively. Added extra functionality as well. No overloaded functions as of now just so I dont have extra work to do if I do some major restructuring. I have a few more things I need to add though, but its 100x better than the old version (probably another child script to deal with custom stepped effects to keep them out of the main scripts).

Overall I kinda just picked a random anime song from youtube that seemed to have good segmentation. Due to the length I felt I would keep things fairly simple and extremely low RNG. After the other script update, I added more complex actions and spawners. Also added a few test custom actions which were a lot easier to create with the last iteration of the script. Fancied up the room and I decided to release a version to show what Ive been doing. I have a lot more functions that I wish I could of put in, but it would of just made things more complex.

https://www.mediafire.com/download/rl5wavilolbx6n7/Avoidance+Testing.zip
A few things.
Song is 3.54 mins long. Has a few repeat sections (chorus) were the "animation" is the same / similar. This was to keep things simple.
The title / save_load / ending screen are the same from the engine.
There is only one screen in this build (the avoidance boss)
Shoot the yellow box to start the avoidance fight.
All of the fruit projectiles have a circle collider on them, so the stems are safe.
I wish I had some better tiles to fit the nature of the song, but it looks ok.

I wouldn't consider it a bug, but during testing, I have the song skip to a certain time at the start of each section of the avoidance fight. This was so I could start the fight in certain sections. Some are seamless and you wont notice it, whereas others will have a very slight noise. In the real release, I would just comment out the skip to X spot in the song, so for now it is still in.

Nothing too fancy and I wish I could of thrown some other script function calls in to show better what I can do with the rewritten scripts.
Overall, this helped me iron out those problems from the older version and should make future bosses / avoidance so much easier. It was seriously easier and cleaner looking than my cat boss script, so that was a good thing.

[FlyingTaoster]

I have to admit, i am pretty impressed.

I tried out your game awhile ago, and the physics were certainly a bit different from the regular Guy physics in game maker. My playthrough of it ended when I had saved on the spot where one of those enemies in the later area is that you can kill. woops  Despite me save-screwing myself, it was an enjoyable experience 

This avoidance however, even though it is somewhat plain and has it's lulls in action, is an impressive feat. The timing of the attacks match the song well, and some of the attacks are in themselves impressive. The game you made somewhat piqued my interest in making a fangame in unity, but with what i've seen in your preliminary version of the avoidance, I can't wait to see what else you'll be able to do with it 

[RegalPrime]

The whole saving inside of the monster problem can be resolved just by hitting the Q button (was in the readme :p not that I expect most people to read them). Dont worry I did it a few times as well. Pressing R, normally restarts at your save point and resets the room / monsters to their default positions, whereas Q will restart you at the start of the room and reload the scene from scratch. Of course you can always skip to any room you want from the main save / load screen in the current build and start the scene over that way.

I appreciate your feedback on my engine. My goal is more to make sure my code works rather than make the best game / avoidance ever and Im glad you noticed that.
Overall, the avoidance code is stupidly simple looking because it just calls all of these functions Ive been working on. I think it took me longer to diagram the song than write the boss code.

Here is one of the phases of the avoidance boss.
I dont have overloaded functions as of yet (so there is a lot of null / new Vector2(0,0) fillers that probably wont be there later)
You can guess what stuff does just by glancing at the code.
X object, Do this, at variables X /X / X / X / etc

(click to show/hide)

SV = This is the position of the song it skips to. It is also used as the offset counter for all the calls in that section.
The first variable in each function call is the delay in which it starts and since each coroutine runs separately, it need to subtract SV so it triggers at the right time.
So Creating the first circle happens at time (31.03 - SV) ( SV =  31.03). So it happens at 0s after the Phase 3 coroutine is called.
Not sure if this is the best way to set things up, but it makes things simple if I have to move functions around because the time to do an action is always the exact time in the song.

print ("PHASE 3");
float SV = 31.03f;
MusicController.control.SkipToPoint (SV);
Spawner3.MoveObjectToPoint (31.03f-SV, null, new Vector2 (-2, 0), 0);
Spawner4.MoveObjectToPoint (31.03f-SV, null, new Vector2 (2, 0), 0);

Spawner3.CreateShape_Circle (31.03f-SV, null, new Vector3 (-2, 0), 0.38f, 9, 0.5f, 0.5f, 1, true);
Spawner3.ChangeScale (34.73f-SV, null, 4, 4, 3.1f);

Spawner4.CreateShape_Circle (37.74f-SV, null, new Vector3 (2, 0), 0.38f, 9, 0.5f, 0.5f, 1, true);
Spawner4.ChangeScale (41.35f-SV, null, 4, 4, 3.1f);


Spawner1.CreateLine_ToFrom (44.36f-SV, null, new Vector2 (-2, -2.5f), null, new Vector2 (2, -2.5f), 0.38f, 5, true);
Spawner1.CreateLine_ToFrom (44.36f-SV, null, new Vector2 (-2, 2.5f), null, new Vector2 (2, 2.5f), 0.38f, 5, true);
Spawner1.BreakRandomly_Children (46.32f-SV, 0, 2);
Spawner1.ChangeAlpha_Children (46.32f-SV, 0, 0, 4);
Spawner1.Destroy_Children (50.32f-SV, 0);


Spawner3.RotateDegrees (46.32f-SV, null, 360, 1.45f);
Spawner4.RotateDegrees (46.32f-SV, null, -360, 1.45f);


Spawner2.CreateLine_ToFrom (47.87f-SV, null, new Vector2 (-2.5f, -2.5f), null, new Vector2 (2.5f, -2.5f), 0.38f, 5, true);
Spawner2.CreateLine_ToFrom (47.87f-SV, null, new Vector2 (-2.5f, 2.5f), null, new Vector2 (2.5f, 2.5f), 0.38f, 5, true);
Spawner2.BreakRandomly_Children (49.56f-SV, 0, 2);
Spawner2.ChangeAlpha_Children (49.56f - SV, 0, 0, 4);
Spawner2.Destroy_Children (53.56f - SV, 0);


Spawner3.RotateDegrees (49.73f-SV, null, -360, 1.35f);
Spawner4.RotateDegrees (49.73f-SV, null, 360, 1.35f);


Spawner1.CreateLine_ToFrom (51.21f-SV, null, new Vector2 (-2.5f, -2.5f), null, new Vector2 (2.5f, -2.5f), 0.38f, 5, true);
Spawner1.CreateLine_ToFrom (51.21f-SV, null, new Vector2 (-2.5f, 2.5f), null, new Vector2 (2.5f, 2.5f), 0.38f, 5, true);
Spawner1.BreakToTarget_Children (52.89f - SV, null, new Vector2 (0, 0), 0, 4);
Spawner1.Destroy_Children (56.89f - SV, 0);


Spawner1.Shoot_CircleBurst (54.90f-SV, null, new Vector3(-1, 1), 15, 2, 3);
Spawner2.Shoot_CircleBurst (55.75f-SV, null, new Vector3( 1, 1), 15, 2, 3);
Spawner1.Shoot_CircleBurst (57.25f-SV, null, new Vector3( 0, 0), 15, 1.5f, 3);
Spawner2.Shoot_CircleBurst (57.25f-SV, null, new Vector3( 0, 0), 15, 2, 3);

A lot of what I have done is all of the generic stuff, like move / rotate / create and dealing with sets of objects. My next post, Ill give a list of all of the new completed functions that are available. For the most part that stuff is done and I have enough of the functions I can start doing some advanced custom "actions." Not sure what things I will work on, but for starters I already wrote the ability to create an N-Sided polygon with X skips (skips = instead of just going around the outside of an object, you can skip X points and create star like objects easily). I also rewrote how shapes are created and morphed using something new I learned about C#.

[RegalPrime]

Been a while since the last update. The avoidance is still the same :p

It's surprising how long you can spend writing support scripts to get them just right. After doing this scripting and my avoidance, I watch others stream and I look at it so differently now. Its not that its a fancy design, I try to break it down in how they did it, and that alone made me spend a lot more time adding functionality to make it easy to do these design effects. On top of that, I found some cool c# stuff that made me rewrite a chunk of my code again, but it made it a lot easier to add to the script now.

I have a bit of time tonight and I figure I will list ALL of the stuff I have added. Guess it will also help me with the readme when I update the engine in the future.
For the people who have looked at my engine, all of the stuff I have been coding, replaces the NewObjectSpawner.cs script. It works better, has tons more functionality, and its very clean.
The script contains functions that make life easy. Stuff like, moving / rotating / scaling / looking at an object, and also the creation of shapes for use in an object spawner / avoidance fights.

- So here we go - I will list the coroutine name and brief information about what it does
Pretty much every coroutine has extra variables that are not listed that deal with start delay, position references, locality, and etc

ObjectManipulation.cs script

(click to show/hide)

MoveObjectToPoint - Takes an object and moves it to a particular position over X seconds

FollowTarget - Takes an object and makes it follow another target object
Stop_FollowTarget - Stops the above coroutine

WaveEffectObject - Makes an object move in a sin wave effect depending on variables
Stop_WaveEffect - Stops the above coroutine

RotateDegrees - Rotates an object X degrees over Y seconds. Can also rotate forever.
Stop_ForeverRotate - Stops the above coroutine

RotateToDegree - Rotates an object to a certain degree over X seconds (either clockwise / counterclockwise direction)

RotateTwordsPoint - Makes an object look in the direction of another object. Can also forever "look at"
Stop_RotateTwords - Stops the above coroutine

RotateAroundPoint - Makes an object rotate around another object.
Stop_RotateAround - Stops the above coroutine

ChangeScale - Changes the scale of an object over X seconds

ChangeColor - Changes the color of an object over X seconds. Can change it randomly / constant random color change as well.
StopColorChangeEffect - Stops the above coroutine

ChangeAlpha - Changes the alpha of an object (fade / unfade effect)

ObjectCreation.cs script

(click to show/hide)

Pooling stuff - Efficiency code so it reuses objects instead of deleting and creating them again. Can turn off.

The below Set_coroutines deal with how objects are spawned.
SetEnablePooling - Allow for repooling of objects?
SetProjectile - Set the object that will be spawned
SetColor - Set the color of the spawning object
SetColor_Random - Makes objects spawn at random colors
SetKinematic - Are the objects kinematic?
SetGravityScale - Sets the gravity multiplier of the spawned objects

The calculate functions are the one stop shop for other functions to get data on how to make certain shapes. They will return certain positions based on input values.
IEnumerable<Vector3> Calculate_Line - Returns the location of each object on a certain line
IEnumerable<Vector3> Calculate_Circle - Returns the location of each object on a circle
IEnumerable<Starting_EndingPoint> Calculate_Square - Returns the starting and ending point of each leg on a square.
IEnumerable<Starting_EndingPoint> Calculate_Polygon - Returns the starting and ending point of each leg on a polygon.
IEnumerable<Vector3> Calculate_PolarCurve - Returns the location of each object along a polar curve.

All of the below creation coroutines create a shape out of individual objects (much like you see in avoidance bosses).
They have a lot of variables to deal with startdelay, spawn rate of individual objects in a set, size, etc.
There are variables that deal with the curvature / indents of a line as well. So a line can be a curved line or a square / polygon can have curved edges.
CreateLine_ToFrom - Creates a line between 2 points containing X objects.
CreateLine_InDirection - Creates a line at a point in a certain direction of a certain length
CreateLine_MultiLines - Creates an X legged object.

CreateShape_Circle - Creates a circle shape out of X objects.
CreateShape_Square - Creates a square shape out of X objects.
CreateShape_Triangle - Creates a triangle shape out of X objects.
CreateShape_Polygon - Creates a polygon shape out of X objects. This deals with things from n-sided polygons to star shapes (using the leg skip variable)
Create_PolarCurve - Spawns objects along a polar curve
Create_PolarCurve_abcoskt - Takes inputs to use the polar formula r=a+bcos(kt) (polar rose, this shows some designs you can do  https://en.wikipedia.org/wiki/Rose_%28mathematics%29)
Create_PolarCurve_Heart - Uses the polar formula that creates a heart shape (spacing on the certain X object spawn looks wonky at times)
Create_PolarCurve_Spiral - Uses the polar formula that creates a spiral shape

All morph coroutines take in a list of gameobjects and morphs them to a certain shape over time.
MorphTo_Line_GameObjectList
MorphTo_Circle_GameObjectList
MorphTo_Square_GameObjectList
MorphTo_Polygon_GameObjectList
MorphTo_PolarCurve_GameObjectList
MorphTo_PolarCurve_abcoskt_GameObjectList
MorphTo_PolarCurve_Heart_GameObjectList
MorphTo_PolarCurve_Spiral_GameObjectList

Destroy_GameObjectList - Destroy a set of gameobjects
Destroy_GameObjectList_CircleBurst - Destroy a set of gameobjects, but spawn a circle burst in each objects place.

Change coroutines are the same as above, but effect an entire set of objects instead (like changing the color of all the objects in a square)
ChangeAlpha_GameObjectList
ChangeColor_GameObjectList
ChangeScale_GameObjectList
ChangeKinematicState_GameObjectList
ChangeGravity_GameObjectList

WaveEffectObject_GameObjectList - Causes a wave effect on each object in a list (will increment each object to create a consistent wave effect over each consecutive object)
BreakToTarget_GameObjectList - Causes every object in a list to be thrown at a certain point.
BreakRandomly_GameObjectList - Causes every object in a list to be thrown in a random direction.
StopVelocity_GameObjectList - Stops every object in a list from moving.

RotateDegrees_GameObjectList - Rotates all objects in a list
RotateTwordsPoint_GameObjectList - Causes all objects in a list to look at a target.

All of the below are spawner functions. They shoot objects.
Shoot_AtTarget - Shoot X objects at a target
Shoot_FollowTarget - Shoot X objects that follow a target.
Shoot_RandomSprayBounce - Shoot X objects that bounce off of the ground (or even each other)

Shoot_RandomSprayOutwards - Shoots X objects randomly outwards from a certain point
Shoot_SprayInDirection - Shoots X objects in a general direction
Shoot_CircularSpray - Shoots X objects circularly outwards
Shoot_WaveSpray - Shoots X objects so that it creates a wavy like line (will continue to do the wave effect over its life)
Shoot_FromScreenEdge - Shoots X objects in certain direction that originate from the edge of the screen.
Shoot_CircleBurst - Creates a circle of objects that expand outwards at a certain point.

ObjectCreationExtras.cs script
These are coroutines that do a chain of events and then destroy themselves to make a simple to use effect.
Nice to be able to do a multistep effect with one function call. Too busy writing the above script stuff to add to this section to make the better looking effects.

(click to show/hide)

Custom_SingleExpandEffect - Creates a single object, expands it enormously. While expanding it will change color and drop its alpha to 0 over time. Then it destroys the object.
Nothing that fancy. I used it in my avoidance fight where it spawned a non-deadly object. Also has an overloaded function call that randomly chooses its spawn location somewhere on the screen.

Custom_CircleBurstEffect - Creates a circle burst at a location. After X seconds, it stops all of those objects from moving. After X more seconds, it destroys every object and spawns a circle burst in its place. Also used in my avoidance fight.

Not sure when I will be done with these scripts. Also not sure when I will release the next engine version. If you are interested in the above scripts, let me know.

[RegalPrime]

I feel pretty good about the scripts I have been working on, so I started taking some engine things off my list.

I really want to do another engine release, but I have to see what is the easiest way to do it. I have no clue if there is a quick way to do it without totally breaking old versions or make it just update the old stuff. I will have to mess around on that to see what is the least intrusive way. The easiest way for me is to just zip up the project folder again, but I am not sure how they works if people have some items created already in their project.

I keep a running list of things added to the engine and I dont think I mentioned any so far, so here we go.
Major addition includes
ObjectManipulation.cs script
ObjectCreation.cs script
ObjectCreationExtras.cs script

The above 3 scripts replaces the NewObjectSpawner.cs script. See this post for a bit more information.
https://www.iwannacommunity.com/forum/index.php?topic=1150.msg10687#msg10687

The new scripts were used in the creation of an avoidance boss. This scene is included in the engine build (added as a scene in the engine build)
All of the "I wanna be the cat scenes" were put into a sub folder and removed from the scene engine build). So each individual scene is there, just dont expect to be able to move from scene to scene without adding them to the engine build first.
Be aware that due to the update to many scripts, there may be some disconnects or bugs in the cat scenes. I have not went through any of the scenes as of late.

Fiddled with materials and learned how to deal with them + create normal mapping. Interesting what you can do with normal mapping. This allows for sprites to have the illusion of depth via shadows. The hardest part is to find a way to create them easily. Added some temporary normal maps for certain objects to see how they work such as blocks / apple / tree / and miku.

Created full screen effects using materials and scrolling normal maps
- fire - looks like the screen is on fire with flames licking up. pretty nice looking
- fog - looks like rolling fog / smog across the screen
- water - looks like you are looking at the bottom of a riverbed with the water going over rocks. Not very awesome looking but I didnt try all that hard finding good materials, lol

Got rid of the hard coded double jump and put in a generic multijump variable. This way you can easily change the number of extra jumps the player can do.
- Added the option to change this variable through the area modifier prefab.
- Jump refreshers refresh all the extra jump.

Jump refresher updated
- Has option to add a certain number of jumps per trigger
- Has option to allow to go over jump cap from the above trigger

Added an array of saveable triggers. Is set to 10 at the moment. Used for things like secret collectables or boss tokens.
- GameCompleted script - Tells the saved file the game is completed.
- SaveATrigger script - Updates the array / value when object is triggered and saves it to the file
- CheckATrigger script - Will check if the statement is valid and will enable / disable the gameobject.

Updated the save/load screen. Moved some stuff around and updated the graphics a bit.
Added in a panel to show the 10 collectables. Shows an icon when that triggered index is triggered ingame.
Changed the game complete from a toggle button to a gameobject that is set active when the game complete trigger is activated. Added a game completed icon.

ResetManager is now the EventManager
- Added in the ability for other scripts to know when the player has died. Can be used for avoidance fights to stop them from doing their actions.
- Still has the ability for other scripts to know when to reset their values.
- Certain information is displayed in the console about attachments when events are called (just for my information). Stuff like, 7 scripts are resetting, or player died by X object and 2 scripts were told about it.

PlayerDied script is now the PlayerHPModule
- Player now has option to change its HP. Default is 1 HP and 1s damage delay. These variables are hard coded and only changeable in script.
- I can expand on this later when I feel a screen might need a HP based player (still need functions to manipulate this value).
- Added in option for hit sound effect. Is only played when player is hit and still has hp remaining (else the death sound would play).

CalculateChecks.cs. If a AoE check finds a ground object but it is not a BoxCollider2D, it will use raycasting on whatever is there to find the distance (previously had bad logic where I missed an else statement)
Went though every script to get rid of certain player references. Each object should effect the player that triggered it. Overall just a clean up of code, might help out later.
Cleanup of old engine assets. Some sprites / old AI prefabs that didnt have connections. Some old materials.
Added a few sprite sheets of fruits / flowers because they looked nice
Added duplicate sprites + their normal map, so that section is a bit of a mess.

Been a while since I have done a picture, so here are two.
All of the sprites on this screen are the default guy game sprites EXCEPT that I added a normal map to them (even the background). I made all of the normal mapping so dont expect it to be perfect.
Stuff to look for
-Shadow on the face and hands of the guy
-tree / spikes / apple gets texture from shadows
-parts of miku seem to to have some depth
The light source is on the rightish middle

(click to show/hide)

New loading screen as well. looks better than the old one

(click to show/hide)

[radicalero]

Hi! I am trying to test your RegalPrime-UnityEngine v1.2 on unity v4.5.5f1 ad the program break when open loading the project.
I tryed with unity 5.0.1f1 too and the the project open and the scene play but dont work.
Can you share your actual latest version of the proyect and say what is your unity version?
Best Regards!

[RegalPrime]

Guess I haven't been keeping up on the newest versions nor did I think to list what version build I was using (updated the first post with that information).
Both engine 1.1 and 1.2 were built in version 4.6.1f1. If I remember, I downloaded / updated to 4.6 when it came out and never updated it since then.

Now I see that unity 5.0 free is out (since March 3, 2015), so I need to think about updating the engine and if you had problems, it makes me wonder what will happen when I do the update. I really appreciate you letting me know. I admit I didnt know unity 5.0 was free as of yet (I haven't kept a close eye on their site in forever).

Ive been doing a rewrite of the AI and that is pretty much done (at least the major points), so I will download 5.0 and start the painful task of figuring out what is new / what might break and how to fix it.

[radicalero]

Thanks! Waiting for it =)

[RegalPrime]

I uploaded a preliminary version of the engine updated to Unity 5. Did a lot of cleaning and it's a bit smaller (89m -> 71m)
This is so I can get some feedback on if people are able to use the engine in the newest version of unity (I felt kinda bad about posting my v1.2 using the outdated engine)

I am using Unity v5.0.2f1 Personal
https://www.mediafire.com/download/ya5dq5f0qz7971f/RegalPrime+-+UnityEngine+v1.25+-+Unity5Test.zip

Cat game scenes are reattached and most everything has been tested. Some weird stuff happened when I updated to unity5 and it wouldn't surprise me if I missed a few things.

[radicalero]

I uploaded a preliminary version of the engine updated to Unity 5. Did a lot of cleaning and it's a bit smaller (89m -> 71m)
This is so I can get some feedback on if people are able to use the engine in the newest version of unity (I felt kinda bad about posting my v1.2 using the outdated engine)

I am using Unity v5.0.2f1 Personal
https://www.mediafire.com/download/ya5dq5f0qz7971f/RegalPrime+-+UnityEngine+v1.25+-+Unity5Test.zip

Cat game scenes are reattached and most everything has been tested. Some weird stuff happened when I updated to unity5 and it wouldn't surprise me if I missed a few things.

Awesome speed to do the update. I will check it today. When I test it i will say how works on me.
Thanks. Best Regards!