Custom Map #564: Exostopia Map#2 : A new type of emitter. By: Exostum

AutoPost · 1697

AutoPost

  • Global Moderator
  • *****
    • Posts: 27044
This topic is for discussion of map #564: Exostopia Map#2 : A new type of emitter


Author: Exostum
Size: 50x50

Desc:
Encounters a new type of emitters and beat it with .... Beams ???? #CRPL #NoSpores #Forge #NoTechLimits #CustomEnnemy



Grayzzur

  • Sr. Member
  • ****
    • Posts: 785
An interesting concept, but in a map that's way too easy. There should be some pressure from the creeper to keep you from being able to immediately build a beam in range of that emitter. On a map this small, limiting to one command node might have slowed down initial progress a little. I like the idea of this enemy, but it should be in a much harder to get to location or there's no real challenge.

"Fate. It protects fools, little children, and ships named 'Enterprise.'" -William T. Riker


exostum

  • Jr. Member
  • **
    • Posts: 71
I started the map with stronger parameters for the emitter but I tuned them down as it was getting to 2000 too quick.

Limiting the cn down to 1 might be indeed a good idea.


My Work in progress Maps (On hold for now)


Giant_Gamer

  • Newbie
  • *
    • Posts: 3
I liked this map, it was sweet and to the point.

As for challenge level, why not make it grow stronger with every beam, until the set level of creeper, and it dies because of overloading? This would allow the player to tackle it, but if they don't start to up the defense, the beams in range could be at risk, allowing for more of a fight and making this foe almost the same from encounter to encounter. Since the foe would not be target-able from nulifiers, the risk of having one low-medium emitter would not be there.



I do have a quick little question, when I was looking into making custom entities I had trouble displaying more than one line of data. I tried to just copy the example and then fill in the info relevant to the entity (in this case a "Terrain Rail Walker" (from the sample page).

I could only display one height value and on;y on one line...

(click to show/hide)
only the min shows up

Any help in this matter would be helpful to me.



ZackNAttack

  • Jr. Member
  • **
    • Posts: 86
I liked this map, it was sweet and to the point.

As for challenge level, why not make it grow stronger with every beam, until the set level of creeper, and it dies because of overloading? This would allow the player to tackle it, but if they don't start to up the defense, the beams in range could be at risk, allowing for more of a fight and making this foe almost the same from encounter to encounter. Since the foe would not be target-able from nulifiers, the risk of having one low-medium emitter would not be there.



I do have a quick little question, when I was looking into making custom entities I had trouble displaying more than one line of data. I tried to just copy the example and then fill in the info relevant to the entity (in this case a "Terrain Rail Walker" (from the sample page).

I could only display one height value and on;y on one line...

(click to show/hide)
only the min shows up

Any help in this matter would be helpful to me.

Use
(click to show/hide)
The problem was that it reads it as "Max_Hieght:(whatever the max height is)" "Min_Hieght:(whatever the min height is)" SetPopuptext, but now it's
"Max_Hieght:(whatever the max height is)
Min_Hieght:(whatever the min height is)" SetPopuptext

Zack on cw3


exostum

  • Jr. Member
  • **
    • Posts: 71
Here comes a workaround for what you want (i modified my own CRPL but not tested it)

(click to show/hide)
Here comes a example map

EDIT : the time that i posted this message ZackNattack posted another reply. That is interesting to see that we both use different means to achieve the same results
« Last Edit: May 16, 2014, 06:40:13 pm by exostum »

My Work in progress Maps (On hold for now)


chwooly

  • Full Member
  • ***
    • Posts: 546
I liked this map, it was sweet and to the point.

As for challenge level, why not make it grow stronger with every beam, until the set level of creeper, and it dies because of overloading? This would allow the player to tackle it, but if they don't start to up the defense, the beams in range could be at risk, allowing for more of a fight and making this foe almost the same from encounter to encounter. Since the foe would not be target-able from nulifiers, the risk of having one low-medium emitter would not be there.



I do have a quick little question, when I was looking into making custom entities I had trouble displaying more than one line of data. I tried to just copy the example and then fill in the info relevant to the entity (in this case a "Terrain Rail Walker" (from the sample page).

I could only display one height value and on;y on one line...

(click to show/hide)
only the min shows up

Any help in this matter would be helpful to me.

Use
(click to show/hide)
The problem was that it reads it as "Max_Hieght:(whatever the max height is)" "Min_Hieght:(whatever the min height is)" SetPopuptext, but now it's
"Max_Hieght:(whatever the max height is)
Min_Hieght:(whatever the min height is)" SetPopuptext

Is the misspelling of height intentional?

“Always listen to experts. They'll tell you what can't be done, and why. Then do it.”
― Robert A. Heinlein, Time Enough for Love