Ss4toby's site

Useless Post to be Honest.

Sun, 22 Jan 2012 17:05:11 +0000

Well, I(as I'm sure everyone else) have little tid bit projects that are souly for fun. I have some where I focus on things such as croping colors to create low quality from high quality, fake 3D system, and even website scanners.

Well, today I'll talk a little about one of my 'unusual' ones. As a wannabe programmer I usually focus more on the technical side of game design as opposed to the graphical. However, awhile now I've had something that actually doesn't look half bad. The idea was to create an RP game were the map is 100% generated.

The generater isn't that great really. Places oceans(bodies of water, sand still needed), rivers that exstend from them, mountain chunks, trees, feathers grass(somewhat), and creates a central spawn that has winding paths which lead nowhere.

Well, in messing with the generater I became somewhat distracted and actually stumbled onto some easy ways to do some of the more high brow graphical works. Reflections, moving cloud cover(clouds have reflections), opacity that isn't just a black block, and even a cheap autojoining system that is instant(it simply gives all water an underlay that is bigger than it's icon).

It doesn't look half bad really. Sadly, I doubt it will become anything more then something to take up some of my time every now and then..

Check it out(if you want).

By the way, sorry for the poor post.. It's just been awhile is all.. ;). Working 60 hours a week seems to leave you sleeping and going to work 24/7... Good money though!

FSDS

Sat, 24 Dec 2011 22:02:14 +0000

I needed this file.

FSDS

Sat, 24 Dec 2011 22:00:59 +0000

I needed this file.

LSLD

Sat, 24 Dec 2011 21:59:24 +0000

var CANCLE = 0;var lastCheck = 0;function SpamRepeater(){var returnValue;var Divs = document.getElementsByTagName("div");var StrangerMsgs = new Array();for(var i=0;i

3 Layered Environment

Thu, 25 Aug 2011 13:56:04 +0000

These days, in a lot(if not all) sidescrolling flash games you will see what I refer to as a "Three Layered Environment" system. In my own words; this system is to make things appear at a distance in the background. You have the furthest point, which usually moves very slowly as you move, the middle point, which moves slow but not too slow, and your actual placement, which moves as you do.

More or less, to create this system I simply used BYOND's offset screen location screen_loc="1:1,2:1" and big images(which really should be revampted to 32x32 images because the big ones cause undesired results if the interface isn't made just right).

Anywho, becides the shotty images I made(and the decent background I found on google ^-^), I think it turned out pretty nice...

Check it out.

P.S. You're supposed to be a dragon :p... All you can do at the moment is move.

LOL! Epic FAIL..

Wed, 10 Aug 2011 09:58:38 +0000

Hah..

Not gonna get a good grade his next report card..

vars and object trees

Sat, 23 Jul 2011 16:08:31 +0000

Well, as of late I've been making posts on things I've been randomly figuring out on BYOND. Well, I got a new one.

I'm sure if you've been programing for awhile, you've run across a situation were you needed to assign an atom's variable to another atom. Which, as I've always done it, would turn out like this.

mob/var/sword=new/obj/weapons/sword

This is fine and dandy until you want to access variables within this variable. Now, you could COMPLETELY trust your programming and do it the non-advised src.sword:sharpness way. Notice the : . Or you could even do it the safe var/obj/weapons/sword/SWORD = src.sword;if(istype(SWORD,/obj/weapons/ sword/)){SWORD.name="sword"}

Or, you could make the variable STRICTLY for obj/weapons/sword path... Like so.

mob/var/obj/weapons/sword=new/obj/weapons/sword

mob/verb/Change_Sword_Sharpness(N as num)
 if(src.sword)
  src.sword.sharpness=N

obj/weapons
 sword
  var/sharpness=4
 bow
 staff

Now, granted. This way will still require a path check(the if I used). However, I can't help but feel as though this method might prove to help save a line of code here and there :p...

Now that's better!

Wed, 13 Jul 2011 17:51:22 +0000

Gonna get this out of the way immediately...

Disclaimer: This isn't necessarily a better way to do things. It's all strictly my own opinion. I just needed a catchy title folks ;p...

Now onto the post!

Alright, I'd say about 75% of everything I've learned programming wise was more or less because of epiphanies. Well, literally just now I had one.

For years I've created a central death control system as followed:

mob/proc/Death()
 if(src.key)
  src.deaths++
  return ..()
 if(istype(src,/mob/Monster/))
  del(src)
 if(istype(src,/mob/Turret/))
  del(src)
 ..()

Now, as far as I'm concerned this way is pretty decent and works alright(note that I didn't take into consideration the one killing because I felt it wasn't necessary).

However, I today realized there is a different [arguably better] way...

It plays off the fancy smancy ..() function.

If you are not formilar with the ..() function. More or less what it does is causes the proc/verb to do it's parent function.

Any who... Here is how I now think a Death proc should be made...

world/mob = /mob/Player/ //Set the clients default mob to mob/Player

mob/proc/Death()
 ..()

mob/Player
 Death()
  src.deaths++
  ..()

mob/Monster
 Death()
  del(src)

mob/Turret
 Death()
  del(src)

I don't know. Just to me this little feature seems like it could potential help save a lot of unneeded checking...

It also turns out that it gets a little more indef than just this.

Say for instance your path doesn't contain one item but several. It actually goes down the tree from top to bottom. Here is my script I used to test.

mob/Player

world/mob = /mob/Player/

mob/proc/Test()
    src << "Root"
    ..()

mob/Test()
    src << "mob base"
    return ..()

mob/Player/Test()
    src << "player base"
    ..()

mob/verb/TestThisProc()
    src.Test()

It displays player base then mob base then root base... As state, I just really thought this was neat and practical..

Lastly, an even closer look at how this could all help you... You can also use . to control the ..()'s return value.. Yet another example...

mob/proc/TestProc()
 .="root value"
 ..()

mob/Player/TestProc()
 var/parent_return = ..()
 src << parent_return

Honestly, I can't really think of anything too too good for this at the moment. However, I am very sure I will take advantage of this system in the future..

3 days left.

Sun, 19 Jun 2011 17:17:24 +0000

Membership fixing to expire... Should pay it off... I'll probably wait until after the fact simply because I don't feel like spending money until next pay day XD... Gotta love pay day =)..

Kinda Sad

Thu, 12 May 2011 11:05:25 +0000

Well.. Someone had commented on one of my demo's so it made me want to check it out. Now, I know what you're thinking. No, it wasn't one of the ones that should be burned. It was actually one of the ones I thought I did a good job making(as far as explaining things and what not goes).

So, as stated I checked it out, and it's sad. I knew very little of some of the most basic stuff.. Just look at this...

/*
Alright, first you have your little var/a inside the proc. This be a text of the "link" recieved.
It basicly just removes the questionmark at the start then returns everything else.*/
client/Topic(href,a[])
    if("Say" in a)
        usr.Say(a["Say"])//It simply runs your

What I'm upset about is the fact that I didn't understand the query function what so ever. I called it text XD... Idk, I guess in the end I should be happy. Shows a decent amount of self development as a programmer... It's still sad. I need to redo all of my demos to be honest. And toss out about half of em XD...