Author Topic: Ultimate Boss Battles  (Read 13444 times)

You shouldn't post a topic on a server before its finished, in my opinion.

1.  Rip off of Pecon's Boss Battles.
2.  You shouldn't have posted anything until you were near finished with construction.
3.  There's almost no real story line.
4.  Horrible outline for the topic.

If you can fix these four things, perhaps this could be big.
Seems redundant to make a topic about an idea that you haven't tarted working on, and is very similar to an already incredibly popular server. If you can make it unique, I'd wait until you have some tangible progress before making a thread about it.
You shouldn't post a topic on a server before its finished, in my opinion.
Make sure you think before posting lord. Otherwise these kind of posts wouldn't be here.

1.  Rip off of Pecon's Boss Battles.
2.  You shouldn't have posted anything until you were near finished with construction.
3.  There's almost no real story line.
4.  Horrible outline for the topic.

If you can fix these four things, perhaps this could be big.
What four things? I can only see 2 issues.
1. is obviously invalid and you don't need a story line for a server.

well im sorry but im new at this stuff. i got singed up for the forums about a week ago

1.  Rip off of Pecon's Boss Battles.
2.  You shouldn't have posted anything until you were near finished with construction.
3.  There's almost no real story line.
4.  Horrible outline for the topic.

If you can fix these four things, perhaps this could be big.
well ive always wanted to have a server that was big...IM WORKIN ON DIS stuff

It might not be real since this person did not plan out the topic.

EDIT: I would also like to help on this server, I am an eventer and a scripter, I can't build because I am terrible at that; but I am very good at inventing and I am decent at scripting, I have made a setMaxHealth event, but I will never release this since there is only one bug that I can't fix yet. Which is when the person leaves, the maxDamage is stuck at the amount it was set at.
That isn't a bug. That's player persistence saving it, like how it saves your tools and velocity and position.

That isn't a bug. That's player persistence saving it, like how it saves your tools and velocity and position.
You don't understand how my script works. It overwrites the datablock's max damage. When they spawn, it saves the actual damage. The events overwrite the max damage. When they die, it makes that data block return back to its original health it was. When they leave, it will not reoverwrite the datablock. So its stuck at a max damage it was set on the event. This will be fixed when I get home though.